... | ... | @@ -12,8 +12,8 @@ The aim of this section is to provide useful **guidelines** about the features t |
|
|
* Due to **technical limitations**, we don't recommend to run experiments having many startdates/members (increased concurrency) or very large wrappers with 3.12.0b. As a rule of thumb, experiments with more than 10-20 members in total or wrappers with more than 50 jobs (the user can always reduce the wrapper size) may experience delays in the Autosubmit refresh cycle and generating the monitor views.
|
|
|
* In this version, inner jobs inside QUEUING wrappers show a SUBMITTED status. This is fixed in 3.13.0.
|
|
|
* Autosubmit **migrate** is not secured for big experiments, so it is recommended to backup the offered experiment (in the remote platforms) first. We encourage to use only 3.13.0 migrate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* **3.13.0** - This has been the Autosubmit development version for many months, so it provides a lot of improvements, especially in terms of efficiency and stability. It also brings a full refactor of the wrapper module.
|
|
|
* **Multi-threaded** wrappers were introduced in this version.
|
|
|
* It provides the possibility to specify **multiple hosts** for the same platform (in a list) so it is more robust against connection issues/login failures.
|
... | ... | |