Home » Groups » STAR Protected

BTof issue in Run12 Cu+Au production

Updated on Mon, 2021-11-29 12:06. Originally created by marr on 2020-12-09 21:18.
This page documents issues in the BTof matching seen in several data sets

Year System Issues found Library used Detailed study Comments
2012 Cu+Au @ 200 GeV
  • Half of BTOF (eta<0) is not seen during track matching
  • This shows up in Daq->MuDst production or running afterburner on MuDst 
  • Hits in the entire acceptance are present in the BTOF hit collection
 SL19d
SL19e		 SLIDES
(Ziyang)		  
2012 p+p @ 500 GeV
  • Half of BTOF (eta<0) is not seen during track matching when running BTOF matching afterburner using SL20c
  • This issue is not present in the original production using SL13b
 SL20c SLIDES
(Leszek)		  
2009 p+p @ 500 GeV
  • For the data produced with SL18h, BTOF matching efficiency is decreased, compared to SL17h production, because of no matching to some trays. 
  • Running afterburner with SL20a and SL21a has the same issue as SL18h
  • Even full reconstruction with BFC and same chain options with SL20a has the issue
  • BTOF trays #97-120 are initialized, but show no matched tracks
  • BTOF tray #93 initialized, while it wasn't physically installed (mix-up of trays in geometry)
 SL18h
SL20a
SL21a
potentially all after SL18c		 SLIDES
Slides_3.2021
(Leszek)		  


In SL18c and beyond, the StBTofMatchMaker and StBTofGeometry got updated to use gGeoManager-based geometry. This seems to introduce some issues when using the new code on the old geometry. 


Run09 p+p @ 500 GeV:

With bug - missing trays:




Bug during looping over valid trays and wrong logic for check of GMT trays
Fixed here: https://www.star.bnl.gov/cgi-bin/protected/viewvc.cgi/cvsroot/StRoot/StBTofUtil/StBTofGeometry.cxx?r1=1.32&r2=1.33

After fix - OK!
Groups: