I am dealing with thermal neutrons that hit a LiF target giving rise to tritons and alphas inside a gas volume. With the usrmed routine I chose to kill the entering alphas in the gas and keep only the tritons.
Then, in the mgdraw routine I implemented the following logic in order to record the tritons that enter inside the gas:
IF(JTRACK .EQ. -4) THEN
IF (NTRACK .GT. 0 .AND. MTRACK .GT. 0.) THEN
In the produced output, a very small fraction are double events and one triple:
Where 205066 is the primary index for a double event (2 produced tritons) and 588890 for a triple.
I would like to take into account in the boundary crossing estimation only single events (events with 1 produced triton) and discard double or triple events.
Is there any suggestion to be done in mgdraw using an appropriate variable and not post-processing afterwards?
Hi, what actually puzzles me is why we have 2 or even 3 entries for the same primary neutron…
Is it a bug or just the same particle that changes direction in the border?
How could it be corrected? The last column in the following entries is the emission angle in degrees with respect to beam direction.
Dear Andre, please find attached the running files… how we could tag a secondary triton to know how many times interacts? Because it is not natural to have two tritons produced from the same neutron in the reaction of thermal neutrons that hit LiF… the produced file: XYmgdraw_1001_fort.66 is the one that I highlighted with multiple boundary crossing entries in the previous messages…
Indeed, what you are obtaining is peculiar.
Using the LTRACK variable you can obtain the generation number of the current particle.
For all your tritons you are obtaining a value of LTRACK=2, which means that the doubles and triples events are secondaries from an interation of a primary thermal neutron…
We are looking into it, and as soon as we get a solution I will come back to you.
Thanks for your question, and I apologise for the delay in replying.
First of all I would like to point out that some of your cards and routines are incompatible with the current FLUKA.CERN version:
LOW-PWXS: Here you are defining the WHAT(1) as 1, which applies the pointwise treatment for the metastable material. I would recommend you to leave all the whats empty to enable the pointwise for all the materials.
LOW-MATS: Considering that you want to use the point-wise treatment you do not need to use these cards. These ones are intended for the group-wise treatment.
Usrmed routine: The format of your includes are not compatible anymore with the current FLUKA.CERN version.
Now, after these comments, we can solve your issue.
The problem was simply that the tritons were returning from the REG-5 to the REG-3 and crossing again the boundary REG-3 → REG-5.
You can observe this by yourself flagging the particles that a crossing the surface and checking the flag if they cross again. Something like this:
IF (ISPUSR(1).eq.724) THEN
WRITE(66,*) “It is me again!”, NCASE
ISPUSR(1) = 724
And of course, you see this just a few time because these are super rare cases.