...
- Option 1: Simple job submission monitored by ECMWF:
- Suitable for single jobs or simple jobs with multiple steps.
- Based on the ECaccess framework.
- Service available to all registered users (no formal request needed).
- See https://software.ecmwf.int/wiki/display/USS/Simple+time-critical+jobs for more information.
- Option 2: Member State ecFlow (or SMS) suites monitored by ECMWF:
- Suitable for more complex applications comprising several tasks with interdependencies between them.
- The suites will be developed according to the technical guidelines described in this document.
- To be requested by the TAC representative of the relevant Member State.
- Monitored by ECMWF.
- Option 3: Member State ecFlow suites managed by ECMWF:
- Further enhancement of Option 2.
- Requires an ecFlow suite, which has usually been developed under option 2 of the framework.
- Application developed, tested and maintained by the Member State.
- It must be possible to test the application using ECMWF pre-operational (e-suite) data.
- Member State suite handed over to ECMWF.
- Member State responsible for the migration of the application, e.g. when supercomputer changes.
- Monitored by ECMWF.
- ECMWF will provide first-level on-call support, while second-level support would be provided by the Member State.
- To be requested by the TAC representative of the relevant Member State.
...
As this work will be monitored by ECMWF staff (User Support during the development phase; the operators, once your work is fully implemented), the only practical option is to implement time-critical work using a suite under ecFlow (or SMS), ECMWF's monitoring and scheduling software packages. Given that SMS will gradually be phased out, we ask new developers of Option 2 activities to use ecFlow. We will therefore only refer to ecFlow in the remaining part of this document. The suite must be developed according to the technical guidelines provided in this document. General documentation, training course material, etc ... on ecFlow can be found at: http://software.ecmwf.int/wiki/display/ECFLOW/Home. No on call support will be provided by ECMWF staff but the ECMWF operators can contact the relevant Member State suite support person, if this is clearly requested in the suite man pages.
...
EcFlow will manage your jobs. Three main actions on the ecFlow tasks are required: one to submit, one to check and one to kill a task. These three actions are respectively defined through the ecFlow variables ECF_JOB_CMD, ECF_KILL_CMD and ECF_STATUS_CMD. You can use any script to take these actions on your tasks. We recommend that you use the commands provided by ECMWF with the schedule module which is available on ecgate. To activate the module, you will run: module load schedule The command called 'schedule' can then be used to submit, check or kill a task: Usage: /usr/local/apps/schedule/1.4/bin/schedule <user> <host> [<requestid>] <jobfile> <joboutput> [kill - status] Command used to schedule some tasks to sms or ecflow <user>: <host>: <requestid>: <jobfile>: <joboutput>: By default /usr/local/apps/schedule/1.4/bin/schedule will submit a task. An example is given in the sample suite in ~usx/time_critical/sample_suite.def. Alternatively, you can use the commands task_submit or task_status and task_kill.
...