MTD software tasks

 The page collects the remaining tasks for the MTD related software.

  •  StMtdHitMaker (Rongrong Ma)
    • Run on muDst in afterburner mode. A new function setMtdArray() is added in StMuDst. (done)
    • Insert the map for TdigId <-> TrayId <-> TdigBoardId into offcial database, and modify the class to extract such maps from the database. (done)
    • Insert the trigger window cuts for MTD hits into the database, and modify the class to extract such calibration data from the database and use them in the production.
    • Fix a bug to obtain the MTD hits when running on muDst: collection -> muDst. (done)
    • When decoding the raw data, swap backleg 25 and 26. In the muDst mode, add a flag to determine if the swapping is needed. This flag is set to false by default, and it is the user's resposibility to enable the flag if needed. (done)
    • In order to be consistent with the indexing of backlegs and trays which both start from 1, the index for channels can be changed to begin from 1 instead of 0. This is also the convention for TOF.

  • StMtdMatchMaker (Bingchu Huang, Qian Yang, Shuai Yang)
    • Move functions of common interests to a geometry class (see StMtdUtil) (done)
    • Use the geometry file as in simulation (done)
    • Make sure it runs on all the productions in both bfc chain and offline muDst (done)
    • Optimize the matching algorithm
    • Modify the energy loss according to the comparison to GEANT. (done)
    • Simplify the QA tree and histograms which are probably not needed anymore

  • StMtdSimMaker (Yi Yang) 
    • Set up a working framework. Fine tuning can come later. (done)
    • Add option to include different GEANT configurations for different years, e.g. the map between GEANT backleg/tray and real life backleg/tray (done)
    • Possible correction on time-of-flight to account for the discrepancy between GEANT and matchmaker
    • Investigate the energy loss in GEANT (done)

  • StMtdCalibMaker(Xinjie Huang, Rongrong Ma)
    • Extract calibration data for T0 and tot, and insert them into data base. 
    • Option to run in afterbuner mode locally. Some local data base might be needed.(done)
    • Implement different correction modes: tray-based or strip-based correction factors depending on the available statistics.(done)
    • Add a new data member to pidTraits to store the time-of-flight obtained using track propagation. (done)
    • Year-dependence is foreseen.(done)

  • StMtdUtil (Rongrong Ma, Bingchu Huang)
    • Holding geometric constants
    • A geometry class containing the common function for matchmaker. For example, a function returning to the path-length, time-of-flight and matched MTD hit given a TPC track, etc
    • More utility functions (some already in StMtdQAMaker):
      • Return the global coordinates for a given MTD hits
      • Return the backleg, tray, strip for a given set of global coordinate
    • 3d magnetic field?

  • StMtdQAMaker(Rongrong Ma)
    • Currently in peer review
    • Add option to run different levels of QA for different purposes: e.g. a very low level QA of a few plots in official production, a mid-level QA in daily monitoring, and a high-level QA for deep investigation, etc

  • Event display

  • Example macro: provide an example macor for general users to use MTD information.