Why doesn Reactis recognize a workspace variable in my model?
Although Reactis may invoke MATLAB to perform some tasks, Reactis does not directly interact with an executing MATLAB session in the same way that Simulink does. Consequently, any workspace data items that a model uses must be attached to a model using Simulink’s pre-load callback. For the cruise-control example included in the Reactis release, the file cruise_constants.m defines two workspace variables that are used in cruise.mdl. One attaches cruise_constants.m to cruise.mdl as follows: • Load cruise.mdl into Simulink. • From the Simulink window, select the File, Model Properties menu item. • In the resulting dialog, select the Callbacks tab. • In the Model pre-load function entry box enter cruise_constants. (note the .m suffix is omitted) • Save the model.
Related Questions
- I created a test suite from a model using Reactis, but when I run the tests within Reactis, the output values are different than those stored in the tests. Why is this?
- Does Utah recognize the Modified Series 65 and 66 Exams and model waiver provisions?
- Why doesn Reactis recognize a workspace variable in my model?
