Heracles 4.3 User's Guide: Difference between revisions

(4 intermediate revisions by the same user not shown)

Line 49:

This gives you an opportunity to copy ~~the setup of~~ an existing experiment while changing what needs to be changed to make it work.

This gives you an opportunity to copy an existing experiment while changing what needs to be changed to make it work. If you enter yes, the script will ask you which experiment to clone, and then will do so and exit.

Line 76:

Enter the Atmospheric Model Vertical Resolution: LM (Default: 72)

Unless you know you want a different vertical resolution, hit enter.

Do you wish to run the COUPLED Ocean/Sea-Ice Model? (Default: NO or FALSE)

Line 182:

Line 183:

/discover/nobackup/aeichman/myexp42

This U.S. Government resource is for authorized users only. By 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.

This U.S. Government resource is for authorized users only. By 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>

~~And~~ the experiment is set up. After you copy initial condition files (aka restarts) to the experiment directory, you can submit your job.

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.

===Do not copy old experiments===

When creating related experiments, you will be tempted to copy the experiment directory tree of an older experiment. '''Do ''not'' copy old experiments, ~~run~~ <code>gcm_setup</code> instead.''' There are numerous instances where an experiment-specific directory is used in the run scripts created from templates by <code>gcm_setup</code> and they will wreak subtle and pervasive havoc if executed in an unexpected environment. This warning is especially true between model versions. A useful and relatively safe exception to this rule is to copy previously used examples of <code>HISTORY.rc</code>. However, you need to change the lines labeled <code>EXPID</code> and <code>EXPDSC</code> to the values in your automatically-generated <code>HISTORY.rc</code> or the plotting will fail.

When creating related experiments, you will be tempted to copy the experiment directory tree of an older experiment. '''Do ''not'' copy old experiments, clone them through <code>gcm_setup</code> instead.''' There are numerous instances where an experiment-specific directory is used in the run scripts created from templates by <code>gcm_setup</code> and they will wreak subtle and pervasive havoc if executed in an unexpected environment. This warning is especially true between model versions. A useful and relatively safe exception to this rule is to copy previously used examples of <code>HISTORY.rc</code>. However, you need to change the lines labeled <code>EXPID</code> and <code>EXPDSC</code> to the values in your automatically-generated <code>HISTORY.rc</code> or the plotting will fail.

=== Using restart files ===

Line 266:

Line 277:

The individual collection attributes are described below, but what users modify the most are the <code>fields</code> attribute. This determines which exports are saved in the collection. Each field record is a string with the name of an export from the model followed by a string with the name of the gridded component which exports it, separated by a comma. The entries with a third column determine the name by which that export in saved in the collection file when the name is different from that of the export.

There is a good description of available collection options at Modeling Guru: https://modelingguru.nasa.gov/docs/DOC-1190

===What exports are available?===

@@ Line 49: / Line 49: @@
-This gives you an opportunity to copy the setup of an existing experiment while changing what needs to be changed to make it work.
+This gives you an opportunity to copy an existing experiment while changing what needs to be changed to make it work. If you enter yes, the script will ask you which experiment to clone, and then will do so and exit.
@@ Line 76: / Line 76: @@
   Enter the Atmospheric Model Vertical Resolution: LM (Default: 72)
+Unless you know you want a different vertical resolution, hit enter.
   Do you wish to run the COUPLED Ocean/Sea-Ice Model? (Default: NO or FALSE)
@@ Line 182: / Line 183: @@
 /discover/nobackup/aeichman/myexp42
+This U.S. Government resource is for authorized users only.  By 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.
+This U.S. Government resource is for authorized users only.  By 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>
-And the experiment is set up.  After you copy initial condition files (aka restarts) to the experiment directory, you can submit your job.
+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.
 ===Do not copy old experiments===
-When creating related experiments, you will be tempted to copy the experiment directory tree of an older experiment.  '''Do ''not'' copy old experiments, run <code>gcm_setup</code> instead.'''  There are numerous instances where an experiment-specific directory is used in the run scripts created from templates by <code>gcm_setup</code>  and they will wreak subtle and pervasive havoc if executed in an unexpected environment.  This warning is especially true between model versions.  A useful and relatively safe exception to this rule is to copy previously used examples of <code>HISTORY.rc</code>.  However, you need to change the lines labeled <code>EXPID</code> and <code>EXPDSC</code> to the values in your automatically-generated  <code>HISTORY.rc</code> or the plotting will fail.
+When creating related experiments, you will be tempted to copy the experiment directory tree of an older experiment.  '''Do ''not'' copy old experiments, clone them through <code>gcm_setup</code> instead.'''  There are numerous instances where an experiment-specific directory is used in the run scripts created from templates by <code>gcm_setup</code>  and they will wreak subtle and pervasive havoc if executed in an unexpected environment.  This warning is especially true between model versions.  A useful and relatively safe exception to this rule is to copy previously used examples of <code>HISTORY.rc</code>.  However, you need to change the lines labeled <code>EXPID</code> and <code>EXPDSC</code> to the values in your automatically-generated  <code>HISTORY.rc</code> or the plotting will fail.
 === Using restart files ===
@@ Line 266: / Line 277: @@
 The individual collection attributes are described below, but what users modify the most are the <code>fields</code> attribute.  This determines which exports are saved in the collection.  Each field record is a string with the name of an export from the model followed by a string with the name of the gridded component which exports it, separated by a comma.  The entries with a third column determine the name by which that export in saved in the collection file when the name is different from that of the export.
+There is a good description of available collection options at Modeling Guru: https://modelingguru.nasa.gov/docs/DOC-1190
 ===What exports are available?===