Resource requirements

[simleo]

If available, record the application's resource requirements. This is useful to those who want to reproduce the run. In CWL, this is provided via ResourceRequirement. We could use properties like memoryRequirements or storageRequirements for this.

[simleo]

This would be part of the prospective provenance. SoftwareApplication already has several *Requirements properties that can be used, so profile-wise (if we don't add any extra terms) we can simply add a general recommendation to use them if the corresponding information is available, e.g. if the workflow author added the relevant annotations. Runcrate could add a section where CWL ResourceRequirement is converted, then we can compile a mapping guide and add it to the web site (similar to https://www.researchobject.org/workflow-run-crate/cwl_param_mapping).

[simleo]

The only actual match I've found in ResourceRequirement is between ramMin and memoryRequirements .

CWL	Meaning	SoftwareApplication
ResourceRequirement coresMin	Minimum number of CPU cores
ResourceRequirement coresMax	Maximum number of CPU cores
ResourceRequirement ramMin	Minimum RAM	memoryRequirements
ResourceRequirement ramMax	Maximum RAM
ResourceRequirement tmpdirMin	Minimum storage for temporary directory
ResourceRequirement tmpdirMax	Maximum storage for temporary directory
ResourceRequirement outdirMin	Minimum storage for output directory
ResourceRequirement outdirMax	Maximum storage for output directory
	Processor architecture	processorRequirements
SoftwareRequirement packages	Dependencies	softwareRequirements
	Free space required	storageRequirements

[rsirvent]

FYI, this maps with COMPSs constraints definitions, although a different approach is followed (no min-max, exact numbers for some terms, ...).

https://compss-doc.readthedocs.io/en/stable/Sections/02_App_Development/04_Constraints.html

[stain]

Discussed in meeting 2025-03-13

COMPSs vocabulary: https://github.com/ResearchObject/ro-terms/tree/master/compss

WfExS looking at different terms.

[simleo]

This is about the prospective provenance though ("this workflow requires ..."). The issue about the retrospective provenance ("this specific run of the workflow required...") was #10, which is now closed. As we discussed, however, the two are related in the sense that average a priori requirements can be determined by looking at a posteriori usage stats from multiple runs.