[MITgcm-support] internal wave verification: problem with output for delX

[Martin Losch]

Hi Jeremy,

I believe that this experiment expects double precision input (in data: readBinaryPrec=64,), but in your script you write everything as “>f4”. Probably changing to “>f8” will fix the problem.
(alternatively you could set readBinaryPrec=32,)

Martin

> On 6. Apr 2021, at 09:06, Jeremy Miller <jeremysharonmiller at gmail.com> wrote:
> 
> Dear MITgcm support forum,
> 
> I am attempting to run the internal wave verification. Being a python user I transcribed gendata.m to python. The script I am using is attached here in the file gendata_IWs.py .
> After running genedata_IWs.py and subsequently running ./mitgcmuv > output.txt, I receive the following message in the terminal window:
> 
> S/R LOAD_GRID_SPACING: delX(i=   31)=  0.00000000E+00 : MUST BE >0
> S/R LOAD_GRID_SPACING: delX(i=   32)=  0.00000000E+00 : MUST BE >0
> .
> .
> .
> 
> S/R LOAD_GRID_SPACING: delX(i=   60)=  0.00000000E+00 : MUST BE >0
> S/R LOAD_GRID_SPACING: found   30 invalid delX values
> 
> I have read back in the delXVar file that I output and checked that the values do match the values in the original array dx.
> Best
> Jeremy Miller
> 
> 
> <gendata_IWs.py>_______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1665 bytes
Desc: not available
URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20210406/81b2877e/attachment.p7s>