Closed glemieux closed 4 months ago
@glemieux that last bit in the error about the launcher is something that tells me to resubmit. And usually it resolves itself. I think I've maybe only had to resubmit another time for it to resolve.
But, if you are getting this consistently on every submission (but try a good four times or so) -- this must mean something real. The first thing that springs to mind is to try the intel and gnu compilers. And you might also try with fewer processors.
Hmmm....
Closing to move this to CTSM as it is either an issue there or an issue with the fates land use data tool. See https://github.com/ESCOMP/CTSM/issues/2653 and https://github.com/NGEET/tools-fates-landusedata/issues/5, respectively.
This was discovered in the process of testing https://github.com/NGEET/fates/pull/1223. The
FatesColdLUH2
test in thefates
suite fails RUN very early into the process. From the lnd.log file it looks like thefinundated
read upper bound step isn't reporting the correct file that it's reading from, but I think that might be a red herring. Note that this doesn't appear to be an issue onderecho
orperlmutter
.I can confirm that switching the
fluh_timeseries
to an older file that has a shorter time length does not present this issue. That said, the size of the file does not appear to be an issue after attempting to run the test case with a copy of the same file, but truncated to a shorter time. I will also note that the older file is formatted with theclassic
netcdf type, where as the newer file iscdf5
. That said, I'm not sure how relevant that is as theflandusepftdat
file that is used in this test does not present an issue when used in conjunction with the olderfluh_timeseries
file.It is possible that the newer file, which was generated via the fates land use tool, could be introducing an issue based on an update since the initial tool development when the original default was created (the original file was created when the tool was located as part of the fates repository). Issue https://github.com/NGEET/tools-fates-landusedata/issues/5 to investigate potential causes on that side.
The log file results are below:
lnd.log
cesm.log