[MITgcm-support] how to run for exactly 1 month with calendarDumps
jklymak at uvic.ca
Mon Sep 18 13:31:51 EDT 2017
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.
On 18 Sep 2017, at 10:04, Ryan Abernathey wrote:
> 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,
> for many years.
> I am using the following data.cal
> calendarDumps = .TRUE.,
> I understand that calendarDumps causes chkPtFreq, pChkPtFreq,
> etc. to automatically conform their output to one calendar month if I
> 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
> after each run, and anyway, that would be hard because I would need to
> account for the variable month length. Alternatively, I could just
> run for 31 days, but this would waste some computer time for 30 and
> months. (A small amount, but the model is quite expensive already.)
> What do people commonly do in this situation?
> Thanks for the help!
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MITgcm-support