[MITgcm-support] mnc questions

Ed Hill ed at eh3.com
Mon Dec 19 22:05:49 EST 2005


On Mon, 2005-12-19 at 16:33 -0500, David Wang wrote:
> Hi Michael,
> 
> If your aim is only to store each variable in its own nc file. There is 
> a way to let mitgcm do something like:
> 
> enable diagnostics pkg, in data.diagnostics for each entry you add a 
> single variable, To get the identical result as state.*.nc has, set 
> frequency to be dumpFreq, and timephase to be zero. After getting 
> diagnostics pkg to work, you may want to prevent model from dumping 
> state.*.nc by setting dumpFreq = 0. and dumpInitAndLast = .FALSE.

Hi Michael & David,

The above is good advice.

Also, there is a temporary feature in place activated by the variable
"mnc_filefreq" within the data.mnc file.  Basically, what it does is
allow the user to specify an overall frequency (in terms of model time)
that MNC files should be created.  Currently, this frequency is only set
on a global (all mnc output files) basis using a simple bit of code in
FORWARD_STEP():

  IF (DIFFERENT_MULTIPLE(mnc_filefreq,myTime,deltaTClock)) THEN
     ...create new MNC output files...
  ENDIF

and it should do most of what you want.  Although, it still doesn't let
you write one-variable-per-file.

Ed

-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Rm 54-1424;  77 Massachusetts Ave.
             Cambridge, MA 02139-4307
emails:  eh3 at mit.edu                ed at eh3.com
URLs:    http://web.mit.edu/eh3/    http://eh3.com/
phone:   617-253-0098
fax:     617-253-4464




More information about the MITgcm-support mailing list