[MITgcm-support] Diagnostics at end of run

[Martin Losch]

Hi Roland,

I usually let the model run for one extra timestep (so 73 in your case) to make sure that I get the full output. and then use timePhase = 21600. As far as I know, the diagnostics package stores the data at the beginning of the time step so that the data for the 72nd time step is only available in timestep 73.

Martin

> On 11 May 2015, at 12:11, Roland Young <Roland.Young at physics.ox.ac.uk> wrote:
> 
> Hi,
> 
> I’m having trouble outputting diagnostics at the end of a run. I’m currently running a test job with time step 600s for 12 hours (72 timesteps). I want to get diagnostic output of some instantaneous fields after 6 hours and 12 hours, but I can’t get it to output diagnostics in the final timestep.
> 
> Here are the relevant lines in my data.diagnostics:
> 
> &DIAGNOSTICS_LIST
> 
>  dumpAtLast = .true.,
>  diag_mnc   = .true.,
> 
>  fields(1:4,1) = 'UVEL', 'VVEL', 'WVEL', 'THETA',
>  filename(1)   = 'diagout4',
>  frequency(1)  = -21600.,
>  timePhase(1)  =  21600.,
> 
> &
> 
> &DIAG_STATIS_PARMS
> &
> 
> This gives me output at timesteps 0 and 36 (model start and 6h).
> 
> timePhase(1)  =  0. also gives me output at timesteps 0 and 36.
> timePhase(1)  =  21000., gives me output at timesteps 35 and 71 (i.e. 1 time step before the last one).
> timePhase(1)  =  600., gives me output at timesteps 1 and 37.
> timePhase(1)  =  10800., gives me output at timesteps 18 and 54 (3h and 9h).
> Leaving timePhase(1) unset also gives me output at timesteps 18 and 54.
> 
> None of which is what I want. What am I doing wrong here?
> 
> Thanks,
> 
> Roland
> 
> 
> 
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support