GSI Forum: Simulation Issues » TrackID changes

Home » R3BRoot » Simulation Issues » TrackID changes (TrackID change through a trajectory)

Show: Today's Messages :: Polls :: Message Navigator

TrackID changes [message #20789]

Wed, 29 March 2017 08:16

lanyizsombor
Messages: 6
Registered: March 2017
Location: Budapest, Hungary

occasional visitor

From: *catv.broadband.hu

Hi all,

I would have a short question. I would like to track every neutron's way in a simulation to test my own code for neutron cross-talk and for this, I thought that I get the interaction coordinates with stepping through the points using GetTrackID(), but I'm not sure whether it works well. So, the main question is that the TrackID changes only if a neutron stops (energy below threshold) and give it's energy for a proton for example; or it could change otherwise too? Hope I asked the question more or less clear.

Best regards,
Zsombor Lányi

Report message to a moderator

Re: TrackID changes [message #20800 is a reply to message #20789]

Wed, 05 April 2017 09:34

Jan Mayer
Messages: 20
Registered: August 2015

occasional visitor

From: *dyn.hrz.tu-darmstadt.de

Hi Zsombor,

the TrackIDs can be a bit fiddly, especially while accessing them during the simulation, but should work in principle. The track ID can also "change" on any interaction - that means you technically have a new track. You can have a look at that afterwards by using the MotherID. This is -1 for primary particles, so if you shoot in two Neutron you should have two tracks with motherID -1 and pid 2112 (see http://pdg.lbl.gov/2010/reviews/rpp2010-rev-monte-carlo-numbering.pdf).
run->SetStoreTraj(kTRUE); probably needs to be set for this at well (4th parameter in r3ball.C).

Best,
Jan

Attachment: trackids.png
(Size: 21.78KB, Downloaded 254 times)

Report message to a moderator

Previous Topic:	GLAD magnetic field
Next Topic:	Detector ID

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Apr 25 23:33:04 CEST 2024

Total time taken to generate the page: 0.00731 seconds