[mpas-developers] mpas output file naming conventions

Jones, Philip W pwjones at lanl.gov
Thu Sep 8 10:47:36 MDT 2011


Folks,

A couple of options.  POP generally appends a simulation date (and time if the output is frequent enough) to output filenames.  The namelist just contains root filenames and paths and the suffix contains date stamp and format (bin vs netCDF).  CESM has similar date tags and both CESM and POP have an option to read info from a "pointer file" - this file is a simple text file that contains the name of the last restarts written (and is over-written every time a new restart is written).  Then, on startup, the code can read the location/name of the last restart from this pointer file.

We probably will need the latter option for CESM compatibility at some point.

Phil

On 9/8/11 10:39 AM, "Todd Ringler" <ringler at lanl.gov> wrote:


Hi Everyone,

More broadly, the issue that Sara raises is a common headache in climate modeling. A simulations might be composed of a dozen or more queue submissions that pick up where the last submission ended.

Sara offered one possible remedy. I am guessing Mat has also come up with solutions and that Phil has had to address this more broadly within the CESM. Can others offer up ideas on how we should build in support for production simulations that need a large number of submissions/restarts to complete?

Cheers,
Todd


On Sep 8, 2011, at 10:22 AM, Sara A. Rauscher wrote:


 Hi,

 I mentioned this to Todd and he suggested I post my user experience to the developer team.

 I've been running cam-mpas, and revision 983 brought up a small run-time hassle. Is there any way to automatically put a unique name on mpas output files instead of generic names like "output.nc", "ocean.nc" without editing namelist.input every time? For example, they could be time stamped by model time (YYYY-MM-DD-HH as in CESM)  or number of time steps) or the real-world time at which the job is running.

 It's not a big deal during testing, but in production runs it starts to be a hassle. I have set my run script to capture the date from the latest CAM restart file and sed that into namelist.input so that the output files have a unique and meaningful name. It works fine but errors can still happen. In production runs, with one misnamed file, or writing over an output file, things get messy fast.

 thanks
 cheers
 sara





 -------- Original Message --------
 Subject:  [mpas-developers] /home/subversion/mpas/model revision 983
 Date:  Wed, 7 Sep 2011 11:00:48 -0600 (MDT)
 From:  mpas-developers at ucar.edu
 Reply-To:   mpas-developers at ucar.edu
 To:  mpas-developers at ucar.edu


ringler at lanl.gov 2011-09-07 11:00:48 -0600 (Wed, 07 Sep 2011)

add default naming for I/O files


________________________________

Modified: branches/ocean_projects/timesplitting_mrp/namelist.input.ocean
===================================================================
--- branches/ocean_projects/timesplitting_mrp/namelist.input.ocean 2011-09-07 15:53:33 UTC (rev 982)
+++ branches/ocean_projects/timesplitting_mrp/namelist.input.ocean 2011-09-07 17:00:48 UTC (rev 983)
@@ -8,6 +8,9 @@
    config_stats_interval = 100
 /
 &io
+   config_input_name = 'ocean.nc'
+   config_output_name = 'output.nc'
+   config_restart_name = 'restart.nc'
 /
 &restart
    config_restart_interval = 10000000



 <Attached Message Part.txt>




_______________________________________________
mpas-developers mailing list
mpas-developers at mailman.ucar.edu
http://mailman.ucar.edu/mailman/listinfo/mpas-developers




---
Correspondence/TSPA/DUSA EARTH
------------------------------------------------------------
Philip Jones                                pwjones at lanl.gov
Climate, Ocean and Sea Ice Modeling
Los Alamos National Laboratory
T-3 MS B216                                 Ph: 505-500-2699
PO Box 1663                                Fax: 505-665-5926
Los Alamos, NM 87545-1663



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/mpas-developers/attachments/20110908/5eb772fc/attachment.html 


More information about the mpas-developers mailing list