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
Copy file name to clipboardExpand all lines: MC/doc/WorkflowRunner.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,7 @@ still in development. Currently, it follows the following scheme:
58
58
},
59
59
{
60
60
"name": "task2",
61
+
"env": { "MY_ENV":1 }
61
62
"cmd": "o2-sim-digitizer-workflow"
62
63
"needs": [ "task1" ],
63
64
"resources": {
@@ -80,7 +81,8 @@ Further keys in this format are:
80
81
|`resources`| estimated resource usage for average cpu load (250 = 2.5 CPUs) and maximal memory in MB. Used for scheduling. -1 is used for unknown or don't care. |
81
82
|`timeframe`| timeframe index or -1 if not associated to any timeframe. May have influence on order of execution (prefer finish timeframe first) |
82
83
|`cwd`| the workding directory where this is to be executed |
83
-
| `label` | a list labels, describing this stage. Can be used to execute workfow in stages (such as 'do all digitization', 'run everthing for ITS'
84
+
|`label`| a list labels, describing this stage. Can be used to execute workfow in stages (such as 'do all digitization', 'run everthing for ITS' |
85
+
|`env`| local environment variables needed by the task |
84
86
85
87
While a workflow may be written by hand, it's more pratical to have it programmatically generated by sripts, that is sensitive to configuration and options. A current example following the PWGHF embedding exercise can be found here [create_embedding_workflow](https://github.com/AliceO2Group/O2DPG/blob/master/MC/run/PWGHF/create_embedding_workflow.py)
0 commit comments