GEM 5.0 running

Listings

While the model is running is produces several listings. They all start with the name of the experiment, exp, followed by the year and month of the current month. All listings will start with the experiment name followed by the current year and month:

   ${exp}_YYYYMM_*

When starting a simulation with 'Chunk_lance' the output of the main script will go into a listing called:

   cjob_${exp}.n.*

While a month is running all listings will go into the directory:

   ~/listings/${TRUE_HOST}

At the end of a month all model listings (${exp}_YYYYMM_*) will get archived under:

   ${CLIMAT_archdir}/${exp}/Listings/listings_${exp}.zip

These are the different types of listings:

a) Model listings

• ${exp}_YYYYMM_S*
  

This is the output of the Scripts which prepare directories and update the config files. When starting a simulation with 'Um_lance' this output appears in the window in which you executed the command. When a simulation is started with 'Chunk_lance' or when a second month is launched automatically the output of the scripts get redirected into a listing with the name ${exp}_S*.

• ${exp}_YYYYMM_M*
  

This is the main model output.
When a model job is running, each MPI process will write is output in a separate file, so while a simulation is running you will only see the first part of the output in the listing. Close to the end you will find a line starting with:
      INFO: temporary listings for all members in ...
Under that path you will find all the temporary process listings. Once a job finished all process listings will get added to the main model listing. If you want to see the simulation advancing while it is running, you can execute the command 'u.tail' on the main model listing. It will do a 'tail -f' on the listing of the main MPI process:
      u.tail ${exp}_YYYYMM_M...
Whenever there are problems with the model look for the error in the last of these two listings, which ever it may be. I usually execute something like:

   ls -lrt ${exp}_*_[MS][._]*

b) Post processing listings

Every now and then but at least at the end of timestep 0 and at the end of each job the model execute a a little job, preparing and submitting a post processing job. If you are not using 'superjobs' this post processing job will then run under the name:
      ${exp}_YYYYMM_DX...

• ${exp}_YYYYMM_PP0* and ${exp}_YYYYMM_PP*
  

Listing of the job creating and submitting the Post Processing job. If need be you can find in these listings the command to resubmit a post processing job. Look for 'soumet' close to the end. The '_PP_' job is the last one, submitted at the end of a job. If post processing jobs were submitted during a job they will be called '_PP0_'.

• ${exp}_YYYYMM_DX*
  

This is the listing of the main post processing job. You will see there the results of the combination of the files, the transfer (Xfer) in the archive and the calculation of the Diagnostics.

• ${exp}_YYYYMM_SR*
  

At the end of a month the Restart files will get Saved.

• ${exp}_YYYYMM_SL*
  

And at the end of the post processing the Listings will get Saved.