[MITgcm-support] 32-bit diagnostic output

[Jean-Michel Campin]

Hi Neil,

The precision (32-bit or 64 bit) of pkg/diagnostics output file
is, by default, set according to writeBinaryPrec (that you can set in main 
parameter file "data", 1rst namelist, default value is 32). 
This is just to confirm Anthony's response.

But you can also specify (overwrite the default) the precision of 
pkg/diagnostics output file on a per output file basis, in data.diagnostics:
to select 64 bit output:
  fileName(1) = 'surfDiag',
 fileFlags(1) = 'D       ',
(see example in verification/tutorial_deep_convection/input/data.diagnostics
or 32 bit output:
  fileName(2) = 'shap_shot',
 fileFlags(2) = 'R       ',
But I agree that this "fileFlag" setting is not well documented and should
be improved.

Cheers,
Jean-Michel

On Mon, Oct 03, 2016 at 09:09:57PM -0400, Anthony Joyce wrote:
> Neil,
> 
> Add....
> 
> readBinaryPrec=32, (or 64)
> writeBinaryPrec=32, (or 64)
> 
> in the data file.
> 
> Anthony
> 
> 
> On 10/3/2016 6:33 PM, Neil Patel wrote:
> >I???ve tried search the manual and listserve, but haven???t been able to find an answer. Some of my 3-D fields (SALTanom, THETA) from the diagnostics package are being outputed with 64-bit precision and I???d prefer 32-bit precision. I don???t see any control in data or data.diagnostics. Anyone know where the control is?
> >
> >Thanks,
> >
> >Neil
> >_______________________________________________
> >MITgcm-support mailing list
> >MITgcm-support at mitgcm.org
> >http://mitgcm.org/mailman/listinfo/mitgcm-support
> 
> -- 
> Anthony J. Coletti
> Climate System Research Center
> Department of Geosciences
> University of Massachusetts-Amherst
> paleoclimate.org
> ajcolett at geo.umass.edu
> 
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support