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
For transient models with thousands of reaches, the burden for specifying rainfall, runoff, evaporation values can quickly add up. For example, the input may look something like the following (though thousands of lines longer), where sw_rain_rate and sw_evap_rate are time series:
I was thinking it might be an enhancement to allow the user to instead specify a boundname in place of the reach number rno, then all reaches associated with that boundname could be provided a RAINFALL value with one line. So for example, if I had a group of reaches with the boundname 'mainRiv', the input could be reduced to the following:
BEGIN period 1
1 INFLOW main
mainRiv RAINFALL sw_rain_rate
mainRiv EVAPORATION sw_evap_rate
END period
and spare the input size. I think this would be a nice way to further leverage the boundname functionality.
The text was updated successfully, but these errors were encountered:
When entering PERIOD data in SFR, which takes on the form:
### FOR ANY STRESS PERIOD
The parameter
sfrsetting
can take on the following values;For transient models with thousands of reaches, the burden for specifying rainfall, runoff, evaporation values can quickly add up. For example, the input may look something like the following (though thousands of lines longer), where

sw_rain_rate
andsw_evap_rate
are time series:I was thinking it might be an enhancement to allow the user to instead specify a boundname in place of the reach number
rno
, then all reaches associated with that boundname could be provided aRAINFALL
value with one line. So for example, if I had a group of reaches with the boundname 'mainRiv', the input could be reduced to the following:and spare the input size. I think this would be a nice way to further leverage the boundname functionality.
The text was updated successfully, but these errors were encountered: