GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » R3BRoot » Simulation Issues » Detector ID
Re: Detector ID [message #21189 is a reply to message #21158] Mon, 12 June 2017 08:39 Go to previous messageGo to previous message
Dmytro Kresan is currently offline  Dmytro Kresan
Messages: 166
Registered: June 2004
first-grade participant
From: *
I was not able to find any match with "TrackPoint" branch in R3BRoot. Did you mean "TraPoint"? In this case, those are the hits from Tracker. Matching of data to a detector is done using the name: R3BXBall (detector) - R3BXBallPoint (hits of particles), the name of the branch has to be changed to "XBallPoint" (XBCrystalPoint is currently used).

There is enum type in r3bdata/R3BDetectorList.h, but it is used for counting how many points in each detector an MC track has, and not for storing together with simulated hits.

fDetectorID is meant to be sub-system internal, and it looks like, in case of XBall, it is the Volume ID. This number changes, depending on the order you add your detectors to the simulation run in the macro. It is better to use R3BXBallPoint.fCrystalType (1,2,3,4) and .fCrystalNb (running index, I suppose).

Best regards,
Read Message
Read Message
Read Message
Read Message
Previous Topic: TrackID changes
Next Topic: GLAD positioning
Goto Forum:

Current Time: Tue Jun 25 21:43:22 CEST 2024

Total time taken to generate the page: 0.01103 seconds