Reality Check is run by first setting up a simulation and then testing one or more of the Reality Check equations you have entered.
You can start Reality Check from the Toolbar or from the Simulation Control dialog (see Simulating in the Reference Guide for details on these). You can make changes and adjust other options just as you would for a normal simulation. After you have done this click on Reality Check in the Simulation Control dialog or click on the Reality Check button 
on the Toolbar.
NOTEAny changes you have made to constant values, data to be used, and so on prior to launching Reality Check will continue to hold throughout the Reality Check session.
When you launch Reality Check, the Reality Check Control dialog appears:
Test type (not PLE or PLE Plus) allows you to specify which type of Reality Check you want to test. If this is blank all types will be tested. The type of a Reality Check is indicated in the TypPrio field of the Equation Editor. In the Text Editor Type, and Priority are enclosed in square brackets [ ] in the units field (~[type,priority]). This field is only applicable when the Test All button is used to start testing.
Priority >= (not PLE or PLE Plus) will restrict testing to only Constraints having a priority bigger to or equal to that specified. This field is only applicable when the Test All button is used to start testing.
NOTEIf Constraints do not have a priority specified, they are treated as highest priority. If Constraints do not have a type specified they are assumed to match all types.
Show Graphs is used to display a graph of the variable being tested in the Consequence portion of a Constraint against the behavior that variable needs to conform to. This is done using a special invocation of the Graph Tool and can be very helpful for understanding the manner in which the failure occurred.
| • | Always, if checked, causes a graph to come up for each Constraint Checked. |
| • | Never, if checked, suppresses graph output. |
| • | Sim/Fail, if checked, causes graphs to appear whenever a Reality Check fails, and also when a single simulation is made using the Sim Active or Highlighted buttons. |
| • | On Fail, if checked, causes a graph to come up only if a Reality Check fails. When you use the Test All button this is the same as Sim/Fail. For the Sim Active and Highlighted buttons this suppresses the graph unless there is actually a failure. |
Constraints is a list of Constraints you have entered. Clicking on one of these will highlight the corresponding Test Inputs. You can then activate one or more of these Test Inputs.
Test Inputs is a list of the Test Inputs in the model. This list includes everything you defined explicitly as a Test Input, and all comparisons in the logical expressions making up the condition components of Constraint equations. Comparisons are shown directly and not given a name.
>> moves the highlighted items in the Test Inputs list to the Active Test Inputs list.
<< removes the highlighted items in the Active Test Inputs list.
Clicking on an element in the list highlights it. Control-clicking toggles the highlight status adding or removing it from the selection of highlighted elements. Double clicking moves the item to the Active Test Inputs list.
Active Test Inputs shows a list of the Test Inputs, explicit and implicit, that are active. These will be used when the Simulate Button is clicked. Clicking on an element highlights it, and unhighlights anything else that may be highlighted. Control-clicking toggles an element's highlight. Double clicking removes an element from the list.
Clear All Active removes all elements of the Active Test Inputs list.
Sim Active simulates the model using the active Test Inputs in the list. All other Constraints are tested passively. If the simulation succeeds the results will be stored just as for a normal simulation, and you can review them with the tools on the Workbench. Be careful to note that causal tracing will not always give the expected results since model structure may have been changed during the simulation.
Highlighted simulates the model using the item highlighted in the Constraint list. Because of the logical structure of the condition portion of a Constraint this may actually require more than one simulation. The final simulation will be stored just as a normal simulation.
Test All tests all the Constraints in the model one at a time by forming the collection of Test Inputs necessary to activate each Constraint. Because of the logical structure of the condition portion of a Constraint equation, it may take more than one simulation to test a Constraint. This testing can be time consuming, activity and errors are reported in a separate window. Running Test All does not store any simulation results but simply reports the results of Reality Check.
Close closes the Reality Check Control dialog.
