Production Release p12

Overall Status: It is based on t02.24.00. We are still building new pass-releases.

Notes for p12

Database, COOR, Lists
The version of COORSIM in p12 is not caught up with the latest online lists. If you want to run with a recent list you should look at the d0trigsim trigger list page. There you will find some pre-made sim files for recent lists and instructions on how to make them yourself. You will find several versions of the *.sim files to try to take account of the hacks below. So, if you grab the right set of *.sim files you should be able to skip the stuff below about editing *.sim files.
Alternatively, you can check out coor v00-56-00, compile it yourself and run it on your XML file. The next release or COORSIM will remedy version-compatibility issues like this.
Contributed Tips
- Disk space save Gordon Watts runs a version of TrigSim that saves on disk space. Here are his comments:
  I run trigsim in a slightly different mode that it was designed. I want to run trig sim, dump to root tuples, and if there are RECO chunks there, then I want to dump those also. And I'm running out of disk space so I don't want to write an intermediate file. I also wanted the latest version of the event_info package. Since trigsim and d0_analyze are simply a collection of framework packages, it is quite easy to make these changes. Everything I had to do (including the trigsim fixes [from p12.02.00]) is listed on [this] web page. Let me know if you find any errors.

P12.04.00 (10/10/2002)

Status IN PROGRESS: See certification plots.
Tricks Here are some things you should know about for this version (see also general tips above)
- level2.sim Need to add the following lines to the top of online triggerlists. Please note that the size of jet clusters below is 5x5. This is the new default setting for p12.04.00 and above.
```
L2CAL ADMIN CALJET_WORKER {
IETA_MIN = 0,
IETA_MAX = 39,
JET_SIZE = 5,
KEEP_CORNER = 1,
KEEP_ROW = 1,
DCLEAR = 4
}

L2CAL ADMIN CALEM_WORKER {
IETA_MIN = 0,
IETA_MAX = 39,
BOX_SIZE = 3
}

L2GBL ADMIN GLOBALWORKER {
    USEL1BITS = 0
}
```
- L3 On data: Some parts of L3 code need triggerlist configuration of geometry or unpacking. In practice this means that when you run on MC inputs you need a different level3.sim file than you do for data. You may even need a different level3.sim for each MC version. Here are the cases I know about and documentation for fixing things.
  1. rdc_run_config_mgr seems to mess-up L3 when running on data inputs. This problem is fixed!!! Still bad in the first build of p12.04.00 but will go into the last one. Thanks Jon Hays! If you run before this final build you need to turn off rdc_run_config_mgr (see p12.02.00 instruction below) or you should checkout run_config_mgr p12-br-02 and make you own local d0trigsim executable and run with rdc_run_config_mgr still in.
  2. L3 Tracking. See Daniel's tracking FAQ for all details. Quick summary:
    - Cookbook for running over MC:
      - Specify the correct geometry. To do this, you need to know the version which was used to create the MC file. This must be specified in the L3 Geometry Management tool. Your level3.sim file (which is generated from the trigger list) must be configured as such (this example uses the tag p10.06.01):
        GEO L3GeometryManagement (MCTag="p10.06.01")| CFTUnp L3CFTUnpack| SmtUnp L3TSmtUnpack|
      - Use the correct calibration. For MC files, only the SMT needs to be calibrated, and the correct file is automatically selected from the package l3fsmtunptool.
    - Cookbook for running over real data:
      - Specify the correct geometry. In the level3.sim file, the geometry and clustering tools should appear as below. This is the configuration for all triggers run online:
        GEO L3GeometryManagement( tooltype="utility", RunNo=-1, MCTag="xxx.xx.xx")| CFTUnp L3TCFTUnpack( tooltype="unpack", adcthreshold=20, maxfibers=8, realdata=TRUE)| SmtUnp L3TSmtUnpack( chanthreshold=.03, maxstrips=16, adcthreshold=10, clusterthreshold=.03, tooltype="unpack")|
        Note that "RunNo=-1" will give you the latest geometry available. If you instead insert a specific run number (like 123456), then it will use the geometry from the DB which was available for that run.
      - Specify the correct map and calibration information. For running on real data, one needs to have calibration/mapping information included in the L3 calibration file, called "l3calib.ev".
        The CFT and SMT information must be merged by hand into one file. This file can be obtained from cvs: gtr_l3/bin/l3calib.merged.cftstereo2.ev and must be copied into your "trigsim" directory if you are using runD0TrigSim, or into your local directory if you are using another executable:
        $ cp /d0dist/dist/packages/gtr_l3/devel/bin/l3calib.merged.cftstereo2.ev ./l3calib.ev
      Scheduled to be fixed in p13. Causes code to throw fatal exception and "skip" every event if you get it wrong.
  3. L3 Calorimeter Unpacking. Need to set dataVersion field to something sensible for your input file. Andre Turcot is working on a document for this. Here is what I know (very little)
```
You need to modify this definition:

  CAL_UNP L3TCalUnp(
          trgthrsh=0.,
          unpthrsh=0.,
          nbrrad=1,
          unpall=0,
          caltype="MC_PLATE",
          hotcell=1,
          hotthresh=1.,
          islthresh=.2,
          dataVersion="latest",
          tooltype="unpack")|
Some examples:

Data: dataVersion="latest"
MC, d0sim p10.06.00: dataVersion="p10"
MC, d0sim p10.15.00: dataVersion="latest"
MC, d0sim p11: dataVersion="latest"
```
  These issues should be resolved in p13.

Package changes in p12.04.00

build 03
--------
d0_analyze       v02-04-27  adds the -l3toollist to rund0analyze
                             and removes my typo in the rund0trigsim docs.
d0trigsim        p12-br-07  remove L3 unpackers from default toollist.txt
                             and change default triggerlist to L2Jet 5x5
l2gblem          p12-br-01
l2gblgeneric     p12-br-01
l2gblmuon        p12-br-01
l2slic_tables    p12-br-13
trigsim_analyze  p12-br-01  use L3 auto rcps for analyze (changes d0_analyze behaviour)
tsim_l1l2        p12-br-08  l2jets go to 5x5 in default list
--------------------------
l3fanalyze       p12-br-08  added ctest for L3XYVertexDebugInfoExaminer
                             updated L3MuoUnpackDebugInfoExaminer

build 02
--------
d0trigsim    p12-04-00a add run rcp for MC farms, fix typo in D0TrigSimWriteEvent.rcp (aka p12-br-06)
l1l2unpacker p12-04-00a fix byte-swapping in L1 muon
l2calworker  p12-04-00a fix bug in online-only cal workers
l2iogen      p12-04-00a fix bug found while introducing l2 tracking
l2slic       p12-04-00a fix bug causing online crashes
tsim_l1l2    p12-04-00a remove l2cttcft_analyze from default rcp
tsim_l1muo   p12-04-00a remove warning messages
------------------------
l3fchunk      p12-br-04 added insertClient and modified other insert 
                          methods in L3MonChunk
l3ftrack_cft  p12-br-02 fix bug for incorrect array indexing in L3TCFTTrack.
                          (Fixes itest crash in tsim_l3)
l3tCalUnpTool p12-br-03 2.5 sigma zero suppression threshold implemented
ScriptRunner  p12-br-06 corrected monitoring data for the case of several
                          clients defined

build 01
--------
d0trigsim    p12-03-00a
l1l2unpacker v00-03-19
l2calworker  v00-01-02
l2iogen      v04-05-00
l2slic       p12-br-14
tsim_l1l2    p12-03-00a
tsim_l1muo   v00-99-04
-----------------------
l3fchunk      p12-br-01
l3ftrack_cft  p12-br-01
l3tCalUnpTool p12-br-01
ScriptRunner  p12-br-04

P12.03.00 (09/07/2002, updated 09/30/2002)

Status Needs to be tested.
Tricks Here are some things you should know about for this version
- Disk space save Gordon Watts runs a version of TrigSim that saves on disk space. Here are his comments:
  I run trigsim in a slightly different mode that it was designed. I want to run trig sim, dump to root tuples, and if there are RECO chunks there, then I want to dump those also. And I'm running out of disk space so I don't want to write an intermediate file. I also wanted the latest version of the event_info package. Since trigsim and d0_analyze are simply a collection of framework packages, it is quite easy to make these changes. Everything I had to do (including the trigsim fixes [from p12.02.00]) is listed on [this] web page. Let me know if you find any errors.
- D0TrigSimWriteEvent.rcp has a bug - there is a quote missing in the string OutputFile. You need to
```
      addpkg d0trigsim p12-br-05
     
```
  to get a corrected version. The typo will be included in the next build of p12.04.00.
- toollist.txt is now parsed from the trigger list if one other than the default is provided. If you try to modify the parsed toollist and then runD0TrigSim, your version will get overwritten by a newly parsed toollist. A version of d0tools has been created with a command line option to allow you to specify which toollist to use.
```
      addpkg -h d0tools
      runD0TrigSim ... -l3toollist=mytoollist.txt ...
    
```
  NOTE: The documentation for d0tools has a typo. It calls this option -toollist. The correct option is -l3toollist. This option will eventually be in the "test" version of d0tools. It was introduced as tag v02-04-24.
Implimented Fixes The L3 ntuple content problem in p12.02.00 has been corrected. Otherwise, all the "Tricks" listed under p12.02.00 still have to be done.

Package changes in p12.03.00

build 02
--------
d0_analyze      p12-02-00-b3 (v00-02-00)
l2slic          p12-02-00b   (v00-03-22)
----------------------------------------
l3fanalyze         p12-03-00a (v00-02-07)
l3femtools         p12-br-02  (v00-01-69)
l3filters          p12-br-02  (v00-02-89)
l3fmuo_local       v00-03-12
l3monitor_utils    v01-00-05
l3tCalUnpTool      v00-04-47
l3xDAQSuperComBase v00-14-00
l3xetg             v01-00-06
l3xevb             v00-02-24
l3xsbc             v00-17-00
l3xtrace           v01-01-01
trigdb_scripts     p12-br-02  (v00-01-84)

build 01
--------
d0trigsim      p12-03-00a (v00-03-01)
l2calbase      p12-03-00a (v01-00-02)
l2calemworker  p12-03-00a (v01-00-02)
l2slic_tables  p12-03-00a (v00-01-07)
tsim_l1ft      p12-03-00a (v00-06-02)
tsim_l1l2      p12-03-00a (v00-04-32)
-------------------------------------
l3fCalMEt      p12-br-01  (v00-01-38)
l3fanalyze     p12-03-00a (v00-02-07)
l3node         p12-br-01  (v00-07-01)

P12.02.00 (08/13/2002, updated 09/04/02)

Status Has been tested on some cert-files and looks OK. Not yet approved by package authors/experts. Runs without modification or recompilation. I would use this version as default now. It has considerable improvements in L1/L2 cal running on data that are not present in any other version. It also is the basis for what will go online soon in L2/L3. If you want to certify, this is where you should do it (until p12.03.00).
Tricks Here are some things you should know about for this version
- new d0tools has been released using
```
      - -format=mc,data   to select right config for running on mc or
                        data inputs
      - automatically runs parser on level3.sim in order to create 
           toollist.txt for l3fanalyze
      - -forcercpoutfile is no longer needed
    
```
- Database, COOR, Lists
  The version of COORSIM in p12.02.00 is not caught up with the latest online lists. If you want to run with a recent list you should look at the d0trigsim trigger list page. There you will find some pre-made sim files for recent lists and instructions on how to make them yourself. You will find several versions of the *.sim files to try to take account of the hacks below. So, if you grab the right set of *.sim files you should be able to skip the stuff below about editing *.sim files.
  Alternatively, you can check out coor v00-56-00, compile it yourself and run it on your XML file. The next release or COORSIM will remedy version-compatibility issues like this.
- level2.sim Need to add the following lines to the top of online triggerlists
```
L2CAL ADMIN CALJET_WORKER {
IETA_MIN = 0,
IETA_MAX = 39,
JET_SIZE = 3,
KEEP_CORNER = 1,
KEEP_ROW = 1,
DCLEAR = 2
}

L2CAL ADMIN CALEM_WORKER {
IETA_MIN = 0,
IETA_MAX = 39,
BOX_SIZE = 3
}

L2GBL ADMIN GLOBALWORKER {
    USEL1BITS = 0
}
```
  I am not yet sure which one of these keeps things from crashing. I hope it is the L2CAL stuff.....
- L3 On data:
  rdc_run_config_mgr seems to mess-up L3 when running on data inputs. L3 has its own run_config_mgr interface and these two don't want to co-exist. However, L1 _must_ have rdc_run_config_mgr in order to unpack inputs. So, if you need to run L3 on data you can do
```
 
     addpkg  d0trigsim  
     edit d0trigsim/rcp/InitD0TrigSimInit_data.rcp to remove rdc_run_config_mgr
     runD0TrigSim -filelist=blah.txt -format=data -localrcp -l3only
   
```
  Don't know what the problem is....don't know how to fix it....
- L3 ntuple content:
  L3 needs a list of tools for which to create ntuple branches. It can get this out of the level3.sim file....the new d0tools version does this for you automatically. However, the default rcps in p12.02.00 don't make use of it.
```
        addpkg l3fanalyze p12-br-04
        addpkg d0trigsim p12-br-03
        runD0TrigSim -filelist=blah.txt -format=data,mc -localrcp -localfwkrcp
       
```
  will be fixed in p12.03.00.
- L3 unpacking/versioning: Some parts of L3 code need triggerlist configuration of geometry or unpacking. In practice this means that when you run on MC inputs you need a different level3.sim file than you do for data. You may even need a different level3.sim for each MC version. Here are the cases I know about and documentation for fixing things.
  1. L3 Tracking. See Daniel's tracking FAQ for all details. Quick summary:
    - Cookbook for running over MC:
      - Specify the correct geometry. To do this, you need to know the version which was used to create the MC file. This must be specified in the L3 Geometry Management tool. Your level3.sim file (which is generated from the trigger list) must be configured as such (this example uses the tag p10.06.01):
        GEO L3GeometryManagement (MCTag="p10.06.01")| CFTUnp L3CFTUnpack| SmtUnp L3TSmtUnpack|
      - Use the correct calibration. For MC files, only the SMT needs to be calibrated, and the correct file is automatically selected from the package l3fsmtunptool.
    - Cookbook for running over real data:
      - Specify the correct geometry. In the level3.sim file, the geometry and clustering tools should appear as below. This is the configuration for all triggers run online:
        GEO L3GeometryManagement( tooltype="utility", RunNo=-1, MCTag="xxx.xx.xx")| CFTUnp L3TCFTUnpack( tooltype="unpack", adcthreshold=20, maxfibers=8, realdata=TRUE)| SmtUnp L3TSmtUnpack( chanthreshold=.03, maxstrips=16, adcthreshold=10, clusterthreshold=.03, tooltype="unpack")|
        Note that "RunNo=-1" will give you the latest geometry available. If you instead insert a specific run number (like 123456), then it will use the geometry from the DB which was available for that run.
      - Specify the correct map and calibration information. For running on real data, one needs to have calibration/mapping information included in the L3 calibration file, called "l3calib.ev".
        The CFT and SMT information must be merged by hand into one file. This file can be obtained from cvs: gtr_l3/bin/l3calib.merged.cftstereo2.ev and must be copied into your "trigsim" directory if you are using runD0TrigSim, or into your local directory if you are using another executable:
        $ cp /d0dist/dist/packages/gtr_l3/devel/bin/l3calib.merged.cftstereo2.ev ./l3calib.ev
      Scheduled to be fixed in p13. Causes code to throw fatal exception and "skip" every event if you get it wrong.
  2. L3 Calorimeter Unpacking. Need to set dataVersion field to something sensible for your input file. Andre Turcot is working on a document for this. Here is what I know (very little)
```
You need to modify this definition:

  CAL_UNP L3TCalUnp(
          trgthrsh=0.,
          unpthrsh=0.,
          nbrrad=1,
          unpall=0,
          caltype="MC_PLATE",
          hotcell=1,
          hotthresh=1.,
          islthresh=.2,
          dataVersion="latest",
          tooltype="unpack")|
Some examples:

Data: dataVersion="latest"
MC, d0sim p10.06.00: dataVersion="p10"
MC, d0sim p10.15.00: dataVersion="latest"
MC, d0sim p11: dataVersion="latest"
```
  These issues should be resolved in p13.

Package changes in p12.02.00

 
build 3
-------

tsim_l1cal    p12-02-00a   workaround unpacker problem on data
l2gbljet      p12-02-00b   fix reference to M_PI on d0mino
l2slic        p12-02-00b   remove (C++ in C) comment warnings
d0trigsim     p12-02-00b   fix *_data rcps for run_config_mgr choice
                           add a new default triggerlist area
build 2 
-------
l2base         p12-02-00a  fix NULL definition on IRIX
l2stt_analyze  p12-02-00a  conform to interface change in l2stt_utils
                           (interface was changes because of duplicate
                           symbols problem)
l2calemworker  p12-02-00b  fix checking for "too many objects"
tsim_l1l2      p12-02-00b  fix missing OBJECTS (this is the version that
                           I meant to tag to begin with :(

build 1 - all tags are p12-02-00a
---------------------------------
l2io            fix bug in SimInputBuffer class
l2workerbase    Sets overflow bit in MBTChannel header and limits objects
                to max allowed
l2utils         Increase the object limits for the L2cal
l2monitor       minor update for online
tsim_l1l2       add tsim_l2cal_inputfix
l2gblworker     added mjt tool and filter
l2gbljet        fixed bug
l2slic          fixed minor bug in phi=0 region
l2slic_tables   eliminated gcc warnings
l2caljetworker  fix initialization and default values
l2calemworker   convert to global coordinates and fix bugs
l2calem_analyze bits for saturated EM and Tot towers
l2stt_util      resolve multiple symbol problem
tsim_l1ft       removed l2iogen from bin/LIBRARIES file
d0trigsim       add tsim_l2cal_inputfix

P12.01.00 (08/01/2002)

Status I hope this is the first version of p12 where evenrything at least runs out of the box.

Package changes in p12.01.00 (build 2)

l2utils        p12-br-02   fix bits 63 and 127
l2parser       p12-br-01   fix memory problem
l2slic         p12-br-10   online and gcc fixes
tsim_l2slic    p12-br-10   "
l2slic_tables  p12-br-10   "
l2mucworker    p12-br-10   "
l2mufworker    p12-br-10   "
l2mu_analyze   p12-br-10   "
l2mu_util      p12-br-10   "
tsim_l1ft      p12-br-02   running on data fixes
tsim_l1l2      p12-br-02   rcp changes

Package changes in p12.01.00 (build 1)

l2gbl_analyze  p12-br-01
l2monitor      p12-br-02
tsim_l1ft      p12-br-01
tsim_l1l2      p12-br-01
l2io           p12-br-01  (no siminputbuffer fix for Jodi)
l2message      p12-br-01
l2workerbase   p12-br-01
l2base         p12-br-01
l2utils        p12-br-01
l2calemworker  p12-br-01  Send out non-zero Pt