[MITgcm-support] how to run for exactly 1 month with calendarDumps

[Ryan Abernathey]

>
> I’ve not done this at all, but it seems a script to manually specify
> startTime and endTime wouldn’t be too hard. I parse the data file all the
> time when I want to do automatic runs like this. I use python, but I’m sure
> clever people can use bash and awk or sed.
>
That script would have to understand calendars. endTime is specified in
seconds. So the script would have to know which month it is running and how
many days that month has. Yes, this is do-able, but, wherever dates are
involved, I prefer not to get my hands dirty, especially if there is an
established solution already.

> Cheers, Jody
>
> On 18 Sep 2017, at 10:04, Ryan Abernathey wrote:
>
> Hi,
>
> I am new to doing "realistic" simulations with the cal package activated. I
> would like to run for one calendar month and then dump diagnostics and
> pickup files. I will then restart from pickup and run the next month, etc.,
> for many years.
>
> I am using the following data.cal
>
> &CAL_NML
> TheCalendar='gregorian',
> startDate_1=20100101,
> startDate_2=000000,
> calendarDumps = .TRUE.,
> &
>
> I understand that calendarDumps causes chkPtFreq, pChkPtFreq, taveFreq,
> etc. to automatically conform their output to one calendar month if I set
> chkptFreq = 259200.0.
>
> My question is: how to I make the model stop running after exactly one
> month, given that the length of a month is variable?
>
> The two options I am familiar with for setting the length of the run
> are nTimeSteps or endTime. I don't want to manually specify the endTime
> after each run, and anyway, that would be hard because I would need to
> account for the variable month length. Alternatively, I could just always
> run for 31 days, but this would waste some computer time for 30 and 28-day
> months. (A small amount, but the model is quite expensive already.)
>
>
>
>
> What do people commonly do in this situation?
>
> Thanks for the help!
>
> -Ryan
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20170918/e38b77e6/attachment-0001.html>