Im trying to use a version 12 trigger list (in .xml form) and p15 TrigSim, but its crashing on the impact parameter (IP) triggers or giving me COOR errors. Whats wrong?
When TrigSim translates a .xml triggerlist into the *.sim files it needs (using “coorsim”), some values are extracted from the COOR name server. If COOR is not set up correctly, this can cause problems. IP triggers are known to have such problems. To get around this, you need to execute the coorsim command yourself before running TrigSim. Create a file in your working area called l3ns.cmd. Edit the file to read: ns set l3_beam_pos.x 0.0 ns set l3_beam_pos.y 0.0 ns set l3_beam_pos.yz 0.0 ns set l3_beam_pos.xz 0.0 load triggerlist_file_name start where triggerlist_file_name is replaced with the name of the triggerlist file you wish to use, minus the .xml. Issue the command coorsim triglist-name.xml l3ns.cmd. The triglist… parameter is really ignored; it is the “load” command in the l3ns.cmd file that is really what is needed. Copy or move the files that get produced into your trigsim subdirectory. You should then be able to continue to execute TrigSim as usual without any additional co
Related Questions
- Im trying to use a version 12 trigger list (in .xml form) and p15 TrigSim, but its crashing on the impact parameter (IP) triggers or giving me COOR errors. Whats wrong?
- When does the Governing Council remove or de-list membership names form its institute Register list?
- What will happen if a new version of the Form becomes available?
