[fluka-discuss]: RE: jtrack in endraw

From: Joachim Vollaire <joachim.vollaire_at_cern.ch>
Date: Mon, 20 Oct 2014 08:31:47 +0000

Dear Francesca,

Did you consider printing the ICODE instead in your output file to track back the physics process at the origin of the deposition. Depending of your application this might be the most straightforward way to proceed ?

* ENDRAW (energy deposition dumping)
     Argument list (all variables are input only):
          ICODE : type of event originating energy deposition
                  1x: call from Kaskad (hadrons and muons)
                     10: elastic interaction recoil
                     11: inelastic interaction recoil
                     12: stopping particle
                     13: pseudo-neutron deposition
                     14: particle escaping (energy deposited in blackhole)
                     15: time kill
                  2x: call from Emfsco (electrons, positrons and photons)
                     20: local energy deposition (i.e. photoelectric)
                     21 or 22: particle below threshold
                     23: particle escaping (energy deposited in blackhole)
                     24: time kill
                  3x: call from Kasneu (low-energy neutrons)
                     30: target recoil
                     31: neutron below threshold
                     32: neutron escaping (energy deposited in blackhole)
                     33: time kill
                  4x: call from Kashea (heavy ions)
                     40: ion escaping (energy deposited in blackhole)
                     41: time kill
                     42: delta ray stack overflow
                  5x: call from Kasoph (optical photons)
                     50: optical photon absorption
                     51: optical photon escaping (energy deposited in
                         blackhole)
                     52: time kill
          MREG : current region
          RULL : energy amount deposited
          XSCO, YSCO, ZSCO : point where energy is deposited


Cheers
Joachim


From: owner-fluka-discuss_at_mi.infn.it [mailto:owner-fluka-discuss_at_mi.infn.it] On Behalf Of Francesca Fiorini
Sent: 11 October 2014 10:16
To: fluka-discuss_at_fluka.org
Subject: [fluka-discuss]: jtrack in endraw

Dear Fluka expert,

I have a problem with JTRACK. I am using MGDRAW and in particular ENDRAW to score the deposited energy and other quantities in a region. Well it seems that I am detecting particles with JTRACKs equal to 208, 211 and 308, which I suppose are not real particles. In fact, if I ask ENDRAW to give me the mass for these ‘particles’, I receive the error: "Fortran runtime error: Index ‘208’ of dimension 1 of array ‘am’ above upper bound of 64."
Is this because I should not score jtrack or any quantity depending on it in ENDRAW? I have exactly the same problems if I try to score the same quantities using COMSCW.
So, if scoring Jtrack is not possible in ENDRAW, is there any other way to know which particle (mass, charge, kinetic energy) deposited the energy (rull) using MGDRAW?
(I know I can use USRBIN to score the deposited energy and AUXSCORE to separate the particles, but my final calculations are a bit more complex than that.)

If instead I detect the same quantities with BXDRAW the results seem reasonable: Jtrack does not assume those strange numbers and I have no problems with scoring mass, charge… but obviously that is a boundary scoring and unfortunately I don’t need that.

Many thank for your help
Francesca

Francesca Fiorini, PhD
CRUK and MRC Oxford Institute for Radiation Oncology
Old Road Campus Research Building
Off Roosevelt Drive
University of Oxford
Oxford, OX3 7DQ
UK


Received on Mon Oct 20 2014 - 12:11:45 CEST