Representation - Yes
- Burrito
- Chef
- CMake: Makefiles can be used as an executable representation for the experiment.
- CRIS
- Dexy
- ES3: The tool generates provenance graphs.
- eScienceCentral
- Galaxy
- GenePattern
- IPython
- Kameleon
- Kepler
- LLVM: The execution trace produced is a provenance graph that is loaded into SPADE, where it can be managed and queried.
- Madagascar
- make: Makefiles can be used as an executable representation for the experiment.
- Mathematica
- MATLAB
- Noweb
- noWorkflow: noWorkflow creates a provenance graph from the execution that can be analyzed. Provenance can also be analyzed by differing multiple executions, or using inference queries.
- PASS: Besides the audit trails (descriptive-only), PASS has a feature to generate scripts to reproduce an experiment in the environment in which it was originally created and executed.
- ProvenanceCurious
- PTU: It generates a provenance graph from the execution.
- Puppet
- Pysa
- RCloud
- RDataTracker: RDataTracker creates a provenance graph (DDG) from the execution that can be analyzed.
- ReproZip: ReproZip creates a configuration file (descriptive-only representation) that details all the provenance related to the experiment. Besides, it can create a scientific workflow (VisTrails) for the experiment (executable representation).
- Sage
- SCons: The Python scripts can be used as an executable representation for the experiment.
- Sweave
- Taverna
- Trident
- VisTrails
- Wings