This repository contains the results of several CWLProv-related experiments and their results.
If workflow is previously run with --cachedir and later with --provenance, will the timestamps recorded in the RO correspond to the final execution time (when the cached results were used instead of rerunning the steps) or do they (as they should) represent the time of the execution when the results were cached?
Answer: they do incorrectly represent to the final execution time.
Example workflow to test and enhance the --print-dot function of cwltool such that it distinguishes between components of class Operation (dashed), Workflow (orange) and CommandLineTool (yellow). See PR #...
To assess whether information about docker containers is included in CWLProv provenance.
To assess whether a file specified with a remote location preserves its remote timestamp.
Comparison of CLWProv provenance before and after the propagation of input data annotations.
Design for software metadata in CWLProv provenance.
Answer to the question: Are input parameter values included in CWLProv provenance?
Are SoftwareRequirement and DockerRequirement included in CWLProv provenance?
Emulated extended provenance graph (niaa_wf_run/primary.cwlprov.ttl) and associated SPARQL queries (sparql_queries.ipynb) which can extract the newly added information from the RDF graph.