... | ... | @@ -23,7 +23,7 @@ The aim of this section is to provide useful **guidelines** about the features t |
|
|
* There is a new **log** (.err, .out, COMPLETED, STAT files) **recover system**, that performs re-tries (in background threads) of the log files transfer from the remote platforms in case of failure.
|
|
|
* The user can specify a `datetime` or `time` to trigger the **experiment start** by sending the `-st` flag (plus the right format) using the `autosubmit run` command.
|
|
|
* The user can specify an **experiment dependency** by providing the `-sa` (plus the right expid format) flag to the `autosubmit run` command. The experiment will start when the experiment specified in the `-sa` flag finishes.
|
|
|
* When the user quits Autosubmit by using the `CTRL+C` keys, Autosubmit will make sure all threads are finished correctly before closing.
|
|
|
* When the user **quits** Autosubmit by using the `CTRL+C` keys, Autosubmit will make sure all threads are finished correctly before closing.
|
|
|
* Job lifecycle information is stored in an **external database** that will allow users to visualize job historical information. This information is gathered in a way that does not interfere with the normal workflow (even if the information gathering fails or any of its components). Furthermore, threading is implemented to prevent unnecessary delays.
|
|
|
* **Specific members** can be selected to run by using the `-rm` flag with `autosubmit run`. Autosubmit will only run jobs belonging to the specified members. Jobs already running will be monitored and properly completed.
|
|
|
* The `git clone` operation (`Autosubmit create`) now implements a **backup procedure** that will prevent loss of information in case of wrong configuration or network error.
|
... | ... | |