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

Timestamp:

Mar 9, 2026, 10:29:53 AM (8 days ago)

Author:

jbclement

Message:

PEM:

• Introduction of a configurable display/logging system with options 'out2term', 'out2log', 'verbosity_lvl'. All messages now use verbosity levels ('LVL_NFO', 'LVL_WRN', 'LVL_ERR' and 'LVL_DBG').
• Code encapsulation improvements with systematic privacy/protection of module variables.
• Addition of workflow safety checks for required executables, dependencies (e.g. 'ncdump'), input files and callphys keys.
• Renaming of PEM starting and diagnostic files ("startevol.nc" into "startevo.nc", "diagevol.nc" into "diagevo.nc").

JBC

File:

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

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

@@ -47 +47 @@
     > the starting files you want to run the PCM: "startfi.nc" and "start.nc"/"start1D.txt";
     > the necessary PEM files: "pem_workflow.sh", "pem_workflow_lib.sh", "pcm_run.job", "pem_run.job", "run_pem.def" and "obl_ecc_lsp.asc";
-    > the optional PEM files: "diagevol.def" to define the PEM variables to be ouputted and "startevol.nc" to set the initial state of the PEM.
+    > the optional PEM files: "diagevo.def" to define the PEM variables to be ouputted and "startevo.nc" to set the initial state of the PEM.
 
 The PEM files can be found in the deftank folder.
@@ -55 +55 @@
     > "pcm_run.job" (see below for details);
     > "pem_run.job" (see below for details);
-    > def files, especially for "run_pem.def", "run_pcm.def" and "callphys.def" which must be consistent. In particular, "run_pem.def" needs to include some definitions for the physics in file "run_pcm.def" with "INCLUDEDEF=run_pcm.def".
+    > def files, especially for "run_pem.def", "run_pcm.def" and "callphys.def" which must be consistent. In particular, "run_pem.def" needs to include some definitions in file "run_pcm.def" and "callphys.def" with "INCLUDEDEF=run_pcm.def".
 In addition, the user has to provide a "startfi.nc" whose orbital parameters are consistent with the initial date set in "run_pem.def". The script "ini_pem_orbit.sh" can do it automatically reading "obl_ecc_lsp.asc".
 
@@ -64 +64 @@
     > the XIOS outputs of the PCM: "Xoutdaily4pem*.nc"/"Xoutyearly4pem*.nc";
     > the outputs of the chained simulation: "pem_workflow.log", "pem_workflow.sts" and possibly "kill_pem_workflow.sh";
-    > the usual outputs of the PEM: "restartevol.nc", "restartfi.nc", "restart.nc"/"restart1D.txt" and "diagevol.nc".
+    > the usual outputs of the PEM: "restartevo.nc", "restartfi.nc", "restart.nc"/"restart1D.txt" and "diagevo.nc".
 During the simulation, the PCM/PEM run files are renamed conveniently and stored in the sub-directories "logs" (log files), "starts" (starting files) and "diags" (diagnostic files).
 If you run a simulation by submitting jobs, the script "kill_pem_workflow.sh" is automatically generated. It can be used to kill the jobs related to your chained simulation in the queue of the job scheduler.
@@ -102 +102 @@
 # run_pem.def
   All the possible parameters to define a PEM run (read in "config.F90").
-  It needs to include some definitions for the physics in file "run_pcm.def" with "INCLUDEDEF=run_pcm.def".
+  It needs to include some definitions in file "run_pcm.def" and "callphys.def" with "INCLUDEDEF=run_pcm.def".
 
 # obl_ecc_lsp.asc [default], obl_ecc_lsp_pos.asc [future years]
@@ -126 +126 @@
 
 # visu_layering.py:
-  Python script file to output the stratification data from the "startevol.nc" files.
+  Python script file to output the stratification data from the "startevo.nc" files.
 
-# visu_layering_evol.py:
-  Python script file to output the stratification data over time from the "startevol.nc" files.
+# visu_layering_evo.py:
+  Python script file to output the stratification data over time from the "startevo.nc" files.