Re: [fluka-discuss]: FW: jtrack in endraw or comscw

From: paola sala <paola.sala_at_cern.ch>
Date: Thu, 16 Oct 2014 12:53:17 +0200

Dear Francesca,
Yes, indeed jtrack can assume some of the "generalized" values . I copy
here lines from
the release notes (fluka2006)

"When scoring some types of "pointwise" energy depositions,
   the JTRACK variable (common TRACKR) is set to a generalized particle
   value:
     JTRACK = 208 for non-transported nuclear recoils
     JTRACK = 308 for low energy neutron kerma
     JTRACK = 211 for EM particles produced below threshold
   Values 208 and 211 were already set in past versions, while the 308 flag
   is new. A new variable has been added in the TRACKR common to help
identify
   these energy depositions:
     J0TRCK
   it records the ID of the particle that originated the interaction.
   Warning: this variable is normally set to 0, its value has a
   meaning only when JTRACK = 208, 211, 308. "


For your easier reference, there is a short documentation in the
(TRACKR) include file:

* Jtrack = identity number of the particle: for recoils or *
* kerma deposition it can be outside the allowed *
* particle id range, assuming values like: *
* 208: "heavy" recoil *
* 211: EM below threshold *
* 308: low energy neutron kerma *
* in those cases the id of the particle originating *
* the interaction is saved inside J0trck (which othe-*
* rwise is zero) *
* J0trck = see above *


Hope this helps
Paola

On 10/16/2014 12:08 PM, Francesca Fiorini wrote:
> Dear Fluka experts,
>
> I'll try again with my question. 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 generalised "energy" particles (208=ENERGY, 211=EM-ENRGY...). In fact, if I ask ENDRAW to give me the mass for these ‘particles’ (AM(JTRACK)), 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 score Jtrack in COMSCW.
>
> If instead I detect the same quantities with BXDRAW the results seem reasonable: Jtrack does not assume those strange values and I have no problems with scoring mass, charge… but that is a boundary scoring and unfortunately I don’t need that.
>
> Many thanks 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 Thu Oct 16 2014 - 15:15:56 CEST

This archive was generated by hypermail 2.3.0 : Thu Oct 16 2014 - 15:15:57 CEST