d list This creates in the current directory a file v76_feed.wri29 containing the feed commands feed dlcasu l_estabreq (0) feed dlcasu l_estabreq (1) 4.3.1.5 Create a startup file To avoid entering feed commands manually and executing the four process start transitions each time we launch the Simulator, you will create a startup file. Remember to always invoke the ObjectGeode tools from your working directory. If you launch the ObjectGeode Editor and then navigate to another directory to open the SDL model, the Simulator might not run in the directory where the SDL model is; thus the startup file will not be found and SO on. This is especially true for older versions. A. With a text editor30, create the file 31 v76.startup (and NOT v76.startup.wri) in the current directory, containing source v76_feed.wri source start.scn The files v76_feed.wri and start.scn were described in the previous sections. The next time you run the Simulator, it will automatically execute the file v76.startup. This will load your feed commands and execute the four process start transitions. See details on startup files in Section 4.3.7.2. 29 The purpose of the . wri extension is to provide automatic opening of the file by WordPad in Windows. 30 To easily open any file in Windows, we recommend that you create a shortcut to WordPad on your desktop. Then simply drag the file on the shortcut to open it. 31 Warning: in Unix if you name the file V76.startup, the Simulator will not load it, because it does not expect the capital V. Interactive Simulation 75 4.3.2 Validate against the main scenarios Now the Simulator is ready to check that the SDL model behaves as described in the MSCs drawn during the analysis step in Section 3.3. You can compare 32 the analysis MSCs and the MSCs recorded during simulation. 4.3.2.1 Prepare the simulator for MSC recording You would have carried out the steps described in the previous sections (SDL tracking, feed, etc.). A. In the Simulator, press the Start MSC button: the Editor opens a new window containing an e