Error Messages/42491

Example Error Text

The computed value for Decision_A_include_r_d_2 is not consistent with its domain
specification because the value 'Yes' is not listed as a legal value in the domain specification
at cell coordinate
    A_tecs1='Cellulosic ethanol' 
 
Do you want to stop evaluating and edit the definition?

Cause

This message is just warning you that a computed value is not consistent with its specified domain. It is just a warning, and you can continue by pressing [No]. But, when you see such a warning, it is a good idea to take a closer look to see if it may have possibly caught a logic error recently introduced into your model.

The Domain Attribute of a variable specifies the set of possible value for a variable. When a result is array-valued, the domain identifies the set of possibilities for each cell of the result. In the above message, it specifies the coordinates of the first cell that is inconsistent with the domain -- it occurs in the result of Decision_A_include_r_d_2 where the index A_tecs1 has the value 'Cellulosic ethanol'. The value in question is 'Yes'. In this case, the domain specifies a type, range or set of possible values for the variable Decision_A_include_r_d_2 which does not allow the value 'Yes'.

Using the Domain Attribute to specify the set of possible values can be a good practice for catching inadvertent mistakes, especially ones that might be introduced into the model in the future. It provides a level of validation, and this message is one such message results when that validation ends up being violated.

Remedy

The recommended remedy is press Yes to stop and fix the source of the problem. In the process, you might find a mistake in your model's logic, which is why stopping and fixing it is valuable.

A less desirable option is to simply ignore this message by pressing [Yes]. This does not prevent the model from evaluating. The least desirable option is to turn off bounds checking all together (from the Edit→Preferences dialog.

In the above example, when we examined the variable in question, there was indeed an accidental inconsistency that had been introduced. The Domain Attribute of the variable listed the explicit values [True,False], equivalent to [1,0], while the cells of the variable's edit tables contained pulldowns with values ['Yes','No']. In this case, the cells where defined as Choice(A_yes_no1,1,0), pulling their possible values from A_yes_no1, so we just changed the domain to Copy From Index and selected index A_yes_no1 for the domain.