 Figure 5.43. If both are correct and if the MSC is consistent with the SDL model (for example, you would get an error if using a signal in the MSC not declared in the SDL model), it translates the SDL model into C code, and the MSC into an observer (in C). Then the C files are compiled and linked to the simulator library, to produce the executable file v76.sim. X v76.ogl ObjectGeode Launcher File Edit View Insert Build Options Help SDL & MSC Simulator Working directory (Default) F:\DONNEES\TRANSMET\livreSimul\modelsOGW76 v76.pr F:ADONNEES\TRANSMET\livreSimul\modelsOGW76W76.pr". 0 warning test1.msc F:ADONNEES\TRANSMET\livreSimul\models0GWroxtest1.msc" 0 information F:\DONNEES\TRANSMET\livreSimulBmodels00W76\test1.msc". 0 warning 0 error "F:\DONNEES\TRANSM livreSimul\models0GW76W76.p". information [6.12.1] line 64: CHOICEv76paramtyp not used Ready The MSC is checked Figure 5.43 After pressing the Build button 5.3.2.2 Replay the simulation scenario testl A. Press the Execute button to start the Simulator. The Simulator main window appears. B. In the Simulator, select View > Hierarchy¹1: as depicted in Figure 5.44, you now get a third area containing observation. It corresponds to the MSC testl you compiled with the SDL model. C. Unfold the observation part as in Figure 5.44, select testl and press the button Track: the Editor opens a window showing the hierarchy of MSC testl. Double-click the box testl to open it: a bold horizontal bar at its top, illustrated in Figure 5.45, shows the next signal input or output expected in the SDL model by the MSC. D. Replay the Simulation scenario (or fire transitions manually if you prefer): select File > Scenario > Load, choose testl.scn, and press the redo Simulator button nine times until Step 9, to get the MSC shown in Figure 5.45. In this figure, the lower horizontal bold bar shows you the next expected event in the SDL simulation: input of signal L_EstabResp by block DLCb. To help you, the Simulator displays at each step which events were observed by each observer; here, a