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
The use of the term "unit hydrograph" for both the overland flow to the channel, and again for flow within the channel, appears to be confusing for new users. I think it would be possible to clear up some of the confusion by changing the name of the overland unit hydrograph from UH_BOX (which may not connote overland flow to a new user) to UH_land or something similar. Along the same lines, perhaps call the other unit hydrographs UH_channel or something similar.
Also, perhaps the presence of 2 steps, each involving different unit hydrographs, could be made clearer in the documentation by changing both the text on the readthedocs page to clearly label the 2 stages and also by numbering the stages explicitly in the left-hand menu bar.
These are just suggestions, but might help.
The text was updated successfully, but these errors were encountered:
Sure, I can try to work on it when I have time, but I wanted to get feedback on the idea before putting any effort into it... Now the issue's on the table.
The use of the term "unit hydrograph" for both the overland flow to the channel, and again for flow within the channel, appears to be confusing for new users. I think it would be possible to clear up some of the confusion by changing the name of the overland unit hydrograph from
UH_BOX
(which may not connote overland flow to a new user) toUH_land
or something similar. Along the same lines, perhaps call the other unit hydrographsUH_channel
or something similar.Also, perhaps the presence of 2 steps, each involving different unit hydrographs, could be made clearer in the documentation by changing both the text on the readthedocs page to clearly label the 2 stages and also by numbering the stages explicitly in the left-hand menu bar.
These are just suggestions, but might help.
The text was updated successfully, but these errors were encountered: