The changes in this beta will also be available in the next Source production release.
This release includes:
EEWD: We have added five features, inheriting parent forecast scenarios to all child nodes, changes to netCDF export functionality, persisting zoom for a chart, inserting a node between two links without loosing the link data, and extending the override functionality to a function in tabular editor, these are discussed in detail below.
IRMU: Improvements were made to spell observer settings in order to allow ordering based settings and enhanced spell observer recorder.
Other enhancements and bug Fixes.
EEWD:
Scenario Input Sets - Inherit Forecasts from parent to all of the child scenario nodes
When a new child is added to a Scenario Input Set, if its parent is already selected for a Forecast Scenario (from the feature table of the corresponding node), the child will also be automatically selected for that forecast scenario. If the newly added child’s parent is not selected, the child won’t be automatically selected.
Out of the available six forecast models, only the Pulse Forecast Model’s settings were not exposed in the Input Sets. We have now made Pulse Forecast models configurable from Scenario Input Sets.
Users can now configure the settings of Forecast Scenarios from the Scenario Input Sets, specifically the selected Input Sets for the Forecast Scenarios.
The feature table now displays all six Forecast Model types in a separate section. Selecting each type will list all the Forecast Models in the network that fall under that type. The parameters of those forecast models can also be configured from there.
The feature table now includes a section called 'Operation Forecast Scenarios' that displays all the Forecast Scenarios in the model. From this view, users can configure the Scenario Input Set selection for each Forecast Scenario.
User input validations for the above tables in the Feature Table are done similarly to how they are done in the Feature Editor of the nodes. For Example:
Insert node without breaking the links
The user now has the option to insert a node into the network by right-clicking on a link. This action will show a new option in the right-click menu named 'Insert Node Model,' which will list all the nodes eligible to be inserted into the network. The user can then select a node insertion strategy based on the given four options.
Node Insertion Strategies:
Before Insertion: Node A ------> Original Link -----> Node B
Option 1: Upstream: original link, Downstream: new default link
After Insertion: Node A ------> Original Link -----> New Node ------> New Default Link -----> Node B
This option will unhook the downstream of the original link (the link the user right-clicked) and attach it to the new node’s upstream. A new default link (a straight-through routing link) will be inserted downstream, with its upstream being the downstream of the new node and its downstream being the upstream of the following node.
Option 2: Upstream: new default link, Downstream: original link
After Insertion: Node A ------> New Default Link -----> New Node ------> Original Link -----> Node B
This option will unhook the upstream of the original link and attach it to the new node’s downstream. A new default link (a straight-through routing link) will be inserted upstream, with its downstream being the upstream of the new node and its upstream being the downstream of the previous node.
Option 3: Both streams: new links with original link properties
After Insertion: Node A ------> New Link with Original Link Properties -----> New Node ------> New Link with Original Link Properties -----> Node B
This option will replace the original link with two new links that maintain the properties of the original link. The new node will be inserted between these two new links.
Option 4: Both streams: new default links
After Insertion: Node A ------> New Default Link -----> New Node ------> New Default Link -----> Node B
This option will replace the original link with two new default (straight-through routing links) links. The new node will be inserted between these two new links.
Restrictions on Node Insertions:
There are existing restrictions applied considering the connections we can make between the nodes. The following restrictions were enforced in this implementation:
Nodes cannot be inserted into lateral links.
Scenario Transfer Node: Excluded from the eligible list of nodes because it cannot be inserted into the middle of a network (i.e., it can only have one link connected to it).
Bulk Licensing Node: Excluded from the eligible nodes because it can only be connected to the lateral links of the gauge nodes.
Water User Node: If the new node is a water user, its upstream should be a Supply Point and its downstream should be a Confluence.
Downstream Water User: If the downstream node is a Water User, the upstream node (i.e., the new node) should be a Supply Point.
Upstream Supply Point: If the upstream node is a Supply Point, there should be one and only one Water User connected to it.
3. Users will now be able to override functions in the Tabular Editor
Persistence of Zoom in charts : Re-running Source will no longer reset the zoom in the Results Manager, the zoom setting made on a chart will be persistent from now. The Toolbar > Reset Zoom will now work as expected (previously it wouldn’t reset the zoom until you then tried to zoom in with the scroll wheel).
netCDF Export functionality : We have made changes to netCDF export functionality to make it compatible with CF convention >=1.6
Currently in Source, we can export netCDF file but it is not compliant netCDF-CF file. Furthermore, the output should also need to contain the metadata contained as per the res.csv files that is exported and imported by Source. FEWS requires netCDF files to comply with CF convention 1.6 or greater.
IRMU:
Change in spell observer settings to use the same settings as ordering phase including spell start target, minimum duration, end target, duration below end threshold and seasonal settings.
There are few improvements made to spell observer recorder which include Graph, a red X for failed spells, Four new dates have been introduced in the 'Details' as shown in the below figures
Also, new recorders have been added to the Environmental Flow Manager to show debited volume from the accounts.
Other Enhancements &. Bug Fixes:
Minor enhancements and Bug fixes include:
Results Explorer crashes when invalid files are dragged into it. The bugs are fixed now.
Add --nopluginfile option to CommandLine options. Added Successfully.
Water user storage volume - area table needs resizing. Fixed.
Regression Testing
There is no tolerance in our regression test suite to allow for earlier identification of results being different on different machines or versions of operating systems.
See: 5.42 Regression Test Changes
Full Release Documentation
https://ewater.atlassian.net/issues/?jql=project%20%3D%20Source%20AND%20fixVersion%20%3D%205.42Beta