[MITgcm-support] difference between writeStatePrec and writeBinaryPrec

[Martin Losch]

Hi David,
yes, that's possible and simple: it's the default.

pickup files are always double precision (I don't think that that's  
possible to change). The other ieee-be I/O precision is set via  
readBinaryPrec and writeBinaryPrec which both default to precFloat32  
= 32 (single precision).
If you want double precision output set writeBinaryPrec=64. If you  
want to have your input (topography, initial conditions, etc) as  
double precision, set readBinaryPrec=64 in "data".
writeStatePrec is not really used (as far as I can see), except for  
some stuff which is related to adjoint variables I/O.

Martin

On 5 Jun 2008, at 23:12, David Hebert wrote:

> What is the difference between writeStatePrec and writeBinaryPrec?  
> From search of MITgcm web it looks like writeBinaryPrec gets set to  
> writeStatePrec.
>
> I am interested in writing double precision pickup files, but  
> single precision dumps for storage. It this possible, and what  
> flags are set to do this?
>
> Thanks,
>
> David
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support