Ganymed 1.0 Quick Start: Difference between revisions

Line 157:

Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''. Keep the "originals" handy since if the job stumbles early in the run it might stop after having renamed them. The model expects restart filenames to end in "rst" but produces them with the date and time appended, so you may have to rename them back to ending in "rst". The <code>cap_restart</code> file is often provided with a set of restarts, but if not you can create it: is simply one line of text with the date of the restart files in the format ''<code>YYYYMMDD HHMMSS</code>'' (with a space). The boundary conditions/forcings are provided by symbolic links created by the run script.

If you need an arbitrary set of restarts, you can copy them from <code>/archive/u/aeichman/restarts/Ganymed-1_0/</code>, where they are indexed by date ~~and resolution~~.

If you need an arbitrary set of restarts, you can copy them from <code>/archive/u/aeichman/restarts/Ganymed-1_0/</code>, where they are indexed by resolution and date.

Revision as of 14:34, 20 December 2012 view source Andrew.eichmann (talk \| contribs) 788 edits No edit summary ← Older edit		Revision as of 15:21, 20 December 2012 view source Andrew.eichmann (talk \| contribs) 788 edits →Running GEOS-5 Newer edit →
Line 157:		Line 157:
	Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''. Keep the "originals" handy since if the job stumbles early in the run it might stop after having renamed them. The model expects restart filenames to end in "rst" but produces them with the date and time appended, so you may have to rename them back to ending in "rst". The <code>cap_restart</code> file is often provided with a set of restarts, but if not you can create it: is simply one line of text with the date of the restart files in the format ''<code>YYYYMMDD HHMMSS</code>'' (with a space). The boundary conditions/forcings are provided by symbolic links created by the run script.		Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''. Keep the "originals" handy since if the job stumbles early in the run it might stop after having renamed them. The model expects restart filenames to end in "rst" but produces them with the date and time appended, so you may have to rename them back to ending in "rst". The <code>cap_restart</code> file is often provided with a set of restarts, but if not you can create it: is simply one line of text with the date of the restart files in the format ''<code>YYYYMMDD HHMMSS</code>'' (with a space). The boundary conditions/forcings are provided by symbolic links created by the run script.

	If you need an arbitrary set of restarts, you can copy them from <code>/archive/u/aeichman/restarts/Ganymed-1_0/</code>, where they are indexed by date ~~and resolution~~.		If you need an arbitrary set of restarts, you can copy them from <code>/archive/u/aeichman/restarts/Ganymed-1_0/</code>, where they are indexed by resolution and date.