Changeset 3977 for trunk/LMDZ.COMMON/libf/evolution/deftank/README

Timestamp:

Nov 26, 2025, 5:06:13 PM (4 weeks ago)

Author:

jbclement

Message:

PEM:

• All operations computed by the PEM on the PCM data (averages, minima) are now performed by XIOS with two dedicated file. One is for daily operation outputs ("Xoutdaily4pem*.nc") and the other for yearly operation outputs ("Xoutyearly4pem*.nc").
• Deletion of the reshaping tool "reshape_XIOS_output" used to convert XIOS outputs onto the PCM grid. Thus, the PEM is now able to read directly the format of XIOS outputs.
• Addition of subroutines to convert data between a lon x lat array and a vector.

JBC

File:

• trunk/LMDZ.COMMON/libf/evolution/deftank/README (modified) (5 diffs)

trunk/LMDZ.COMMON/libf/evolution/deftank/README

@@ -17 +17 @@
 Installation:
 -------------
-The PEM can be downloaded alongside the "LMDZ.COMMON" repository of your trunk. The Fortran code is in the following directory: "trunk/LMDZ.COMMON/libf/evolution/". The two PEM programs are "pem.F90" and "reshape_XIOS_output.F90".
+The PEM can be downloaded alongside the "LMDZ.COMMON" repository of your trunk. The Fortran code is in the following directory: "trunk/LMDZ.COMMON/libf/evolution/". The PEM main program is "pem.F90".
 
 Compilation:
@@ -26 +26 @@
     2) [planet]    : mars to use the Mars planet physics package; 
     3) [dimensions]: 64x48x54 to define the grid you want to use  (longitude x latitude x atmospheric layers).
-To run the PEM, you need a dedicated reshaping tool with consistent options. To compile it, in "LMDZ_COMMON", do: ./makelmdz_fcm -arch [local] -p [planet] -d [dimensions] -j 8 reshape_XIOS_output
-To run the PEM, you also need a PCM working with XIOS and consistent options. To compile it, in "LMDZ.COMMON", do: ./makelmdz_fcm -arch [local] -p [planet] -parallel mpi_omp -io xios -d [dimensions] -j 8 gcm
+To run the PEM, you need a PCM working with XIOS and consistent options. To compile it, in "LMDZ.COMMON", do: ./makelmdz_fcm -arch [local] -p [planet] -parallel mpi_omp -io xios -d [dimensions] -j 8 gcm
 After compilation, the executable file can be found in the "bin" sub-directory.
 
@@ -42 +41 @@
 -------------
 To run the PEM, you can create a folder in which you need the following files:
-    > your executable files for the PCM, the PEM and the reshaping tool with consistent options;
+    > your executable files for the PCM and the PEM with consistent options;
     > the xml files for XIOS which can be found in the PCM deftank folder: "iodef.xml", "context_lmdz_physics.xml", "file_def_physics_mars.xml" and "field_def_physics_mars.xml";
     > the def files you want to run the PCM: "run.def", "callphys.def", "traceur.def", etc.
@@ -63 +62 @@
 The PEM simulation generates the following files:
     > the usual outputs of the PCM: "restartfi.nc", "restart.nc", "diagfi.nc", etc;
-    > the XIOS outputs of the PCM, then reshaped: "Xdiurnalave.nc"/"data2reshape*.nc"/"data_PCM_Y*.nc";
+    > the XIOS outputs of the PCM: "Xoutdaily4pem*.nc"/"Xoutyearly4pem*.nc";
     > the outputs of the chained simulation: "launchPEM.log", "info_PEM.txt" and possibly "kill_launchPEM.sh";
     > the usual outputs of the PEM: "restartfi.nc", "restart.nc"/"restart1D.txt" and "diagpem.nc".
@@ -99 +98 @@
       > The headers correspond to the ADASTRA supercomputer and should be changed for other machines and job schedulers. In case of "processing scripts" launching mode, the headers are naturally omitted.
       > The path to source the arch file should be adapted to the machine.
-      > The name of the PEM and Reshaping executable files should be adapted.
+      > The name of the PEM executable file should be adapted.
       > The PEM executable can have an optional argument which should be specified according to the set-up ("--auto-exit" for SLURM and PBS/TORQUE | "" when the script is not run as a job).