User Tools

Site Tools

Trace:
ecearth_3.2a

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
Last revision Both sides next revision
ecearth_3.2a [2015/12/22 12:24]
macosta created 		ecearth_3.2a [2016/02/09 11:25]
macosta [v3.2a]
Line 3: Line 3:
 Here is below a brief description of the new version release of Ec-Earth model, including the ongoing issues and a brief summary of previous releases. Here is below a brief description of the new version release of Ec-Earth model, including the ongoing issues and a brief summary of previous releases.
  
-===== v3.2a =====+===== v3.2betaa =====
  
-The auto-ecearth3 v3.2a (git submodule connected to SVN and sim using run script) and testing it to be able to submit an experiment with Autosubmit3:+The auto-ecearth3 v3.2betaa (git submodule connected to SVN and sim using run script) and testing it to be able to submit an experiment with Autosubmit3:
  
-  * Unordered List Itembug fixes of v3.1f (in auto-ecearth3.git) and start merging beta_3_2 (which has connection with svn and also have two new tiny jobs called pre-sim and post-sim) into develop+  * Unordered List Itembug fixes of v3.1f (in auto-ecearth3.git) and merging beta_3_2 (which has connection with svn and also have two new tiny jobs called pre-sim and post-sim) into develop
   * revising the platform's configuration and also compilation.cmd   * revising the platform's configuration and also compilation.cmd
-  * test-suite: need to revise, how many configurations are needed etc +  * test-suite: old configurations and new one for ENE4 
-  * sources: tagged v3.2beta can't be used as it is now, but we could use trunk/tuning branch (after Mingu synchronise the runtime/autosubmit and runtime/classic). Here one thing just to keep in mind, under some-branch/trunk/tuning/next-tag if there are modifications under runtime/classic they should need to bring into runtime/autosubmit manually.+  * sources: v3.2beta using autosubmit3. State
   * s2dverification: v2.4.6?   * s2dverification: v2.4.6?
   * spec2cmor: v2.0.1?   * spec2cmor: v2.0.1?
Line 19: Line 19:
  
   * Use of Xios: The XIOS IO server used by NEMO allows to write directly only in one file and to perform operations before the output. The modifications needed to use XIOS servers can be found in develop_HR1 of auto-nemo. (Chloe)   * Use of Xios: The XIOS IO server used by NEMO allows to write directly only in one file and to perform operations before the output. The modifications needed to use XIOS servers can be found in develop_HR1 of auto-nemo. (Chloe)
-  * Initial conditions for EC-Earth 3.2 beta (Domingo)+  * Initial conditions for EC-Earth 3.2 beta (Mingu)
   * Output issue with a022: Why the NEMO is showing a wrong output behaviour when PISCES is activated at MN3 while at Ithaca is correct. (Mario)   * Output issue with a022: Why the NEMO is showing a wrong output behaviour when PISCES is activated at MN3 while at Ithaca is correct. (Mario)
-  * Ecearth run-script to be run from SIM template (Domingo)+  * Ecearth run-script to be run from SIM template (Mingu)
  
 ===== Completed issues ===== ===== Completed issues =====
  
-  * Git submodule connected to SVN (Domingo)+  * Git submodule connected to SVN (Mingu)
  
 ===== Previous versions ===== ===== Previous versions =====
  
-==== V3.1f (Released on Decembre 16, 2015) ====+==== V3.1f (Released on December 16, 2015) ====
  
   * bug fixes of v3.1e (in auto-ecearth3.git)   * bug fixes of v3.1e (in auto-ecearth3.git)
ecearth_3.2a.txt · Last modified: 2016/02/09 13:53 by macosta

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki