[MITgcm-support] odd diagnostics package output

[Daniel Enderton]

Thanks for the response JM,

Despite setting

frequency(1) = -600.,
timephase(1) = 0.,

I get the same behavior as originally described.  I looked at the 
posts on the MIT-devel list mails, but this did not to help to 
clarify the issue.

Daniel

>Hi Daniel,
>
>There was few e-mails sent about "negative diagnostics freq"
>on MITgcm-devel list, in April this year, :
>http://dev.mitgcm.org/pipermail/mitgcm-devel/2005-April/subject.html
>
>Since that time, I added the phase shift option,
>but the default is as it was before: for instantaneous diags,
>(negative freq), phase = period/2.
>
>In your case, you just have to specify:
>frequency(1) = -600.,
>timephase(1) = 0.,
>and you shoud get what you want.
>
>Jean-Michel
>
>On Sat, Sep 03, 2005 at 12:40:06PM -0400, Daniel Enderton wrote:
>>  Hello Folks,
>>
>>  I was curious about switching over to using the diagnostics package
>>  for my output when I noticed some odd behavior.  For a held-saurez
>>  simulation I checked the state output using the diagnostics package
>>  versus the normal state.*.nc that is ouput.  For the diagnostics
>>  package I set
>>
>>    frequency(1) = -600.,
>>    filename(1) = 'surface',
>>    levels(1,1) = 1.,
>>    fields(1,1) = 'ETAN    ','ETANSQ  ','DETADT2 ',
>>
>>  and set the  dumpFreq=600 in the data file.  The output for the
>>  diagnostics package was phase shifted.  The state.*.nc file had
>>
>>   T = 0, 600, 1200, 1800, 2400, 3000 ;
>>
>>   Eta =
>>   0, 0, ...
>>   [more zeros corresponding to T=0, as desired for this simulation]
>>   0.0126337883550606, 0.0113340932414461, ...
>>   [The rest of the values for T=600 and beyond]
>>
>>  While the diagnostics package output read
>>
>>   T = 600, 1200, 1800, 2400, 3000 ;
>>   ETAN =
>>   0, 0, ...
>>   [more zeros, here corresponding to T=600]
>>   0.01263379, 0.01133409, ...
>>   [more non-zero values corresponding to T=1200 and beyond]
>>
>>  I tried playing with the timephase setting to try and get the
>>  snap-shot output from the diagnostics package to start at T = 0
>>  (example:  frequency(1) = -600., \ timephase(1) =  -600.,) but I
>>  could not get it to do so.  Further, this apparent phase shift goofs
>>  up the diagnostics package time average data and monitor statistics.
>>
>>  Is there something that I am missing about how to use the diagnostics
>>  package or is this phase shift a problem in the code?  Any
>>  suggestions would be appreciated!
>>
>>  Daniel
>>
>>  _______________________________________________
>>  MITgcm-support mailing list
>>  MITgcm-support at mitgcm.org
>>  http://mitgcm.org/mailman/listinfo/mitgcm-support
>_______________________________________________
>MITgcm-support mailing list
>MITgcm-support at mitgcm.org
>http://mitgcm.org/mailman/listinfo/mitgcm-support