[MITgcm-support] diagnostics - question

Jean-Michel Campin jmc at ocean.mit.edu
Mon Aug 9 10:47:18 EDT 2010

Hi Martin,

I am not sure those are the right parameters to set:

to get 10.d averages, I would just set the normal "frequency" to 10.d:
and to start to write after 99 years, you can set timePhase to 99.years
> # this is 99 year (a 360 days)
 timePhase(3)= 3079296000.,
Note that the 1rst reccord / output file corresponding to 
iter/time = 99.y will contain the average over the 99 years,
but the 2nd (at iter/time = 99.y+10d) will be a 10.d average.

repeatCycle, averagingFreq and averagingPhase would be usefull
to get a mean seanonal cycle over the full 100.years integration 
with 10.d time resolution (repeatCycle=36, averagingFreq=864000.).


On Mon, Aug 09, 2010 at 02:15:23PM +0200, Martin Losch wrote:
> Hi there,
> some time ago I was taught that the diagnostic package not only can do periodic averagings (e.g. to get 12 monthly averages over the entire integration period), but also that you can start the averaging at a different time than the ocean model integration. In my case I'd like to have a 100y run, and I would like to save 10day averages of the final year. Unfortunately I forgot how to do that (=lost my example data.diagnostics). Here is, what I think it should look like:
> >  averagingFreq(3)  = 864000.,
> # this is 99 year (a 360 days)
> >  averagingPhase(3) = 3079296000.,
> >  repeatCycle(3) = 36,
> >  filename(3)  = 'someName',
> >  fields(1,3)  = 'Somediagnostics',
> Can you confirm?
> Martin
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support

More information about the MITgcm-support mailing list