...
Samples | Raw n-hourly/minutely model output |
Diagnostics | Monthly means, variances, and timeseries calculated/assembled by the post processing (only if CLIMAT_diagnos=1 ) |
Analysis | Initial conditions files which can be used to initialize another simulations (only if CLIMAT_out_anal is set) |
Pilots | Pilot files which can be used to drive another simulation at the lateral boundaries (only if CLIMAT_out_pilot is set) |
Listings | Model listings, jobs, and config files |
Restarts | Restart files which can be used to restart a simulation from given check points. Once a simulation is finished remove several of these files to only keep 1 or 2 per year, since they are fairly large. |
...
Actually, there are up to four zip files under ${CLIMAT_archdir}/Listings/listings_${GEM_exp}.zip:
listings_*.zip | Contains all listings (log files) of finished simulations and their post processing |
configs_*.zip | Contains a copy of all used config files (they get updated during a simulation |
jobs_*.zip | Contains all model and post processing jobs which were created and ran |
cjobs_*.zip | If Chunk_lance was used this file contains all "chunk" jobs |
Ancre Restart files Restart files
Restart files
Restart files | |
Restart files |
At the end of each job, a restart file gets written. This contains the physics and dynamics files needed to restart the model. There will be files for each tile. These files contain a copy of the atmosphere and soil fields at the last time step of the job. When the next month gets started it reads the restart files of the previous month and continues from there. After the new month has started, the restart files from the previous month get archived on CLIMAT_arch_mach in CLIMAT_archdir as specified in your 'configexp.cfg'. It is always possible to restart the model at any given month from a restart file.
Since the restart files contain a full copy of the model atmosphere and soil they are quite large. So usually we do not keep all of them but erase some by hand afterwards. The name of a restart file looks like this:
${GEM_exp}_step###.tarz
With '###' being the number of the last timestep that was run.