About Computational Subbasins
Computational Subbasins are created through the same dialogs as other subbasin types; but as with simulation objects, they contains slots and other attributes you can inspect and change by opening the subbasin. See Subbasin Manager in User Interface for details on creating, deleting, and viewing computational subbasins.
Computational Subbasins contain no general slots; all slots are dependent on user-selectable methods.
Selected slot values can be propagated from a computational subbasin to all member simulation objects. When you choose to propagate a slot named “S”, the value of the slot is copied to the slot named “S” on all objects in the subbasin. Propagation has no effect on member objects that do not contain a slot named “S”.
A subbasin can also be verified. The meaning of this depends on the selected methods. During verification, RiverWare performs checks that can be made prior to a run and that might discover errors before a run is begun so that such errors can be identified and corrected early.
A subbasin is either enabled or disabled.
• If enabled, it will be verified at the beginning of a run, and if its verification fails, the run terminates.
• If disabled, it will not be verified at the beginning of a run. This allows subbasin verification not to interfere with model runs while the model or subbasin is under development.
There are no general slots for computational subbasins.
Revised: 01/05/2024