... | ... | @@ -24,7 +24,9 @@ The aim of this section is to provide useful **guidelines** about the features t |
|
|
* 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.
|
|
|
* 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.
|
|
|
*
|
|
|
|
|
|
|
|
|
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 |