R3BNeutronTracker2D crashes [message #19168] |
Wed, 23 March 2016 17:28 |
C. A. Douma
Messages: 88 Registered: September 2015 Location: Groningen
|
continuous participant |
From: *kvi-cart.rug.nl
|
|
Dear Mr. Kresan,
When I use the new Neuland-class for a NeuLAND simulation, the R3BNeutronTracker2D gives a segmentation violation.
Could this be because it searches for "LandPoint" and "LandFirstHits" but not for "NeulandPoints" and "NeulandPrimaryNeutronInteractionPoints"?
Christiaan.
|
|
|
|
|
Re: R3BNeutronTracker2D crashes [message #19177 is a reply to message #19173] |
Wed, 30 March 2016 09:14 |
Dmytro Kresan
Messages: 166 Registered: June 2004
|
first-grade participant |
From: *gsi.de
|
|
Hi Christiaan,
What you suggest, with manually adding 10 energy cuts in order to find 10 candidates for neutron interactions, does not really make sense. In the reconstruction, you will need events which fall into your 9-th or 10-th cut, so you will need 9 or 10 incident neutrons. This is not really what you want to simulate.
There is a feature in the NeutronTracker2D, you can call the following method from the r3blandreco.C macro (comment out ReadCalibrFile(...) call):
tracker->Disable2DEventCut(10);
Which will force the algorithm to produce 10 candidates. Afterwards you can apply your VETO criterium.
Best regards,
Dima
|
|
|