- 1 Introduction
- 2 Basic Chart Navigation
- 3 I&I Tool
- 4 Overflow Events Table
- 5 The "Advanced User Editor" Tool
- 5.1 How to access the "Advanced User Editor" tool
- 5.2 Glossary
- 5.3 General Usage of the Interface Table
- 5.4 Overview of the "Advanced User Editor" tool for HVQ
- 5.5 How to use the "Advanced User Editor" tool for HVQ
The Inflwow and Infiltration analysis tool allows the user to calculate the impact of the rain on a catchment. For detailed information on using this functionality see the Inflow_Infiltration_Analysis_Tool article.
Overflow Events Table
The "Advanced User Editor" Tool
This tool has been developed to enable the advanced user to do basic data processing for HVQ, Flume/Weir and Level/Overflow sites.
How to access the "Advanced User Editor" tool
If enabled, the tool is accessible via the "more options..." button on the details window for each gauge (as shown in picture below). Each gauge type will open the appropriate Advanced User Tool.
Below some useful jargon used in the following paragraphs:
- AF - Adjustment Factor used to compute preliminary velocity.
- DPrelim - Preliminary depth, result of primary depth after offset applied and spike removed. Virtual entity.
- DtoD - Depth to Discharge table used to compute QRating.
- PDepth - Pressure depth sensor. Raw entity.
- Primary Depth - Name of the raw depth entity used as DPrelim at any given time.
- Primary Flow - Name of the quantity used as QPrelim at any given time.
- QContinuity - Flow computed with the Continuity equation. Virtual entity.
- QPrelim - Preliminary Flow, combination of primary flow and secondary flow if selected.
- QRating - Flow computed with a rating equation or table. Virtual entity.
- Raw entity - any entity sent from the monitor to the ftp. Raw entities are fixed and stored in the database
- RawVel - velocity sensor. Raw entity.
- SDepth - Down ultrasonic depth sensor. Raw entity.
- Secondary Depth - Name of the raw depth entity used as a "back up" depth at any given time.
- Secondary Flow - Name of the quantity used as a substitute flow at any given time.
- UpDepth - Up Ultrasonic depth sensor. Raw entity.
- Virtual entity - any computed entity via the interface. Virtual entities are computed "on the fly" and are not stored in the database.
- VPrelim - Preliminary velocity, result of RawVel after AF applied and spike removed. Virtual entity.
For consistency purposes, all depths in the process are in mm, velocities in m/s, flows in L/s and areas in m2.
General Usage of the Interface Table
- Adding a new row: Any new row will be added at the top of the table. Once saved, the row is ordered.
- Table length: There isn't a limited number of rows for any table.
Overview of the "Advanced User Editor" tool for HVQ
- Primary Depth Editor - Enables the user to choose primary depth at any given time (UDepth, SDepth, PDepth, LRDepth, etc...). It's the only requirement to compute DPrelim.
- Secondary Depth Editor - Same as Primary depth, enables the user to choose a secondary depth at any given time. If a secondary trace is selected it could be used as a substitute to primary depth when spikes are identified.
- Spike Filter Editor - Enables the user to identify and remove spikes for DPrelim and RawVel.
- Velocity Editor - Place to edit the AF table to compute VPrelim. Required to compute VPrelim
- Continuity Editor - Table to edit silt measurement with the related pipe table. Required to compute QContinuity.
- Rating Editor - Table to edit DtoD table or rating equation. Required to compute QRating.
- Q Preliminary Editor - Enables the user to choose the primary and secondary flow at any given time.
How to use the "Advanced User Editor" tool for HVQ
Primary Depth Editor
This first table enables the advanced user to choose the better depth sensor at any given time to be displayed as DPRELIM. An offset can be applied to the Primary Depth selected. The offset can be either negative or positive. The table can contain as many rows as user desire.
Selecting Primary Depth: The drop down in this column gives the user the choice of depth sensors available for that particular gauge.
Updating the table: The result of this table is DPRELIM which is a virtual entity. Any change on the Start time, Primary Depth or Offset will trigger the re calculation of DPRELIM.
Secondary Depth Editor
Similar to the Primary Depth Editor, this table enables the user to choose a Secondary depth trace. This secondary trace would be an option of substitution to the primary depth trace when spikes are identified.
Offset can also be applied to the Secondary Depth.
This table has the same edit options than the Primary Depth Editor.
Spike Filter Editor
This table enables the Advanced User to identify and remove spikes from the Primary Depth as well as identify bad data points for the RawVel entity.
- Entity Selection: As mentioned above the user is able to choose between DPRELIM and RAWVEL.
- Method: Two choices are available to the user to remove the identified spikes:
- Last Good Point: This method keeps the data point immediately before the spike - identified as "good" - and replaces the "bad" points with it.
- Secondary Depth: Method only available for DPRELIM, it will substitute the bad points from Primary Depth with the data points from Secondary Depth at the exact same time.
- Max Spike Threshold: Value required for spike identification. It represents the maximum absolute difference considered normal between 2 consecutive data points. Any data point with an absolute difference greater than this threshold will be considered bad and be replaced.
- Dropout Threshold: Mostly used for RAWVEL, it represents the minimum acceptable value for the entity. Any point below that threshold would be considered as bad and be removed.
N.B: More than 3 bad points in a row are currently not recognized as bad hence are not replaced.
This table enables the Advanced User to upload and edit the AF table to applied to RAWVEL. The outcome of this table is VPRELIM.
- Depth to AF Table: This is a subtable that stores the AF values for each Depth
- Calculation philosophy: This table is derived from gauging calibration were for each depth recorded is associated a velocity. AF are extracted from there. Between 2 values the AF is interpolated in a straight line. Above the last depth value it is a flat extrapolation.
N.B: This table needs to be filled in order to compute VPRELIM. At Gauge creation it can be decided to insert 1 as AF to allow the client to visualise VPRELIM
The Continuity Editor tables allows the Advanced User to upload and edit the Pipe Table for the gauge as well as keeping a record of any silt measurement that may occur at the monitored location.
The result of this table displays QContinuity
- Silt: Entered in mm this column keeps a record of the silt measurements and any change that may occur. It does not trigger the generation of the Pipe Table automatically.
- Pipe Table: Store the Depth to Area table related a silt measurement.
This table stores values for Quantity Rating calculation. To compute QRating, the user has the choice to use either a equation or a depth to discharge table.
- Equation: The equation needs to be entered as a PostGres friendly format:
- There as to be a * before any 'x' to be recognized as the value to be replaced.
- Brackets are required for negative powers. Positive powers do not need to be placed in brackets.
- DtoD table: Between 2 depths, the flow is interpolated in a straight line. Above the last depth value, it is extrapolated as a flat line.
Quantity Preliminary Editor
This table needs to be filled to compute and display QPRELIM.
- Primary Flow: Similar to Primary Depth, this column allows the Advanced User to choose the best quantity at any given time to display it as QPRELIM. The dropdown gives a choice between QRating and QContinuity.
- Secondary Flow: If chosen, Secondary flow trace will be substituted to Primary Flow trace when that one is considered to be bad.
- Max flow threshold: Flow value above which the Secondary flow will be used. Not relevant if Secondary Flow is not chosen
- Min flow threshold: Flow value below which the Secondary flow will be used. Not relevant if Secondary Flow is not chosen.