... | ... | @@ -21,13 +21,13 @@ The aim of this section is to provide useful **guidelines** about the features t |
|
|
* Workflows have more **flexibility** by the inclusion of a new way to define dependencies for specific chunks.
|
|
|
* Changes were made to the algorithm that handles the maximum active jobs by platform. From this version, **wrapped jobs** count as a **single job** for Autosubmit, and the maximum number of inner jobs can be defined with new wrapper parameters.
|
|
|
* 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` when the experiment should start by sending the `-st` flag (plus the right format) using the `autosubmit run` command.
|
|
|
* The user can specify an experiment dependency by sending the `-sa` (plus the right expid format) using the `autosubmit run` command. The experiment will start when the experiment specified in the `-sa` flag finishes.
|
|
|
* The user can specify a `datetime` or `time` when the **experiment should start** by sending the `-st` flag (plus the right format) using the `autosubmit run` command.
|
|
|
* The user can specify an **experiment dependency** by sending the `-sa` (plus the right expid format) using 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.
|
|
|
* Job lifecycle information is stored in an external database that will allow the user to see the historical information of the execution of the jobs in her experiment. 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 now be configured to run by using the `autosubmit run` together with the `-rm` command. By setting this flag, Autosubmit will only run jobs belonging to the supplied members. Jobs that were running before this command was sent, will be monitored and properly completed.
|
|
|
* Job lifecycle information is stored in an **external database** that will allow the user to see the historical information of the execution of the jobs in her experiment. 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 now be configured to run by using the `autosubmit run` together with the `-rm` command. By setting this flag, Autosubmit will only run jobs belonging to the supplied members. Jobs that were running before this command was sent, will be monitored and properly completed.
|
|
|
* The git clone operation now implements a backup procedure that will prevent loss of information in case of wrong configuration or network error.
|
|
|
* There is an improvement of the security, now all commands that could change the workflow are locked by an owner-only mechanism. Ej: create,refresh and run.
|
|
|
* There is an improvement of the **security**, now all commands that could change the workflow are locked by an owner-only mechanism. Ej: create,refresh and run.
|
|
|
* Added `autosubmit dbfix expid` command that allows users to fix the `database malformed` error.
|
|
|
* Custom shebang (header of the script templates) so it is possible to use Python or R templates with a specific Python/R version dependency, for example.
|
|
|
|
... | ... | |