Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
fujitsu:hpcgateway:guides:internals:picoms [2018/03/26 13:32]
fujitsu
fujitsu:hpcgateway:guides:internals:picoms [2018/03/26 13:48]
fujitsu [Picom task context]
Line 18: Line 18:
   * the template tasks it can use as model for the new tasks it,    * the template tasks it can use as model for the new tasks it, 
   * the tasks it has spawned previously ​   * the tasks it has spawned previously ​
- 
- 
-=== Runlog structure === 
  
 The runlog is the center of the dialog between Gateway and the picom script. The runlog is the center of the dialog between Gateway and the picom script.
Line 74: Line 71:
 </​code>​ </​code>​
  
 +==== Context ====
 +
 +The executions of the picom tasks and its sub-tasks is influenced by the //context// of the execution.
 +The context is keep the trace of the executions and it propagated to the sub-tasks of the picom task.
 +
 +=== Step and maxStep ===
 +
 +The //step// correspond to the different executions of the picom script.
 +
 +The step is limited by a field //maxStep// in the context (default is 100).
 +
 +=== Depth and maxDepth ===
 +
 +The //depth// is the depth of the task hierarchy.
 +The picom task that is created by the user has a depth 0 and its immediate children have a depth 1.
 +  ​
 +The depth is limited by a field //​maxDepth//​ in the context (default is 3).
 +
 +The depth and its limitation are crucial in the recursive picoms to avoid the picoms to run wild.