search

oceandie / BALTIC-MEs

0 stars 2 forks source link

3. Compiling MEs-DOMAINcfg tool in SMHI supercomputer #3

Open oceandie opened 2 years ago

erik808 commented 2 years ago

Hej! What should be the vertical index for umask? https://github.com/oceandie/BALTIC-MEs/blob/d0cb4a3aaad6326520b275e34dd5a76a3e262393/src/f90/NEMO_4.0-HEAD_test_MEs/tools/DOMAINcfg/src/domwri.f90#L580

1? Compiler nags about it.

oceandie commented 2 years ago

Hi, not sure what you mean ... umask array has the same dimensions than tmask, i.e. jpni x jpnj x jpnk . Could you post here the error you get during compilation?

erik808 commented 2 years ago 
/home/sm_erimu/Projects/NEMO/NEMOGCM_4.0.4/tools/DOMAINcfg/src/domwri.f90(580): error #6351: The number of subscripts is incorrect.   [UMASK]
                  zr1(1) = ABS( kk - km1 ) * umask(ji-1, jj)
---------------------------------------------^
/home/sm_erimu/Projects/NEMO/NEMOGCM_4.0.4/tools/DOMAINcfg/src/domwri.f90(581): error #6351: The number of subscripts is incorrect.   [UMASK]
                  zr1(2) = ABS( kk - kp1 ) * umask(ji  , jj)
---------------------------------------------^
/home/sm_erimu/Projects/NEMO/NEMOGCM_4.0.4/tools/DOMAINcfg/src/domwri.f90(589): error #6351: The number of subscripts is incorrect.   [VMASK]
                  zr1(3) = ABS( kk - km1 ) * vmask(ji, jj-1)
---------------------------------------------^
/home/sm_erimu/Projects/NEMO/NEMOGCM_4.0.4/tools/DOMAINcfg/src/domwri.f90(590): error #6351: The number of subscripts is incorrect.   [VMASK]
                  zr1(4) = ABS( kk - kp1 ) * vmask(ji, jj  )
---------------------------------------------^
compilation aborted for /home/sm_erimu/Projects/NEMO/NEMOGCM_4.0.4/tools/DOMAINcfg/src/domwri.f90 (code 1)
fcm_internal compile failed (256)

So from the looks of it I would give it kk as third index but that's just guesswork :)

oceandie commented 2 years ago

Hi @erik808,

As I was saying last time we spoke the saw_tooth diagnostic is still pretty much in development - so for time being I just comment it out in the last version of the code ... if you pull and try to compile it again we shouldn't have that error anymore ... let me know how it goes

erik808 commented 2 years ago

Ok thanks so rest of the compilation works fine.