Error Messages/42510


Warning text

 Bounds Check Warning: Possible Mistake Detected
  
 There is a good chance you may have a mistake in the Definition of 'Rollover_credit' involving an
 equal (=) or not-equal (<>) comparison of 'Carbon_tax_active' to 1.
  
      If Carbon_tax_active=1 Then ...
                          ^
  
 This appears to be a probable error because the value 1, which is being compared to, is not a legal 
 value for 'Carbon_tax_active' according to the domain for 'Carbon_tax_active'.
  
 Would you like to stop the evaluation and edit 'Rollover_credit'?
  
 [  ] This expression is as intended, don't warn me again

Cause

This message simply indicates a certain "red flag" was detected that is often symptomatic of a mistake in your model. Most the time you see this, you probably do have a mistake, possibly one impacting the logic of your computation, that might otherwise go unnoticed. Ignoring this warning will not prevent your model from computing a result, but it is still wise to take a closer look because you might find that there is an error lurking there that you didn't realize was there.

In the example that generated the message above, the variable Carbon_tax_active is configured as follows:

Screenshot 42510.png

The values of this variable will be either "Yes" or "No". But, the expression in the definition of Rollover_credit treats this variable as if it were zero-one defined:

If Carbon_tax_credit=1 Then ...

The mistake causes the comparison to always fail and the Else clause to always be taken.

Remedy

If there is a mistake in your model, then the remedy is to correct the mistake as appropriate, which may either involve changing the definition with the comparison, or by changing the domain of the variable being compared to.

The mistake in the above example was corrected by changing the definition of Rollover_credits to:

If Carbon_tax_credit = 'Yes' Then ...

If you believe the definition is correct as written, you can check the checkbox and it will suppress this warning for this variable in the future (it does this by setting the UseCheck attribute). The warning will continue to display if other variables are detected that appear to have the same problem.

It is possible to turn off this check globally, but this must be done from the Typescript window. Press F12 to open the typescript window, and then type:

> (checking := Mod(checking, 3) + 8)

(The > character above is the typescript prompt, which you don't type)

See Also

Comments


You are not allowed to post comments.