Page History

Turn Off History

When a splice is created, a subdag is incorporated directly into the parent dag. This is basically a recursive operation, so that splices that contain splices need to be absorbed before being absorbed into the parent dag. For all practical purposes, the splice becomes part of the parent DAG. Because of this, there are some limitations:

  1. Splice DAGs cannot be created at "run-time". They must exist when the dag is parsed. If you need to create a DAG on the fly, use a nested DAG.
  2. Category limits can apply to a splice dag, but not to a nested dag. This is because there is no way for the parent dag to communicate usage to the nested dag.
  3. There is only one DAGman process with a splice DAG.

When one has a splice, the next question is what happens with MAXJOBS and categories. If the category name is prefixed with a '+', the category is global and refers to all jobs with that category. Otherwise, the category only refers to the splice DAG. Upper level dags control lower level dags as far as category goes.