| Horizontal Navigation Bar | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
submitted by a specific ecflow_server
two different ways: as data dependency triggers and as courtesy triggers.
Triggers where designed for the former. The latter are used to prevent too
many jobs running at once and are actually an artificial way of queuing jobs.
Because ecFlow does not distinguish between the two sorts of triggers, suites can become
Limits are declared with the limit keyword
A very useful addition to "edit" is the ability to clone a task, perform some minor modifications to its script, and run it as an "alias".
Such a task can run under the control of the ecFlow but has no impact on the activity of the suite itself i.e. it will have no dependencies.
This feature can be used to rerun a task for a previous date, or to solve transient problems such as full file systems.
In this case, the task can be run using a different disk, in order to guarantee the completion of the suite on schedule.
The analyst then has time to understand why this condition arises and take the necessary actions.
What to do
- Pick an existing task and select the EDIT tab, in the info panel.
- Make some change to the script. i.e could add something like sleep 1
- Select 'Submit as alias', then submit the job.
You should notice that a new node is added as a child of the task. - Select the same task, an repeat the process. This shows a task can have many aliases.
- Select one of your aliases,, and force it to be aborted. Right Mouse Button->Force→Aborted. Notice that node state is NOT propagated.
What to do
| Horizontal Navigation Bar | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|