I am trying to run MPAS-A v6.2 on the Navy computer narwhal (see: Navy DSRC: Narwhal User Guide). This machine is a Cray EX with AMD cores that I am compiling with the Cray ftn and cc compilers using either the titan-cray or cray-nersc Makefile options (both behave the same). The model compiles fine, but once I run MPAS-A, I get the following error in log.atmosphere.0000.log:
ERROR:
ERROR: ------------------------------ FATAL CALLED ------------------------------
ERROR: module_ra_rrtmg_sw: error reading RRTMG_SW_DATA on unit 10
CRITICAL ERROR: MPAS core_physics abort
A quick google search suggests that this issue can arise from either not having the RRTMG files in your run directory, but that is not the case here:
rtorn@narwhal06:/p/work1/rtorn/MPAS-DART/ftest% ls -lL RRTMG_*
-rw-r--r-- 1 rtorn 5048G660 847552 Jul 24 2020 RRTMG_LW_DATA
-rw-r--r-- 1 rtorn 5048G660 1694976 Jul 24 2020 RRTMG_LW_DATA.DBL
-rw-r--r-- 1 rtorn 5048G660 680368 Jul 24 2020 RRTMG_SW_DATA
-rw-r--r-- 1 rtorn 5048G660 1360572 Jul 24 2020 RRTMG_SW_DATA.DBL
Moreover, I found another thread about the possibility of having the wrong endian, so I compiled with "-h byteswapio", but that has not made any difference (I get the same error).
Any suggestions for how to address this error?
ERROR:
ERROR: ------------------------------ FATAL CALLED ------------------------------
ERROR: module_ra_rrtmg_sw: error reading RRTMG_SW_DATA on unit 10
CRITICAL ERROR: MPAS core_physics abort
A quick google search suggests that this issue can arise from either not having the RRTMG files in your run directory, but that is not the case here:
rtorn@narwhal06:/p/work1/rtorn/MPAS-DART/ftest% ls -lL RRTMG_*
-rw-r--r-- 1 rtorn 5048G660 847552 Jul 24 2020 RRTMG_LW_DATA
-rw-r--r-- 1 rtorn 5048G660 1694976 Jul 24 2020 RRTMG_LW_DATA.DBL
-rw-r--r-- 1 rtorn 5048G660 680368 Jul 24 2020 RRTMG_SW_DATA
-rw-r--r-- 1 rtorn 5048G660 1360572 Jul 24 2020 RRTMG_SW_DATA.DBL
Moreover, I found another thread about the possibility of having the wrong endian, so I compiled with "-h byteswapio", but that has not made any difference (I get the same error).
Any suggestions for how to address this error?