[mpas-developers] MPAS time manager

[Jones, Philip W]

Michael,

No strong preference on input format, though it's certainly easier to input separate year, month, day rather than parsing a string and trying to catch all the potential variations and potential errors.

Thanks,

Phil


On 7/19/11 12:10 PM, "Michael Duda" <duda at ucar.edu> wrote:

Hi, All.

We're finally finishing up a first cut at the MPAS time manager
module, and to proceed with implementation in the trunk, I though
we might first create a branch of the trunk and add the new time
manager code to this branch. Then, we could convert all cores in
that branch to use the new time manager for tracking simulation
start time, end time, output interval, restart interval, and
restart time. If this implementation looks alright to everyone, we
could then merge the branch back to the trunk.

We can certainly decide on a per-dycore basis, but it might not be
a bad idea to standardize on a format for specifying, e.g.,
simulation starting and ending times. For example, we could choose
to specify separate integer values for start_year, start_month,
start_day, etc., or we could specify start_time as a date string.
Are there any strong preferences for date/time formats in the
namelist.input file?

Cheers,
Michael
_______________________________________________
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/20110719/732839cc/attachment.html