You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Prior bug was logged to indicate the model crashes when the input dimensions on the forcing files is inconsistent with the geogrid file. That issue results in an ugly model crash with FORC_TYP=6. However, when FORC_TYP=1, the model does NOT crash and completes without error, even if the input forcing files are the incorrect dimension sizes. Currently unknown if this occurs with forcing files larger or smaller than the basin being ran.
Expected Behavior
The model should gracefully crash when the input LDASIN forcing files are of the incorrect dimension size.
Provide a check when the LDASIN files are read in to check for correct dimension sizes.
Current Behavior
The model does not error out or crash. It completes.
See above.
Possible Solution
Provide a check when forcing files are read in to ensure the dimension sizes match that of the geogrid file.
Steps to Reproduce (for bugs)
Your Environment
Version of the code used:
Operating System and version:
Compiler and version:
Other relevant information:
The text was updated successfully, but these errors were encountered:
A Prior bug was logged to indicate the model crashes when the input dimensions on the forcing files is inconsistent with the geogrid file. That issue results in an ugly model crash with FORC_TYP=6. However, when FORC_TYP=1, the model does NOT crash and completes without error, even if the input forcing files are the incorrect dimension sizes. Currently unknown if this occurs with forcing files larger or smaller than the basin being ran.
Expected Behavior
The model should gracefully crash when the input LDASIN forcing files are of the incorrect dimension size.
Provide a check when the LDASIN files are read in to check for correct dimension sizes.
Current Behavior
The model does not error out or crash. It completes.
See above.
Possible Solution
Provide a check when forcing files are read in to ensure the dimension sizes match that of the geogrid file.
Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: