-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USGS_GFmz grid fails to run #273
Comments
Current data structure - rtmCTL - assumes HRU (catchment) where ROF receive areal mean runoff from LND and river reach has one-to-one relationship, allow both elements to have the same domain decomposition information. For example, gridded network, one grid-box is catchment, but also considered as river reach (actually this concept does not exist in gridded network). mizuRoute can handle many HRUs to one reach relationship. USGS network has two HRU to one reach relationship, and HRU and reach has separate domain decompositions. To accommodate this, rtmCTL%discharge, and rtmCTL%volr need to be populated with domain decomposition based on the reach not HRU. For two-way coupling (possibly future), need to distribute discharge, volume and flood from one reach to (many) HRU(s) somehow. |
We think that @nmizukami fixed the underlying issues in mizuRoute with this. However, the overall problem remains, but we believe it's a CTSM or CDEPS/datm issue. See the issue in CTSM about this |
The underlying CTSM and CDEPS issues are resolved and this is now working. |
The USGS_GFmz grid fails to run because of a known issue with there being a different number of river segments to HRU's. @nmizukami tried a simple fix for this that allowed it to work, but had impact on other grids.
Three tests that fail are:
ERS.nldas2_rUSGS_mnldas2.I2000Clm50SpMizGs.cheyenne_gnu.mizuroute-default RUN
ERS.nldas2_rUSGS_mnldas2.I2000Clm50SpMizGs.cheyenne_intel.mizuroute-default RUN
SMS_D.nldas2_rUSGS_mnldas2.I2000Clm50SpMizGs.cheyenne_intel.mizuroute-default RUN
The intel and nag ERS tests are also expected to fail on izumi.
ERS.nldas2_rUSGS_mnldas2.I2000Clm50SpMizGs.izumi_intel.mizuroute-default RUN
ERS.nldas2_rUSGS_mnldas2.I2000Clm50SpMizGs.izumi_inag.mizuroute-default RUN
On cheyenne the SMS_D test seems to fail in datm with the following backtrace in the cesm.log file..
The gnu test shows a more sensible error inside of mizuRoute
Similarly the ERS intel test shows an error inside of mizuRoute for MPI
The text was updated successfully, but these errors were encountered: