Common Autosubmit commands#
Command |
Description |
Autosubmit documentation |
|---|---|---|
expid |
Add a new experiment to the database and create the corresponding directory. |
|
create |
Read the configuration and create the workflow for the experiment. |
|
run |
Run the workflow. Usually this is called in the background. |
|
monitor |
Use this to get the current status of the workflow. Works both when the workflow is running (i.e. an |
|
setstatus |
Set the status of one or multiple jobs. This is useful e.g. if a job failed, you fixed the problem and now you want to start from there again. Some examples are below |
|
inspect |
Create all the scripts for the configured jobs and places them in the |
|
refresh |
Update the project repository. |
|
recovery |
If something went horribly wrong and your workflow is in an ill-defined state, use this to recover your experiment. |
Setting job status#
You can set the status of arbitrary jobs in your workflow to an arbitrary value (e.g. WAITING, READY or COMPLETED) by using the autosubmit setstatus command. A few examples shall illustrate common use cases:
Set all failed jobs in your workflow to WAITING (e.g. to re-run the jobs):
autosubmit setstatus <expid> -fs FAILED -t WAITING -s -np
Set all RUN_ICON jobs in your workflow to WAITING (e.g. to re-run the jobs):
autosubmit setstatus <expid> -ft RUN_ICON -t WAITING -s -np
Set the BUILD_ICON and BUILD_PYTHON jobs in your workflow to COMPLETED (e.g. because they were running successfully already but you had to run autosubmit create again):
autosubmit setstatus <expid> -ft "BUILD_ICON BUILD_PYTHON" -t COMPLETED -s -np
Suspend job t001_2004010100_default_1_RUN_ICON of expid t001 to delay execution:
autosubmit setstatus t001 -fl t001_2004010100_default_1_RUN_ICON -t SUSPENDED -s -np
Further details can be found in the official documentation.