| Horizontal Navigation Bar |
|---|
| Button Group |
|---|
| Button Hyperlink |
|---|
| title | Previous |
|---|
| type | standard |
|---|
| url | https://software.ecmwf.int/wiki/display/ECFLOW/Server+security+-+whitelist+file |
|---|
|
| Button Hyperlink |
|---|
| title | Up |
|---|
| type | standard |
|---|
| url | https://software.ecmwf.int/wiki/display/ECFLOW/Advanced+Topics |
|---|
|
| Button Hyperlink |
|---|
| title | Next |
|---|
| type | standard |
|---|
| url | https://software.ecmwf.int/wiki/display/ECFLOW/Using+python+scripting |
|---|
|
|
|
Because ecFlow was designed with ECMWF suites in mind, the date is a very important notion.
ecFlow defines the time using clocks. A
clock is an attribute of a
suite.
Different suites can have different clocks.
There are two kinds of clocks:
...
- Try to modify the suite to run with a clock date from the previous week use :.
use :ecflow_client –alter change clock_date <day>.<month>.<year> /test
i.e ecflow_client –alter change clock_date 1.1.2010 /test - Check the values of the ecFlow variable‘s
- Set the clock to sync back with the computer
ecflow_client –alter change clock_sync /test
Check with:
ecflow_client –get /test | grep clock
| Note |
|---|
- The attributes date, day and clock are currently not usable if you choose to use a repeat date type structure.
- Be aware that cron with a single time dependency will automatically resubmit indefinitely
- Altering the clock, requires that the suite is re-queued
|
