cho $EIf If you wish to use ecFlow to run your workloads, ECMWF will provide you with ready-to-go ecFlow server running on an independent Virtual Machine outside the HPCF. Those servers would take care of the orchestration of your workflow, while all tasks in your suites would actually be submitted and run on HPCF. With each machine being dedicated to one ecFlow server, there are no restrictions of cpu time and no possibility of interference with other users.
...
Of course, you may change queue to np if you are running bigger parallel jobs, or SCHOST to eventually run on other complexes than aa. This can be specified in the configuration file such as this one:
| Bitbucket file | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
To use a custom troika executable or personal configuration file with Troika, ecFlow variables should be defined like this:
...