Reactis Validator performs automated searches of models for violations
of user-specified requirements. If Validator finds a violation of a
requirement, it returns a test that leads to the problem. This test may
then be executed in Reactis Simulator to gain an understanding of the
sequence of events that leads to the problem. This tool enables the early
detection of design errors and inconsistencies and reduces the effort
required for design reviews.
The current version of Validator works by temporarily creating a new model consisting of the old model with subsystems added for the associated diagram-based assertions and user-defined targets. The coverage targets tracked during test generation are then computed for this new model. As a result, some new coverage targets relating to the Simulink/Stateflow structure of assertions are included.
Our thought in doing this was that having coverage information about assertions was useful to see ``how close'' an assertion came to being violated during the execution of a given test suite.
If you are using Reactis V2011.2 or later, you can disable the tracking of
coverage targets within an assertion system by right-clicking on the assertion
in the model hierarchy tree (left panel) in Reactis and then selecting "Coverage
The likely answer is that, after inserting the objectives using Reactis, you changed the structure of your model using Simulink, and the wiring and structural information regarding where some objectives were placed is no longer valid. You can re-insert these objectives as follows: