...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Info | ||
|---|---|---|
| ||
This function is not available in Source (public version). |
Used for Operations scenarios, the Tabular Editor only contains information after a warm-up or scenario run and is positioned to the first time-step in the forecast period. Refer to Forecasting and Operations for details. It provides a spreadsheet-like representation of data that is otherwise presented in graphical form in the Recording Manager. Figure 1 shows an example of historical and forecast data in the Tabular Editor. The row where the cells have a pale blue background is the first day of the forecast period (ie. normally “today”). Rows prior to this show historical data. At this point, all values in the forecast period are zero because no forecasting has been done.
...
Figure 2. Show Column Editor (Column re-ordered)
Figure 3. Show Column Editor (Add group)
Customising the Tabular Editor
You can customise the Tabular Editor display to your needs. For each type of node or link, you can select:
- A background colour for the cell;
- A foreground colour and stylistic variation (eg. bold-face) for values displayed in the cell; and
- The number of decimal places to be displayed.
...
- To the entire table as a whole - by adjusting a set of user preferences. Refer to Tabular Editor Formatting. Changes made via this method apply to all projects; or
- To individual columns and cells - by right-clicking a column heading and choosing Column Formatting (refer to Customising columns). Changes made via this method only apply to the current project, and will override the Tabular Editor Format settings including templates.
...
- Individual column settings. Here, you can override project-related Tabular Editor Format Settings for the parameters displayed in the Tabular Editor (Figure 4);
- Create a header title (label) and choose the header colour for a column using the Header item (Figure 5); and
- Highlight when thresholds or rules are breached by specifying a function eg. Flow < 500 ML/day (Figure 6).
Figure 4. Column formatting
Figure 5. Column formatting, header
Figure 6. Column formatting, functions
Override Visualization Assistant
...
The developed function about Override Visualization Assistant can help the user to find the editable data in an operation model, enter and edit the comments for changed values and generate a summary table for all overridable values. The functions can be though the editable indicator, comment editor and view override command button.
Note that some parameters such as the modelled outlet release at a reservoir or a weir are not allowed to override.
Override editable indicator
...
Click on the cell with any pen icon, the user can enter an override value ( e.g. 200 965.35 on Figure 7). The new value (e.g., 200 965.35 to replace previous 0 sourced from a time series in Data Sources) will be used by the model running.
Also, when there are numerous entries Uncheck All (Figure 7) can be used to tick off all the entries and then only the required group can tick on.
Figure 7. Override Visualization Assistant
Override Values in Data Source
The Override function can also be used to fill in missing values of the time series being fed into the model. In Source 5.20, “Data Source” is available in the Tabular Editor to do so (Figure 8).
Figure 8. Override values in Data Source
|
|
For instance, time series data assigned to the flow of an inflow node can have missing values that the user can replace them in with new values in the operation Tabular Editor. However, if the time series of this node is used in multiple places in the model, the user can override the missing values through the time series “Data Source” in the Tabular Editor. This way the new values are propagated to all the usage of that Data Source in the model.
Comment Editor
Comment Editor can be accessed by right clicking on an editable cell with Pen icon and it then will display a menu item (Figure 89). Click on Edit Comment (shown in the orange box on Figure 89) will display a text box for the comment continents. The notice icon will be added to the cell (highlighted by the orange box on Figure 7) if the text box is with any contents (e.g., Demo add 200). Enter key can save the contents in the text box.
Figure
...
9. The menu for the Comment Editor
Other menu items on Figure 8 9 are described below:
Cut, Copy and Past are self-explained and can be used to edit the values in the selected cells.
...
Add Additional Cutout Line: by configured color in Scenario options, it can highlight one discontinuous line, which shows the water travel time between the selected cell and relevant columns on Tabular Editor table.
...
Lock Cutout line: it can lock the Cutout for deletion.
Override Summary table
Override Summary table can display all override values in the operation model. This function can be accessed also from Tabular Editor using command button View Override (highlighted by green box in Figure 7). Clicking on View Override will display a table (Figure 910) including all override values such as 200/”Demo: add 200” on 19/04/2021for Dam’s rainfall value and comments respectively, the unchanged value (i.e. zero) for Dam: Unaccounted Difference on 19/04/2021.
Figure
...
10. Override Summary
Clear Historical Overrides: this command button will clear overrides values in whole historical period and will only display overrides values in the forecast period (from “tomorrow “ only). This action is not reversed.
Minimum Flow Requirement nodes in Tabular Editor
Minimum Flow Requirement (MFR) nodes can now be accessed from the Tabular Editor and can be overridden. The recorder of Required Flow Arriving Current Timestep on MFR nodes was added to handle the complex concepts of the water flow due to the travel times. Required Flow Arriving Current Timestep recorder needs to be added to Tabular Editor as one column for Override if required (Figure 11). The user should override any cells in this column using the required flow that will arrive at the MFR node in the current time step considering the travel time. Another column/recorder of Required Flow is not editable in Tabular Editor and this Required Flow column reflects the default Required Flow, Forecast Required Flow and Overridden Required Flow at a source site (e.g., storage). The travel time in Figure 11 is three days and “today” in the operation model is 10/01/2000.
Figure 11. Override for Minimum Flow Requirement in Tabular Editor
