Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • autosubmit autosubmit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 338
    • Issues 338
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • autosubmitautosubmit
  • Wiki
  • versions

versions · Changes

Page history
Update versions authored Mar 09, 2021 by dbeltran's avatar dbeltran
Hide whitespace changes
Inline Side-by-side
versions.md
View page @ e541563e
......@@ -11,7 +11,7 @@ The aim of this section is to provide useful **guidelines** about the features t
* **Horizontal-vertical** wrappers are supported too. They were first developed in this Autosubmit version and they have been used in production together.
* 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.
* 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 versions for many months, so it provides a lot of improvements, specially in terms of efficiency and stability. It also brings a full refactor of the wrappers module.
* **Multi-threaded** wrappers were introduced in this version.
......@@ -31,6 +31,6 @@ The aim of this section is to provide useful **guidelines** about the features t
* Added `autosubmit dbfix expid` command that allows users to fix the `database malformed` error.
* Custom shebang (header of the script templates) so it is possible to use Python or R templates with a specific Python/R version dependency, for example.
* Workflow updates: A difference of 3.12.0 version, in this one, only Create and run commands can regenerate the configuration, workflow and structure information. In case of run, only will be updated if a change is detected before the starting of the main run loop.
* Improves into failure tolerance, in this version AS will try to prevent as many errors as possible at the beginning of the run and other delicate operations, instead of detecting them while in running time.
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
Clone repository
  • Code coverage
  • Deployment
  • Issues documenting different aspects
  • Leaflet
  • Possible Operational Problems and Solutions
  • Running Autosubmit in Earth Sciences
  • Testing_Suite
  • Updating ReadTheDocs Autosubmit documentation
  • Visual Identity
  • [DestinE] Autosubmit VM on Lumi
  • background
  • bibtex
  • databases
  • development
  • dissemination
View All Pages