⏯️ Understanding Executions

An Execution represents the instantiation of a method with a specific set of inputs and parameters.

Each time a user runs a method, CCP creates a new execution record, which includes all the required data to trace what was done, how, where, and with what inputs.

πŸ“ Execution Structure

Each execution contains the following key components:

execution/ 
β”œβ”€β”€ metadata/ 
β”‚ β”œβ”€β”€ request.json 
β”‚ β”œβ”€β”€ method.json 
β”‚ β”œβ”€β”€ infrastructure.json 
β”‚ └── instance.json 
β”œβ”€β”€ auth/ 
β”‚ └── jwt.json 
β”œβ”€β”€ outputs/ 
β”‚ β”œβ”€β”€ output.x
β”‚ β”œβ”€β”€ output.y
β”‚ └── output.z

This structure ensures that all necessary data for understanding and reproducing an execution is preserved.

πŸ§ͺ Workbench

Executions are stored temporarily in a personal Workbench, which acts as a transient area for:

  • Draft executions

  • Testing methods

  • Debugging and reconfiguration

Executions remain in the Workbench until manually deleted or explicitly exported.

πŸ“€ Exporting Executions

Users can export any execution to their D4Science Workspace by selecting the archive option.
This generates a ZIP file containing all outputs and metadata. The exported path is usually:

<workspace_root>/CCP/executions/<execution-name>.zip

Executions can also be imported again from the Workspace or via a shared URL.

πŸ”„ Re-execution

Any execution present in the Workbench can be re-run with the same parameters, or adapted with new inputs before submission.

To resubmit an execution, just press the Re-Submit button in the exeution monitor

To adapt adapted with new inputs before submission, click on the β€œDirect Link” button to open the execution form, prefilled with the previous inputs.