Heracles 5.1 User's Guide: Difference between revisions

Using gcm_setup: Updates for 5.1
 
Line 178: Line 178:
/discover/nobackup/mathomp4/myexp42
/discover/nobackup/mathomp4/myexp42


</pre>


This U.S. Government resource is for authorized users only.  By accessing
After this, you will see a lot of cvs echos, an artefact of the local copy of the model tag being compared via cvs to the same tag on the repositoryIf there are differences it will tell in which files they exist, giving you a record of changes in your tag to the stock tag you entered above as the root.  
this system you are consenting to complete monitoring with no expectation
of privacy.  Unauthorized access or use may subject you to disciplinary
action and criminal prosecution.
 
This U.S. Government resource is for authorized users onlyBy accessing
this system you are consenting to complete monitoring with no expectation
of privacy.  Unauthorized access or use may subject you to disciplinary
action and criminal prosecution.
 
Applications/GEOSgcm_App>
</pre>


The security boilerplate at the end is an artefact of the local copy of the model tag being compared via cvs to the same tag on the repository.  If there are differences it will tell in which files they exist, giving you a change to update and recompile the model. Otherwise, the experiment is set up.  After you copy initial condition files (aka restarts) to the experiment directory, you can submit your job.
The experiment is set up.  After you copy initial condition files (aka restarts) to the experiment directory, you can submit your job.


===Do not copy old experiments===
===Do not copy old experiments===
Line 200: Line 190:
=== Using restart files ===
=== Using restart files ===


Restart files provide the initial conditions for a run, and a set needs to be copied into a fresh experiment directory before running.  This includes the file <code>cap_restart</code>, which provides the model starting date and time in text.  Restart files themselves are resolution-specific and sometimes change between model versions.  As of the current model version, they are now netcdf files with metadata instead of the previous flat binary files but typically have the same naming convention, so they tend to be stored together with restarts of the same provinance with the date either embedded in the filename or in an accompanying <code>cap_restart</code>, typically under a directory indicating the model version.  If you have restarts from a previous model version it may be worthwhile to try running with them as the model will check to see if they are in netcdf format, and if not, convert them.
Restart files provide the initial conditions for a run, and a set needs to be copied into a fresh experiment directory before running.  This includes the file <code>cap_restart</code>, which provides the model starting date and time in text.  Restart files themselves are resolution-specific and sometimes change between model versions.  As of the current model version, they are now netcdf files with metadata instead of the previous flat binary files but typically have the same naming convention, so they tend to be stored together with restarts of the same provenance with the date either embedded in the filename or in an accompanying <code>cap_restart</code>, typically under a directory indicating the model version.  If you have restarts from a previous model version it may be worthwhile to try running with them as the model will check to see if they are in netcdf format, and if not, convert them.


A cleanly completed model run will leave a set of restarts and the corresponding <code>cap_restart</code> in its experiment directory.  Another source is <code>/discover/nobackup/mathomp4/Restarts-H10/nc4/</code>.  Restarts are also left during runs in date-labeled tarballs in the <code>restarts</code> directory under the experiment directory before being transferred to the user's <code>/archive</code> space.  You may have to create the <code>cap_restart</code>, which is simply one line of text with the date of the restart files in the format ''YYYYMMDD HHMMSS'' (with a space).  
A cleanly completed model run will leave a set of restarts and the corresponding <code>cap_restart</code> in its experiment directory.  Another source is <code>/discover/nobackup/mathomp4/Restarts-H10/nc4/</code> which are sample restarts for various resolutions and oceans on 2000-04-14 21z.  Restarts are also left during runs in date-labeled tarballs in the <code>restarts</code> directory under the experiment directory before being transferred to the user's <code>/archive</code> space.  You may have to create the <code>cap_restart</code>, which is simply one line of text with the date of the restart files in the format ''YYYYMMDD HHMMSS'' (with a space).  


Failing the above sources, you can convert restarts from different resolutions and model versions, including MERRA, as described in [[Regridding Restarts for Heracles 5.1]].
Failing the above sources, you can convert restarts from different resolutions and model versions, or from MERRA2, as described in [[Regridding Restarts for Heracles 5.1]].


== What Happens During a Run ==
== What Happens During a Run ==