...
- The Instream Processing model was given the entire body of water associated with the feature. I don't really get this, is this correct: The Instream Processing model uses the entire body of water...
- The processing model would run once per time step for each constituent.
...
The 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 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.
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.) This kind of suggests that it would be more sensible to use Lumped routing
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 function? 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:
...
Additional recorders were requested to better understand the water that has been ordered for use in functions. could it be simplified to 'the water ordered for use in functions'when using functions.
We have added recorders with the following names under rules-based-ordering:
...
Full Release Documentation
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|