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
Calling bmi_noahowp%get_grid_spacing returns (/model%domaingrid%dy, model%domaingrid%dx/) (i.e., via bmi_grid%spacing). This behavior is consistent with BMI 2.0 specifications. However, as the units of dx and dy are not specified in the BMI 2.0 documentation, there is ambiguity regarding the appropriateness of the current implementation.
When executed in standalone (outside NextGen), dx and dy are read-into the model via the required domain attributes NetCDF file (which is expected to have global attributes dx and dy). The example attributes file (i.e., data/NorthForkAttributes.nc) contains a subset of the NWM 3.0 grid for the North Fork (WY) CAMELS test basin; hence, dx = dy = 1 km.
Suggested changes
Verify current implementation of bmi_noahowp%get_grid_spacing or amend implementation of dx and dy as needed.
The text was updated successfully, but these errors were encountered:
Current behavior
Calling
bmi_noahowp%get_grid_spacing
returns(/model%domaingrid%dy, model%domaingrid%dx/)
(i.e., viabmi_grid%spacing
). This behavior is consistent with BMI 2.0 specifications. However, as the units ofdx
anddy
are not specified in the BMI 2.0 documentation, there is ambiguity regarding the appropriateness of the current implementation.When executed in standalone (outside NextGen),
dx
anddy
are read-into the model via the required domain attributes NetCDF file (which is expected to have global attributesdx
anddy
). The example attributes file (i.e.,data/NorthForkAttributes.nc
) contains a subset of the NWM 3.0 grid for the North Fork (WY) CAMELS test basin; hence,dx
=dy
= 1 km.Suggested changes
Verify current implementation of
bmi_noahowp%get_grid_spacing
or amend implementation ofdx
anddy
as needed.The text was updated successfully, but these errors were encountered: