LMDZ Setup - Historique des versions

Abarral le 13 décembre 2024 à 10:34

2024-12-13T10:34:52Z

Abarral le 10 septembre 2024 à 10:21

2024-09-10T10:21:33Z

Abarral le 9 septembre 2024 à 10:48

2024-09-09T10:48:45Z

Abarral : remove obsolete root_dir comment

2024-09-09T09:38:11Z

remove obsolete root_dir comment

Abarral : Add HowTo category

2024-07-16T16:47:49Z

Add HowTo category

Abarral : Add information regarding new LMDZ_Setup

2024-07-09T07:45:04Z

Add information regarding new LMDZ_Setup

Abarral : (WIP) Add information regarding new LMDZ_Setup

2024-07-09T07:26:04Z

(WIP) Add information regarding new LMDZ_Setup

Abarral : add todo

2024-07-08T14:52:07Z

add todo

Abarral : typo

2024-07-08T14:51:06Z

typo

Abarral : (WIP) Add information regarding new LMDZ_Setup

2024-07-08T14:48:13Z

(WIP) Add information regarding new LMDZ_Setup

@@ Ligne 67 : / Ligne 67 : @@
 === Downloading LMDZ_Setup ===
-  /!\ Note: below is for when the new version will replace the old one - for now, use <code>svn co https://svn.lmd.jussieu.fr/LMDZ/BOL/LMDZ_Setup_amaury</code>
+  /!\ Note: below is for when the new version will replace the old one - for now, use <code>svn co http://svn.lmd.jussieu.fr/LMDZ/BOL/LMDZ_Setup_amaury</code>
-* ''(recommended)'' Using ''subversion'': <code>svn co https://svn.lmd.jussieu.fr/LMDZ/BOL/LMDZ_Setup</code>
+* ''(recommended)'' Using ''subversion'': <code>svn co http://svn.lmd.jussieu.fr/LMDZ/BOL/LMDZ_Setup</code>
-* ''(alternative)'' <code>wget https://lmdz.lmd.jussieu.fr/pub/Training/LMDZ_Setup.tar</code>
+* ''(alternative)'' <code>wget http://lmdz.lmd.jussieu.fr/pub/Training/LMDZ_Setup.tar</code>
-* ''(deprecated)'' The old <code>tutorial_prod</code> version: <code>wget https://lmdz.lmd.jussieu.fr/pub/Training/tutorial_prod.tar</code>
+* ''(deprecated)'' The old <code>tutorial_prod</code> version: <code>wget http://lmdz.lmd.jussieu.fr/pub/Training/tutorial_prod.tar</code>
 === Structure ===

@@ Ligne 133 : / Ligne 133 : @@
 The officially supported versions of ORCHIDEE supported by LMDZ_Setup are:
-* the CMIP6 version (still using the two-layer hydrology channel)
+* the CMIP6 version (the last version where the use of the old two-layer hydrology is still possible)
 * version 2.2 r7983
 * version 4 (trunk) r7994 (corresponding to libIGCM's LMDZOR_6.4work configuration)

← Version précédente		Version du 9 septembre 2024 à 10:48
Ligne 66 :		Ligne 66 :

	=== Downloading LMDZ_Setup ===		=== Downloading LMDZ_Setup ===
		+
		+	/!\ Note: below is for when the new version will replace the old one - for now, use <code>svn co https://svn.lmd.jussieu.fr/LMDZ/BOL/LMDZ_Setup_amaury</code>

	* ''(recommended)'' Using ''subversion'': <code>svn co https://svn.lmd.jussieu.fr/LMDZ/BOL/LMDZ_Setup</code>		* ''(recommended)'' Using ''subversion'': <code>svn co https://svn.lmd.jussieu.fr/LMDZ/BOL/LMDZ_Setup</code>

@@ Ligne 81 : / Ligne 81 : @@
 # '''Edit <code>lmdz_env.sh</code>.''' In <code>lmdz_env.sh</code>, in the function <code>set_env</code>, find the case corresponding to your supercomputer: <code>jean-)</code> for JeanZay, <code>spiri)</code> for Spirit, <code>adast)</code> for Adastra. Edit the variables required for your use case. All the variables are documented in the last <code>*)</code> case. In particular:
 # '''Edit <code>main.sh</code>.''' In <code>main.sh</code>, edit all relevant settings.
 # '''''[optional]'' Edit <code>setup.sh</code>.''' In <code>setup.sh</code>, in the function <code>define_expert_options</code>, edit all relevant settings.

← Version précédente		Version du 16 juillet 2024 à 16:47
Ligne 206 :		Ligne 206 :

	Compilation of the various components of the model, in particular of LMDZ and XIOS, is extremely slow on JeanZay compared to other clusters (for unknown reasons) (~15 minutes for LMDZ+rrtm). Moreover, it seems that for uninvestigated reasons, the LMDZ model is systematically recompiled on each call to <code>main.sh</code> (expected behavior, as on other clusters: the <code>fcm</code> system detects that it's already compiled and avoids compiling again). As a result, the whole process of '''launching a simulation is much slower'''.		Compilation of the various components of the model, in particular of LMDZ and XIOS, is extremely slow on JeanZay compared to other clusters (for unknown reasons) (~15 minutes for LMDZ+rrtm). Moreover, it seems that for uninvestigated reasons, the LMDZ model is systematically recompiled on each call to <code>main.sh</code> (expected behavior, as on other clusters: the <code>fcm</code> system detects that it's already compiled and avoids compiling again). As a result, the whole process of '''launching a simulation is much slower'''.
		+
		+	[[Category:HowTo]]

@@ Ligne 50 : / Ligne 50 : @@
-== WIP - Migration de LMDZ_Setup_HowTo + inclusion nouveau LMDZ_Setup ==
+== Below: new LMDZ_Setup docs ==
 ''Old documentation (French): [https://docs.google.com/document/d/1OLZG6e-86NiXuv5-aALxKIh-QPkp4BdCwWtiBFot-6c LMDZ_Setup_HowTo]''
@@ Ligne 159 : / Ligne 158 : @@
 ''Note: for isotopes, <code>iflag_ice_thermo</code> is automatically set to <code>0</code> instead of <code>1</code>.''
 == Cluster-specific information ==

@@ Ligne 105 : / Ligne 105 : @@
 ==== Compilation ====
-When launching <code>main.sh</code>, before launching the simulation, we first download and compile the required models. Although we call the compilation script every time, if the model has already been compiled before, the script should detect that and skip the actual compilation, and thus execute very quickly.
+When launching <code>main.sh</code>, before running the simulation, we first download and compile the required models. Although we call the compilation script every time, if the model has already been compiled before, the script should detect that and skip the actual compilation, and thus execute very quickly.
   '''/!\''' As written in the comments of <code>main.sh/setup.sh</code>, '''if you change the <code>veget</code> version or the <code>aerosols</code>, it is highly recommended to do so in a NEW clean <code>LMDZ_Setup</code> folder''' rather than recompiling in the same folder.
 == Cluster-specific information ==

@@ Ligne 52 : / Ligne 52 : @@
 == WIP - Migration de LMDZ_Setup_HowTo + inclusion nouveau LMDZ_Setup ==
-''TODO Amaury: reprendre à "SSTs et SIC" + vérifier réponse Adriana pour xios+omp>2
+''TODO Amaury: reprendre à "SSTs et SIC" + vérifier réponse Adriana pour xios+omp>2 + rajouter commentaire compilation dans jobs dans section "compilation"
 ''Old documentation (French): [https://docs.google.com/document/d/1OLZG6e-86NiXuv5-aALxKIh-QPkp4BdCwWtiBFot-6c LMDZ_Setup_HowTo]''

@@ Ligne 51 : / Ligne 51 : @@
 == WIP - Migration de LMDZ_Setup_HowTo + inclusion nouveau LMDZ_Setup ==
 ''Old documentation (French): [https://docs.google.com/document/d/1OLZG6e-86NiXuv5-aALxKIh-QPkp4BdCwWtiBFot-6c LMDZ_Setup_HowTo]''
-=== Downloading LMDZ_Setup ===
+== User guide ==
-  ''' /!\ WARNING''' 06/2024
+  ''' /!\ WARNING''' 06/2024 - (ignore if installing a new version)
   The JeanZay calculator, as well as Adastra, do not allow (anymore) communication from/to $STORE for running jobs on the main computing partitions.
   As a result, make sure to replace $STORE by $WORK in <code>lmdz_env.sh</code> wherever relevant.
@@ Ligne 70 : / Ligne 66 : @@
   ''Note'': <code>LMDZ_Setup</code> has been tested on Adastra and Spirit, and to a lesser extent on JeanZay (legacy support only). No guarantee is made on other platforms, although it should be easy to adapt it. It can also be ran locally - for expert use only.
-==== Structure ====
+=== Downloading LMDZ_Setup ===
 Once you have downloaded <code>LMDZ_Setup</code>, you will find the following main files:
@@ Ligne 77 : / Ligne 79 : @@
 * <code>lmdz_env.sh</code>: this file contains platform-specific configuration, such as where to install the model, where to run the simulations, etc.
-==== How to run a simulation ====
+=== How to run a simulation ===
 # '''Edit <code>lmdz_env.sh</code>.''' In <code>lmdz_env.sh</code>, in the function <code>set_env</code>, find the case corresponding to your supercomputer: <code>jean-)</code> for JeanZay, <code>spiri)</code> for Spirit, <code>adast)</code> for Adastra. Edit the variables required for your use case. All the variables are documented in the last <code>*)</code> case. In particular:
@@ Ligne 85 : / Ligne 87 : @@
 # '''''[optional]'' Edit <code>DEF/*</code>.''' Edit the <code>DEF/*.def</code> or <code>DEF/XMLfiles*</code> files, such as <code>config.def</code>, to your liking. ''The options you specify in main.sh/setup.sh don't require any adjustment here; such adjustments are automatically performed at runtime.''
 # '''Launch <code>main.sh</code>'''.