Trigger Lists

D0TrigSim should run either with specially written MC triggerlists, online lists or any other list that comes from the Trigger Database . Please be aware that new online lists can contain things that your release of D0TrigSim simply can't handle or that the version of COOR released offline cannot yet parse. We do eventually catch up.....but it will not always work to run today's online trigger list offline in the latest production release.

There is a generic trigger list for MC studies....however, it cannot be used with current trigsim releases (being revised and updated). You can still look at the current version: tsim_p09 version 1.00.

Instructions

  1. Use the XML generator to extract a trigger list from the database (clued0 or d0mino). 
    setup d0cvs
cvs co trigdb_xmlclient
cd trigdb_xmlclient
gmake
source bin/xmlclient_setup
./xmlgen.py --tlist-name global_CMT --tlist-version 8.20 --file --Sim

OR

./xmlgen.py --tlist-name tsim_p09 --tlist-version 1.00 --file --Sim

OR 

whatever list you choose.....

    Note:

    If you get an error that looks like: 
       xargs: environment is too large for exec
    then you need to run it in a new window in which the "setup D0RunII ..." command has not been given. The "setup D0RunII ..." command sets a lot of environment variables and this can sometimes confuse external packages.
  2. Process the xml file through COORSIM and run D0TrigSim: 
    setup D0RunII version (eg. p12.02.00)
setup d0tools -t
runD0TrigSim -filelist=filelist -trglst=myfile.xml -format=mc
    This will cause COORSIM to run create a subdirectory called trigsim containing a bunch of "sim" files with which to configure the trigger simulation. It will then run d0trigsim on them using these configuration files. You are done.
  3. Once you have this directory full of *.sim files you can put those files aside and use them again as often as you'd like without going back to the *.XML file. Just create a trigsim subdirectory, copy the files into it and 
    setup D0RunII version (eg. p12.02.00)
setup d0tools -t
runD0TrigSim -filelist=filelist -format=mc
    D0TrigSim will find your new *.sim files and will override the default set.
Gordon Watts has also written a detailed set of instruction for doing this (thanks Gordon!!). Take a look at Gordon's description.

Pre-fixed Lists

Here are some interesting lists with the simfiles provided for your convenience. Why do I do this? Because sometimes you cannot use the COOR version from the same release as the d0trigsim version you want to use. This will go away in a future version of COOR....but for now it is easiest if someone just does some pre-processing for you with the latest test-release version of COOR.
list name/version list contents xml sim tarball comments
tsim_p13 1.20 db tsim_p13-1.20.xml tsim_p13-2.10-mc.tar

tsim_p13-1.20-data.tar

tsim_p13-1.20_toollist.txt

notes:
  • this is the first triggerlist which is L3 compatible in p13. It will be made into the default list for d0trigsim. In p13->p13.04.00 the default list will not properly configure L3.
  • -mc corresponds to making the level2.sim-stripped correction and changing the level3.sim geometry management, CFTunp and SMTunp settings. The L3 geometry is set to p11.08.00, edit this line yourself if your inputs are different. The settings of level3.sim are the same as for global_CMT 9.30 below....and need review by an L3 expert as well....
  • -data corresponds to making the level2.sim-stripped correction and leaving level3.sim alone.
  • A toollist.txt is provided which corresponds to this triggerlist but with the L3 unpack tools removed. Until we get a new version of Heptuple in p13 use this toollist to greatly reduce the crashes when producing the ntuple. Use the -l3toolist commandline option to pass this list to the executable.
global_CMT 9.30 db global_CMT-9.30.xml global_CMT-9.30-mc.tar

global_CMT-9.30-data.tar

global_CMT-9.30_toollist.txt

notes for p12:
  • -mc corresponds to making the level2.sim-stripped correction and changing the level3.sim geometry management, CFTunp and SMTunp settings. The geometry is set to p11.08.00, edit this line yourself if your inputs are different. NOTE: I know I made the right fix to level2.sim-stripped....however I edited level3.sim so that results came out....no L3 expert has yet verified the correctness of the edits: 
            GEO L3GeometryManagement(
                tooltype="utility",
                MCTag="p11.08.00")|

        CFTUnp L3TCFTUnpack(
                tooltype="unpack",
                adcthreshold=20,
                maxfibers=8,
                basegeom="CftBaseGeometry",
                channelgeom="CftChannelGeometry",
                realdata=FALSE)|
        SmtUnp L3TSmtUnpack(
                chanthreshold=.03,
                maxstrips=16,
                basegeom="SiBaseGeometry",
                channelgeom="SiChannelGeometry",
                adcthreshold=10,
                clusterthreshold=.03,
                tooltype="unpack")|
  • -data contains my edits for level2.sim-stripped, but no edits of level3.sim.
  • A toollist.txt is provided which corresponds to this triggerlist but with the L3 unpack tools removed. Until we get a new version of Heptuple in p12 or p13 use this toollist to greatly reduce the crashes when producing the ntuple. Use the -l3toolist commandline option to pass this list to the executable.
global_CMT 8.20 db global_CMT-8.20.xml global_CMT-8.20-coor.tar

global_CMT-8.20-data.tar

global_CMT-8.20-mc.tar

notes for p12:
  • -coor tarball is what comes out of COORSIM with no hand-edits.
  • -data corresponds to editing level2.sim to add some missing lines.
  • -mc corresponds to making the level2.sim correction and changing the level3.sim geometry management, CFTunp and SMTunp settings. The geometry is set to p10.06.01, edit this line yourself if your inputs are different.

How to Fix a List - Current=p12/p13