[mpas-developers] MPAS time manager

[Todd D. Ringler]

Hi Michael,

Thanks for producing the initial implementation.

There are others on the LANL side who are much more familiar with the
specifics on the time manager than I am, so I will let them weight in on
the specification of the format.

The part that I would like to weight in on is the cross-component
uniformity. I would strongly advocate for us striving (at least at this
early stage) to have a standard initial implementation across all
components. Of all of the things that we need to coordinate, broad
agreement on the implementation of the time manager should an relatively
easy task. I guess we will see!

Cheers,
Todd

> 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
>