...
Figure 3. Input parameter set using a file
Child Scenario Input Sets
Child scenario input sets allow you to further refine model structure. A child scenario input set inherits all parameters and data sources specified in its parent. You can then set additional parameters, or alter existing ones. When you choose to run a model with the child scenario input set, the parameters from the child will take precedence over the parameters from the parent.
, because parameters in the child take The child inherits parameter changes in the child take precedence o A child input set inherits all parameters from its parent, and allows you to set additional parameters, taking precedence over parameters from the parent.
Testing correct results:
1. Can't delete the last input set. ("Can't delete last")
2. Child can have same name as parent. ("Can have same name as parent")
3. Child can have same name as other children in other branches. ("Can have same name as other branches")
4. Child can't have same name as another child in the same branch. ("Can't name same as in branch")
5. Deleting a parent also deletes the children. ("Before parent delete" + "After parent delete")
6. Only root level input sets can specify datasources. ("Parent only datasource")
7. Root level input set affecting nodes works correctly and does not affect the GUI. ("Deactivate Inflow 100MLd IS") With the left inflow deactivated, only the right inflow reaches the confluence. ("Result - Deactivate Inflow 100MLd IS")
8. Child input set affecting nodes inherits it's parents changes correctly and does not affect the GUI. ("Deactivate Inflow 200MLd IS") With both inflows deactivated (one by the child and one by the child inheriting from the parent), no flow reaches the confluence. ("Result - Deactivate Inflow 200MLd IS")
9. Closing and saving the project, then reopening source does not cause any issues and everything is persistent.