GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » R3BRoot » Simulation Issues » Question on R3BNeutronTracker2D (Question on R3BNeutronTracker2D)
Re: Question on R3BNeutronTracker2D [message #19363 is a reply to message #19362] Thu, 07 July 2016 17:00 Go to previous messageGo to previous message
Dmytro Kresan is currently offline  Dmytro Kresan
Messages: 166
Registered: June 2004
first-grade participant
From: *dyn.telefonica.de
Hi Christiaan,

How often does this happen, percentage of events?

Determining nNeut is just the first step in the reconstruction. nNeut is based on calorimetric and multiplicity properties of an event. Afterwards you need to find your candidates in the hit pattern. Imagine you did 3n -> 4n misidentification, then most probably program will find only 3 best candidates, so @size < nNeut. And this can happen in 20 - 30% of events - depending on input and cuts.

How did you calculate the energy/clusters cuts for your simulation? You need to recalculate them for every different input, do not apply "standard" values.

In addition, beta cut is applied, to select neutrons with velocity close to beam. Due to finite resolution, this condition could also cut out good candidates.

You can investigate 2 things:

1) Determine your multi-neutron identification matrices, like was done for 132Sn input. In your case, you can define primary neutron by cutting on time and position of the MCTrack vertex - close to (0, 0,0,0). Then you will know your proper 2D cuts, efficiency and misidentification.

2) To study the reaction input - plot the velocity distribution of "primary" neutrons, and cut values on top of it. This will help to adjust the beta-cut for this physics case.

Best regards,
Dima
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Tracking energy cut
Next Topic: Tracks on Event Display
Goto Forum:
  


Current Time: Thu Feb 02 09:33:29 CET 2023

Total time taken to generate the page: 0.01028 seconds