[MITgcm-devel] averaging in diagnostics vs. exf

Martin Losch Martin.Losch at awi.de
Tue Jul 12 10:48:41 EDT 2011


Hi there,

this question is almost too embarrasing to be posted at devel:
I want to check the surface forcing that I am using and for that I compare what goes into the model with the diagnostics, for example air temperature. I have daily forcing (and I do not use any interpolation within exf)
cat data.cal
&CAL_NML
 TheCalendar='gregorian',
 startDate_1=19580101,
 startDate_2=000000,
 calendarDumps = .TRUE.,

cat data.exf
[...]
 useExfYearlyFields= .TRUE.,
[...]
#
 atempstartdate1=19480101,
 atempstartdate2=120000,
 atempperiod=86400.0,
#
[...]
and finally in data.diagnostics:
    frequency(3) = 86400.,
    fields(1,3) = 'EXFatemp',  
    filename(3) = 'run10ncf_dailyEXF',

I expect that EXFatemp should be the same as my input (let's call it "atemp") after approprate averaging, e.g. in matlab notation for a specific year:
EXFatemp(:,:,2) = 0.25*atemp(:,:,1)+0.5*atemp(:,:,2)+0.25*atemp(:,:,3)
(the factors are a result of linear interpolations between noon values) but unfortunately that is not the case (be several degrees). What am I missing? Problem in my data.diagnostics file, or in data.exf?

Martin





More information about the MITgcm-devel mailing list