...
- given access only to a single division, and
- run once for each division and constituent in a Link.
The precious previous logic wouldn't work when the model included hard limits e.g. in this model, the average concentration is not meant to exceed 9mg/L. When the Model runs for the entire Weir, we can see this is true on average:
But when we look per division, we can see that some divisions drop to 0 a while others can reach double the cap 18.
Changing the logic for weirs to be consistent with storage routing resolves this issue since the cap is applied in each division rather than across the entire link.
We have introduced a restriction, that this method won't work for lumped routing with weirs.Constituent Instream Processing for Weirs is restricted to Marker routing, i.e. it is not implemented for Lumped routing. (If Lumped routing is being used storages would make a more sensible model for the infrastructure than weirs.)
Sub Source plugin improvements
Previously mappings between main and sub-models were tied to a single run configuration. If you make a new run configuration then the mapping has to be redone. Sub Source mappings have now been moved into a manager so that the same mapping can be used by multiple run configurations. Available under Tools » Sub-model Manning Manager.
We have also improved how Sub Source works with single projects. For single projects, the plugin will now:
- get meta data from the loaded project rather than starting the service when doing configuration, and
- Run the current project without needing to manually save before the run
Documentation is available here: /wiki/spaces/SD50/pages/50136239
...
Additional recorders were requested to better understand the water that has been ordered for use in when using functions.
We have added recorders with the following names under rules-based-ordering:
...
Full Release Documentation
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|