The number of discrete rainfall events that you extract from a continuous time series of rainfall data is inversely proportional to the specified minimum inter-event time. If you use a smaller value for the minimum inter-event time, you will have a larger number of smaller rainfall events. If you use a larger value, you will have a smaller number of larger rainfall events. In terms of an I/I study, you seek to match rainfall with a flow response in the sewer. Therefore, think of the minimum inter-event time as a default value, not as an ideal value. As you review the I/I responses, you will find cases where the default values work out just fine, and you will find other cases where individual adjustments need to be made. Combining two adjacent rainfall events into one larger event is a common example. Use a reasonable default setting to do most of the work for you, then apply your engineering judgement to adjust other Rainfall Events as needed.
You may also like
An ultrasonic level sensor measures only distance to the liquid surface, converting that to depth, while an ultrasonic flow sensor uses ultrasound […]
No. PRISM supports the import of .xml location files only.
Real-time monitoring is the continuous collection and transmission of sensor data with minimal delay, enabling near-instant visibility into sewer conditions and faster […]
If you have the appropriate user permissions, select the Customer Editor icon to the right of the Customer drop-down list. Then choose […]