The LDAS_DEBUGCONUS/model test crashes with a floating point exception when using ESMA_env v4.26.0. The test runs ok with ESMA_env v4.23.0. All other tests (incl. GNUDEBUGCONUS) are ok.
Note that ESMA_env v4.26.0 uses a new version of HDF5.
The GEOSldas "err" and "log" files from the run that crashed are:
GEOSldas_err_txt.txt
GEOSldas_log_txt.txt
The log file suggests that the floating point exception occurs when opening an GEOS nc file (Line 5376 of LDAS_Forcing.F90) using nf90_open().
I overlooked this problem when testing for #713, where I probably only ran the standard tests and not the debug tests.
I suspect the problem is not within ESMA_env v4.26.0 but rather poor coding in LDAS that is exposed with the DEBUG build .
cc: @mathomp4 @weiyuan-jiang @biljanaorescanin
The
LDAS_DEBUGCONUS/modeltest crashes with a floating point exception when using ESMA_env v4.26.0. The test runs ok with ESMA_env v4.23.0. All other tests (incl. GNUDEBUGCONUS) are ok.Note that ESMA_env v4.26.0 uses a new version of HDF5.
The GEOSldas "err" and "log" files from the run that crashed are:
GEOSldas_err_txt.txt
GEOSldas_log_txt.txt
The log file suggests that the floating point exception occurs when opening an GEOS nc file (Line 5376 of LDAS_Forcing.F90) using
nf90_open().I overlooked this problem when testing for #713, where I probably only ran the standard tests and not the debug tests.
I suspect the problem is not within ESMA_env v4.26.0 but rather poor coding in LDAS that is exposed with the DEBUG build .
cc: @mathomp4 @weiyuan-jiang @biljanaorescanin