Changes between Version 54 and Version 55 of 2009WP/Release_v3.2

Timestamp:

2009-11-24T17:30:37+01:00 (14 years ago)

Author:

rblod

Comment:

--

2009WP/Release_v3.2

@@ -1 @@
-==  * Release v3.2
-
- ==
+== Release v3.2 ==
 === content ===
  * New Physics : tidal mixing ; RGB light penetration + ocean color ;
@@ -17 +15 @@
   Using histwrite is still the default behaviour for safety. Nevertheless, iom_put can be activated with the cpp_key key_iomput and should become the default (only) in the future.
 
-Iom_put  allows to distribute and add desired  output fields  everywhere in the code without specific declaration in diawri : Ex : CALL iom_put( "ssh" , sshn ) in sshwzv It is based on : -        a XML-F90 parser, svn  co http://forge.ipsl.jussieu.fr/ioserver/svn/XMLF90 -        an additional library svn co http://forge.ipsl.jussieu.fr/ioserver/svn/XMLIO_SERVER When using modipsl environment, they are extracting automatically with NEMO. Both are delivered under  GPL licence but not under the responsibility of the NEMO team. Actually two levels of functionalities are available : 1-        Just use iom_put to output the variable easily 2-        Use in addition   dedicated processors for output (server mode), then an additional executable is needed At execution time, when key_iomput has been activated, two additional files are required  (and provided with the standard configuration): -        xmlio_server.def : a namelist to define if we are in server mode or not -        iodef.xml : an xml file to be completed with precision  on the variable called by iom_put in nemo (name for output, frequency, file)  In server mode only, user has to define a mpi configuration file  (for instance mpi.conf) looking like: -p 10 -e ./opa                                 <-------- means 10 cpu for opa -p 2-e ./ioserver                           <--------- means 2 cpu for IO Then mpirun –f mpi.conf IOM for output has been implemented in OPA, TOP, LIM3 and LIM3,  it is tested in NVTK, it is currently not compatible with AGRIF (key_agrif) and not implemented in diaptr.
+Iom_put  allows to distribute and add desired  output fields  everywhere in the code without specific declaration in diawri : Ex : CALL iom_put( "ssh" , sshn ) in sshwzv It is based on : -        a XML-F90 parser, svn  co http://forge.ipsl.jussieu.fr/ioserver/svn/XMLF90 -        an additional library svn co http://forge.ipsl.jussieu.fr/ioserver/svn/XMLIO_SERVER When using modipsl environment, they are extracting automatically with NEMO. Both are delivered under  GPL licence but not under the responsibility of the NEMO team. Actually two levels of functionalities are available : 
+
+1-        Just use iom_put to output the variable easily 
+
+2-        Use in addition   dedicated processors for output (server mode), then an additional executable is needed At execution time, when key_iomput has been activated, two additional files are required  (and provided with the standard configuration): 
+
+-        xmlio_server.def : a namelist to define if we are in server mode or not 
+
+-        iodef.xml : an xml file to be completed with precision  on the variable called by iom_put in nemo (name for output, frequency, file) 
+
+In server mode only, user has to define a mpi configuration file  (for instance mpi.conf) looking like: 
+
+-p 10 -e ./opa                                 <-------- means 10 cpu for opa
+
+ -p 2-e ./ioserver                           <--------- means 2 cpu for IO 
+
+Then mpirun –f mpi.conf IOM for output has been implemented in OPA, TOP, LIM3 and LIM3,  it is tested in NVTK, it is currently not compatible with AGRIF (key_agrif) and not implemented in diaptr.
 
 As a consequence of the code reorganisation, average of output fields have been shift of one time step, for instance with nwrite=5, nit000=1, nitend=10 : Nemo_v3.1: