... | ... | @@ -21,5 +21,10 @@ 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.
|
|
|
* 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.
|
|
|
|
|
|
|
|
|
Further information about all this functionalities and commands can be found at the [Autosubmit documentation](https://autosubmit.readthedocs.io/en/latest/introduction.html). |
|
|
\ No newline at end of file |