User`s guide

25 Create Model Advisor Checks
25-18
fixvalue of error. When you run the configuration parameter check using
ex_DataFile.xml, the check fails if the Block Priority Violation setting is
not error. The check fix action modifies the setting to error.
5
In ex_DataFile.xml, edit the Algebraic loop (command-
line:AlgebraicLoopMsg) parameter tagging so that the check warns if the value
is none. Because you are specifying a configuration parameter that you do not want,
you need a NegativeModelParameterConstraint. Additionally, to create a
subcheck that does not have a fix action, remove the line with <fixvalue> tagging.
The tagging for the configuration parameter looks as follows:
<!-- Algebraic loop: (AlgebraicLoopMsg)-->
<NegativeModelParameterConstraint>
<parameter>AlgebraicLoopMsg</parameter>
<value>none</value>
</NegativeModelParameterConstraint>
6
In ex_DataFile.xml, delete the lines with tagging for configuration parameters
that you do not want to check. The data file ex_DataFile.xml has tagging only
for Algebraic loop, Minimize algebraic loop and Block Priority Violation.
ex_DataFile.xml looks similar to:
<?xml version="1.0" encoding="utf-8"?>
<customcheck xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.w3schools.com
MySchema.xsd">
<checkdata>
<!-- Algebraic loop: (AlgebraicLoopMsg)-->
<NegativeModelParameterConstraint>
<parameter>AlgebraicLoopMsg</parameter>
<value>none</value>
</NegativeModelParameterConstraint>
<!--Minimize algebraic loop: (ArtificialAlgebraicLoopMsg)-->
<PositiveModelParameterConstraint>
<parameter>ArtificialAlgebraicLoopMsg</parameter>
<value>error</value>
<fixvalue>error</fixvalue>
</PositiveModelParameterConstraint>
<!--Block priority violation: (BlockPriorityViolationMsg)-->
<PositiveModelParameterConstraint>
<parameter>BlockPriorityViolationMsg</parameter>
<value>error</value>
<fixvalue>error</fixvalue>
</PositiveModelParameterConstraint>
</checkdata>