User`s guide
25 Create Model Advisor Checks
25-24
• dependson - Specifies a prerequisite subcheck. Optional. For example, to specify that
configuration parameter subcheck ID_B must pass before configuration parameter
subcheck ID_A is run, use this tagging:
<PositiveModelParameterConstraint id="ID_A">
<dependson>ID_B</value>
</PostitiveModelParameterConstraint>
Data file tagging specifying a configuration parameter
The following tagging specifies a subcheck for configuration parameter SolverType. If
the configuration parameter is set to Fixed-Step, the subcheck passes.
<PositiveModelParameterConstraint id="ID_A">
<parameter>SolverType</parameter>
<value>Fixed-step</value>
</PostitiveModelParameterConstraint>
Data file tagging specifying configuration parameter with fix action
The following tagging specifies a subcheck for configuration parameter
AlgebraicLoopMsg. If the configuration parameter is set to none or warning, the
subcheck passes. If the subcheck does not pass, the check fix action modifies the
configuration parameter to error.
<PositiveModelParameterConstraint id="ID_A">
<parameter>AlgebraicLoopMsg</parameter>
<value>none</value>
<value>warning</value>
<fixvalue>error</value>
</PostitiveModelParameterConstraint>
Data file tagging specifying configuration parameter with fix action and prerequisite check
The following tagging specifies a subcheck for configuration parameter SolverType.
The subcheck for SolverType runs only after the ID_B subcheck passes. If theID_B
subcheck does not pass, the subcheck for SolverType does not run. The Model Advisor
reports that the prerequisite constraint is not met.
If the SolverType subcheck runs and SolverType is set to Fixed-Step, the
SolverType subcheck passes. If the subcheck runs and does not pass, the check fix
action modifies the configuration parameter to Fixed-Step.
<PositiveModelParameterConstraint id="ID_A">