[MITgcm-support] 'repeatPeriod' in data.exf

[Martin Losch]

Suneet,

you can split you forcing fields into years. They have to follow this naming convention:
forcingFile_year, where "year" is a 2 or 4-digit year (e.g. myatemp_1996, myatemp_1997, etc).

In data.exf set:
 useExfYearlyFields= .TRUE.,
 twoDigitYear      = .FALSE.,

and 
atempfile = myatemp,
etc. If you want to use a Gregorian calendar the data.cal should look like this:
 &CAL_NML
 TheCalendar='gregorian',
# here you insert your start date, of course
 startDate_1=19920101, 
 startDate_2=000000,
# this makes the model interpret output "freqs" (e.g. dumpFreq) close to 1 month (say 2592000.) as a "real" month, the same for a year.
 calendarDumps = .TRUE.,
 &

There are a few examples in the MITgcm_contrib area (arctic, high_res_cube)

Martin


On Jun 22, 2010, at 1:38 AM, Suneet Dwivedi wrote:

> Hi Everybody,
>  
> Could anyone of you please tell me what is the exact meaning of parameter 'repeatPeriod' in exf package/data.exf?
>  
> I wish to perform a long run of 50-55 years with daily air/sea forcing values over Indian Ocean. Matlab is unable to store and process such a long matrix of dimension [250 150 20000] ~ O(1e+10) with 64 bit precision. An alternative way to do this may be to use climatological daily forcing values (averaged over all available years) of dimension [250 150 366] and use the climatological values for each year of simulation. In this case, i need to know the variable that does this in MITgcm. I wonder 'repeatPeriod' does this. Am I right? For example, if i set 'repeatPeriod' to something like 31622400.0 (for 1 year), will I be able to use same values of forcing on same days of each year after completing one year of simulation? Please suggest.
>  
> Thanks,
> Suneet 
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support