You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure what to expect but what I would like to see if there are additional variables in the yaml file that they are also captured in the provenance RDF output. Why? This way we can add additional metadata about the job execution, perhaps a project identifier, description of other properties you would like to have at hand when digging through all the provenance information.
A current "workaround" is to add a basic field to the workflow that can potentially capture a lot. This way it is present in the provenance but it is not a best practice I think to capture it this way.
Actual Behavior
As expected I guess, the arguments that are not used by the workflow are ignored
Your Environment
cwltool version: 3.1.20230719185429
The text was updated successfully, but these errors were encountered:
Expected Behavior
Not sure what to expect but what I would like to see if there are additional variables in the yaml file that they are also captured in the provenance RDF output. Why? This way we can add additional metadata about the job execution, perhaps a project identifier, description of other properties you would like to have at hand when digging through all the provenance information.
A current "workaround" is to add a basic field to the workflow that can potentially capture a lot. This way it is present in the provenance but it is not a best practice I think to capture it this way.
Actual Behavior
As expected I guess, the arguments that are not used by the workflow are ignored
Your Environment
The text was updated successfully, but these errors were encountered: