Running the L2 Simulator


Running the simulator without extra filters is easy. The complete set of directions can be found in D0$LEVEL2$DOC:L2SIM.DOC. Note that the simulator works only on FNALD0 (not the alpha cluster or the sgi's). Terry Geld posted a message describing the minimum set of banks you need to run the simulator -- read it!

  1. In a clean directory and new window, do "$ d0setup trigsim l2prod top" to get the most recent production version of the l2 trigger simulator.
  2. @D0$LEVEL2:SETUP_L2SIM <x>, where x is "D" for data, or "C" for MC with cadmake, or the monte carlo series letter ("N", "P", "Q", "R", or "S"). Choose "1", when prompted, for the standard versoin of the simulator.
  3. A file called L2LIB_SETUP.COM will be left in your directory. Execute this next time, in place of the setup_l2sim file. DEB_D0USER and D0USER are both defined.
  4. Run as you normally would run any other D0USER image.

The trigger list output will be dumped to DOUSER_SUMMARY.TXT.

Be careful what you use the window for after doing the d0setup. Many logicals are redefined! To recover your window, you can use the command "$ d0setup trigsim reset".


Linking in our own filter is a little more complex -- refer to the l2simualtor document for details.


Running your own trigger configuration file is also a little more involved. It is best to start by modifying the global trigger list.

  1. Copy global trigger list from D0$CONFIGS$SOURCE:DZERO.GLB-TRIGLST. You can find all the trigger lists there by doing dir D0$CONFIGS$SOURCE:*.*TRIGLIST.
  2. Copy over the resource file from D0$CONFIGS$SOURCE:TRIG_RESOURCES.CTL.
  3. Parse the default trigger list. This will fill your directory with various trigger definition files. The command is "$ TRIGPARSE DZERO.GLB-TRIGLIST".
  4. Find the trigger or filter script you want to modify and change that file. It may help to look at the global trigger list file as a road map. The .trig files contain trigger definitons, and the .filt files contain filter definitions (i.e. JET_MIN.FILT).
  5. Finally, you must rebuild the conversation the online COOR program has with the trigger frameworks: "$ COOR_SIM." Enter "RESOURCE" for the resource file name, and DZER0.CFG for the conf file name. Note that DZERO.CFG includes most of the other .filt and .trig files.

You should be ready to run VMS_FILTER again. Logicals have already been defined so that it should pick up your new trigger list.


Gordon Watts 3/30/95