|
|
|
== Introduction ==
|
|
|
|
|
|
|
|
Originally, Autosubmit consisted in one perl script (written by Xavi Abellan*) and could submit to the queue a sequence of jobs with different parameters.
|
|
|
|
All the jobs had a common template and autosubmit would fill this template with different parameters value and submit the jobs to the queue.
|
|
|
|
Autosubmit would act as a wrapper around the scheduler, monitoring the number of jobs submitted or queuing and would submit a new one as soon as a space in the queue would appear until the entire sequence of jobs is submitted.
|
|
|
|
|
|
|
|
This concept has been kept for the current Python version of Autosubmit with a few capabilities added.
|
|
|
|
The most interesting added capability is that Autosubmit can now deal with the dependency between jobs. (i.e.: it can wait for a particular job to finish before launching the next one)
|
|
|
|
Autosubmit can manage different type of job with different templates.
|
|
|
|
Autosubmit can also restart a failed job, stop the submission process and restart where it left it.
|
|
|
|
New object oriented design and refactoring of Python code has been done in Autosubmit and now there is a new module to create experiments from scratch and store small information into a SQLite database.
|
|
|
|
Thanks to this, there is also the possibility to create, manage and monitor different types of experiments and to tackling with different queue schedulers.
|
|
|
|
|
|
|
|
{{file:scheduler.png}}
|
|
|
|
|
