LMDZ.COMMON directory layout and contents - Revision history

Martin.turbet at 09:08, 4 February 2026

2026-02-04T09:08:48Z

Emillour at 22:27, 2 August 2024

2024-08-02T22:27:08Z

Emillour at 12:34, 27 May 2023

2023-05-27T12:34:31Z

Martin.turbet at 10:13, 9 March 2023

2023-03-09T10:13:34Z

Emillour at 15:19, 5 August 2022

2022-08-05T15:19:11Z

Emillour at 15:18, 5 August 2022

2022-08-05T15:18:18Z

Emillour at 15:10, 5 August 2022

2022-08-05T15:10:18Z

Emillour at 10:42, 28 July 2022

2022-07-28T10:42:22Z

Emillour at 10:27, 28 July 2022

2022-07-28T10:27:44Z

Emillour: Created page with "This page describes the directory structure of the LMDZ longitude-latitude dynamical core and its main contents == The ''LMDZ.COMMON'' directory == Once download from the svn..."

2022-07-27T16:14:28Z

Created page with "This page describes the directory structure of the LMDZ longitude-latitude dynamical core and its main contents == The ''LMDZ.COMMON'' directory == Once download from the svn..."

New page

This page describes the directory structure of the LMDZ longitude-latitude dynamical core and its main contents

== The ''LMDZ.COMMON'' directory ==
Once download from the svn server, the ''LMDZ.COMMON'' directory contents should be:
<pre>
arch create_make_gcm Licence_CeCILL_V2-en.txt makelmdz
bld.cfg ioipsl Licence_CeCILL_V2-fr.txt makelmdz_fcm
build_gcm libf makegcm
</pre>
Where the noteworthy elements are:
* The <font color="green">makelmdz_fcm</font> script, which is required to compile the model; see [[The_makelmdz_fcm_GCM_Compilation_Script|the dedicated page]]
* The ''arch'' directory which contains architecture files used by the ''makelmdz_fcm'' script
* The ''ioipsl'' directory which contains some scripts to assist one in installing the IOIPSL library
* The ''libf'' directory which contains the Fortran source code (see below).

== The ''libf'' subdirectory ==
TODO...DESCRIBE VARIOUS DIRS AND CONNECTION WITH PHYSICS PACKAGES

@@ Line 17: / Line 17: @@
 <pre>
 aeronomars  dyn3d         dynphy_lonlat  misc        phymars   phyvenus
-aeronostd   dyn3d_common  filtrez        muphytitan  phystd
+aeronostd   dyn3d_common  filtrez        muphytitan  phygeneric
 chimtitan   dyn3dpar      grid           phy_common  phytitan
 </pre>
 The general idea here is that there is both a clean (and hopefully clear) separation between dynamics, physics and interfaces between the two. In addition to this principle comes the fact that there are various physics packages (Mars, Venus, Titan, Generic) and that the dynamical core comes in two flavors, serial and parallel. One can thus identify the following groups:
 * "dynamics"-related directories: <font color="orange">dyn3d</font>: routines specific to the serial dynamical core, <font color="orange">dy3dpar</font>: routines specific to the parallel dynamical core, <font color="orange">dyn3d_common</font>: routines used by both serial and parallel dynamical cores. In addition <font color="orange">grid</font> and <font color="orange">filtrez</font> directories also contain routines used by the dynamical cores and respectively related to the (horizontal) grid and polar filter.
-* "physics"-related directories: links to physics directories specific to the various physics packages (e.g. <font color="orange">phystd</font> and <font color="orange">aeronostd</font> are respectively links to the Generic physics <font color="orange">../../LMDZ.GENERIC/libf/phystd</font> and <font color="orange">../../LMDZ.GENERIC/libf/aeronostd</font> directories), along with <font color="orange">phy_common</font>, a directory containing routines common to all the physics packages.
+* "physics"-related directories: links to physics directories specific to the various physics packages (e.g. <font color="orange">phygeneric</font> and <font color="orange">aeronostd</font> are respectively links to the Generic physics <font color="orange">../../LMDZ.GENERIC/libf/phygeneric</font> and <font color="orange">../../LMDZ.GENERIC/libf/aeronostd</font> directories), along with <font color="orange">phy_common</font>, a directory containing routines common to all the physics packages.
 * <font color="orange">dynphy_lonlat</font>: directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both. In addition, it also hosts some pre/post processing utilities (e.g. newstart, start2archive) which need access both the LMDZ.COMMON (lon-lat) dynamics and relevant physics packages.
 * <font color="orange">misc</font>: this directory contains miscellaneous routines which may be used either by the dynamics or physics but which rely on neither.

@@ Line 23: / Line 23: @@
 * "dynamics"-related directories: <font color="orange">dyn3d</font>: routines specific to the serial dynamical core, <font color="orange">dy3dpar</font>: routines specific to the parallel dynamical core, <font color="orange">dyn3d_common</font>: routines used by both serial and parallel dynamical cores. In addition <font color="orange">grid</font> and <font color="orange">filtrez</font> directories also contain routines used by the dynamical cores and respectively related to the (horizontal) grid and polar filter.
 * "physics"-related directories: links to physics directories specific to the various physics packages (e.g. <font color="orange">phystd</font> and <font color="orange">aeronostd</font> are respectively links to the Generic physics <font color="orange">../../LMDZ.GENERIC/libf/phystd</font> and <font color="orange">../../LMDZ.GENERIC/libf/aeronostd</font> directories), along with <font color="orange">phy_common</font>, a directory containing routines common to all the physics packages.
-* <font color="orange">dynphy_lonlat</font>: directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both.
+* <font color="orange">dynphy_lonlat</font>: directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both. In addition, it also hosts some pre/post processing utilities (e.g. newstart, start2archive) which need access both the LMDZ.COMMON (lon-lat) dynamics and relevant physics packages.
 * <font color="orange">misc</font>: this directory contains miscellaneous routines which may be used either by the dynamics or physics but which rely on neither.

← Older revision		Revision as of 10:13, 9 March 2023
Line 26:		Line 26:
	* <font color="orange">dynphy_lonlat</font>: directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both.		* <font color="orange">dynphy_lonlat</font>: directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both.
	* <font color="orange">misc</font>: this directory contains miscellaneous routines which may be used either by the dynamics or physics but which rely on neither.		* <font color="orange">misc</font>: this directory contains miscellaneous routines which may be used either by the dynamics or physics but which rely on neither.
		+
		+	[[Category:Generic-Model]]
		+	[[Category:Mars-Model]]
		+	[[Category:Venus-Model]]
		+	[[Category:Titan-Model]]

@@ Line 21: / Line 21: @@
 chimtitan   dyn3dpar      grid           phy_common  phytitan
 </pre>
-The general idea here is that there is both a clean (and hopefully clear) separation between dynamics, physics and interfaces between the two. In addition to this principle comes the fact that there are various physics packages (Mars, Venus, Titan, Generic) and that the dynamical core comes in two flavors, serial and parallel. Once can thus identify the following groups:
+The general idea here is that there is both a clean (and hopefully clear) separation between dynamics, physics and interfaces between the two. In addition to this principle comes the fact that there are various physics packages (Mars, Venus, Titan, Generic) and that the dynamical core comes in two flavors, serial and parallel. One can thus identify the following groups:
 * "dynamics"-related directories: <font color="orange">dyn3d</font>: routines specific to the serial dynamical core, <font color="orange">dy3dpar</font>: routines specific to the parallel dynamical core, <font color="orange">dyn3d_common</font>: routines used by both serial and parallel dynamical cores. In addition <font color="orange">grid</font> and <font color="orange">filtrez</font> directories also contain routines used by the dynamical cores and respectively related to the (horizontal) grid and polar filter.
 * "physics"-related directories: links to physics directories specific to the various physics packages (e.g. <font color="orange">phystd</font> and <font color="orange">aeronostd</font> are respectively links to the Generic physics <font color="orange">../../LMDZ.GENERIC/libf/phystd</font> and <font color="orange">../../LMDZ.GENERIC/libf/aeronostd</font> directories), along with <font color="orange">phy_common</font>, a directory containing routines common to all the physics packages.
 * <font color="orange">dynphy_lonlat</font>: directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both.
 * <font color="orange">misc</font>: this directory contains miscellaneous routines which may be used either by the dynamics or physics but which rely on neither.

@@ Line 1: / Line 1: @@
 This page describes the directory structure of the LMDZ longitude-latitude dynamical core and its main contents
-== The ''LMDZ.COMMON'' directory ==
+== The <font color="orange">LMDZ.COMMON</font> directory ==
 Once download from the svn server, the ''LMDZ.COMMON'' directory contents should be:
 <pre>
@@ Line 10: / Line 10: @@
 Where the noteworthy elements are:
 * The <font color="green">makelmdz_fcm</font> script, which is required to compile the model; see [[The_makelmdz_fcm_GCM_Compilation_Script|the dedicated page]]
-* The ''arch'' directory which contains architecture files used by the <font color="green">makelmdz_fcm</font> script
+* The <font color="orange">arch</font> directory which contains architecture files used by the <font color="green">makelmdz_fcm</font> script
-* The ''ioipsl'' directory which contains some scripts to assist one in installing the IOIPSL library
+* The <font color="orange">ioipsl</font> directory which contains some scripts to assist one in installing the IOIPSL library
-* The ''libf'' directory which contains the Fortran source code (see below).
+* The <font color="orange">libf</font> directory which contains the Fortran source code (see below).
-== The ''libf'' subdirectory ==
+== The <font color="orange">libf</font> subdirectory ==
-The ''libf'' directory contains a mix of subdirectories or links to subdirectories:
+The <font color="orange">libf</font> directory contains a mix of subdirectories or links to subdirectories:
 <pre>
 aeronomars  dyn3d         dynphy_lonlat  misc        phymars   phyvenus
@@ Line 22: / Line 22: @@
 </pre>
 The general idea here is that there is both a clean (and hopefully clear) separation between dynamics, physics and interfaces between the two. In addition to this principle comes the fact that there are various physics packages (Mars, Venus, Titan, Generic) and that the dynamical core comes in two flavors, serial and parallel. Once can thus identify the following groups:
-* "dynamics"-related directories: ''dyn3d'': routines specific to the serial dynamical core, ''dy3dpar'': routines specific to the parallel dynamical core, ''dyn3d_common'': routines used by both serial and parallel dynamical cores. In addition '' grid'' and ''filtrez'' directories also contain routines used by the dynamical cores and respectively related to the (horizontal) grid and polar filter.
+* "dynamics"-related directories: <font color="orange">dyn3d</font>: routines specific to the serial dynamical core, <font color="orange">dy3dpar</font>: routines specific to the parallel dynamical core, <font color="orange">dyn3d_common</font>: routines used by both serial and parallel dynamical cores. In addition <font color="orange">grid</font> and <font color="orange">filtrez</font> directories also contain routines used by the dynamical cores and respectively related to the (horizontal) grid and polar filter.
-* "physics"-related directories: links to physics directories specific to the various physics packages (e.g. ''phystd'' and ''aeronostd'' are respectively links to the Generic physics ''../../LMDZ.GENERIC/libf/phystd'' and ''../../LMDZ.GENERIC/libf/aeronostd'' directories), along with ''phy_common'', a directory containing routines common to all the physics packages.
+* "physics"-related directories: links to physics directories specific to the various physics packages (e.g. <font color="orange">phystd</font> and <font color="orange">aeronostd</font> are respectively links to the Generic physics <font color="orange">../../LMDZ.GENERIC/libf/phystd</font> and <font color="orange">../../LMDZ.GENERIC/libf/aeronostd</font> directories), along with <font color="orange">phy_common</font>, a directory containing routines common to all the physics packages.
-* ''dynphy_lonlat'': directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both.
+* <font color="orange">dynphy_lonlat</font>: directory which contains the interface between the (lon-lat) dynamical core and physics packages, i.e routines which are thus connected to both.
-* ''misc'': this directory contains miscellaneous routines which may be used either by the dynamics or physics but which rely on neither.
+* <font color="orange">misc</font>: this directory contains miscellaneous routines which may be used either by the dynamics or physics but which rely on neither.

@@ Line 4: / Line 4: @@
 Once download from the svn server, the ''LMDZ.COMMON'' directory contents should be:
 <pre>
-arch       create_make_gcm  Licence_CeCILL_V2-en.txt  makelmdz
+arch     build_gcm        ioipsl  Licence_CeCILL_V2-en.txt  makelmdz
-bld.cfg    ioipsl           Licence_CeCILL_V2-fr.txt  makelmdz_fcm
+bld.cfg  create_make_gcm  libf    Licence_CeCILL_V2-fr.txt  makelmdz_fcm
 </pre>
 Where the noteworthy elements are:

← Older revision		Revision as of 10:27, 28 July 2022
Line 15:		Line 15:

	== The ''libf'' subdirectory ==		== The ''libf'' subdirectory ==
−	~~TODO~~...~~DESCRIBE VARIOUS DIRS AND CONNECTION WITH PHYSICS PACKAGES~~	+	The ''libf'' directory contains a mix of subdirectories or links to subdirectories:
		+	<pre>
		+	aeronomars dyn3d dynphy_lonlat misc phymars phyvenus
		+	aeronostd dyn3d_common filtrez muphytitan phystd
		+	chimtitan dyn3dpar grid phy_common phytitan
		+	</pre>
		+	The general idea here is that there is both a clean (and hopefully clear) separation between dynamics, physics and interfaces between the two. In addition to this principle comes the fact that there are various physics packages (Mars, Venus, Titan, Generic) and that the dynamical core comes in two flavors, serial and parallel. Once can thus identify the following groups:
		+	* "dynamics"-related directories: ''dyn3d'': routines specific to the serial dynamical core, ''dy3dpar'': routines specific to the parallel dynamical core, ''dyn3d_common'': routines used by both serial and parallel dynamical cores. In addition '' grid'' and ''filtrez'' directories also contain routines used by the dynamical cores and respectively related to the (horizontal) grid and polar filter.
		+	* "physics"-related directories: links to physics directories specific to the various physics packages (e.g. ''phystd'' and ''aeronostd'' are respectively links to the Generic physics ''../../LMDZ.GENERIC/libf/phystd'' and ''../../LMDZ.GENERIC/libf/aeronostd'' directories), along with ''phy_common'', a directory containing routines common to all the physics packages.
		+	* ''misc'': this directory contains miscelaneous routines which may be used either by the dynamics or physics but which rely on neither.