Re: [fluka-discuss]: Dumping information with mgdraw

From: Stefan E. Mueller <stefan.mueller_at_hzdr.de>
Date: Wed, 20 Jan 2021 15:08:36 +0100 (CET)

Dear Giovanni -

I am not sure if I fully understand your problem. The screenshot you
attached shows the output of a RootTTree, which gives different
information to what your "mymgdraw.f"-file gives in output.

If your question is why in your RootTTree the variable "track_id" is not
consecutive within an event then it would be good to understand how you
define "track_id" in your application, the attached mymgdraw.f-file
doesn't contain this information.

Another thing I noted is that when in line 93 of mymgdraw.f, you define
DE = DTRACK (NTRACK), I'd think DE will contain always the energy deposit
of the last track segment, regardless of the value of the iterator
variable "I" - is this really the intention?

         Stefan

--
Stefan E. Mueller
Department of Information Services and Computing - Computational Science
and Institute of Radiation Physics
Helmholtz-Zentrum Dresden-Rossendorf
Tel: +49 (0351) 260 3847
Stefan.Mueller_at_hzdr.de
http://www.hzdr.de
Vorstand: Prof. Dr. Sebastian M. Schmidt, Dr. Diana Stiller
Vereinsregister: VR 1693 beim Amtsgericht Dresden
On Wed, 20 Jan 2021, Giovanni Costantini wrote:
> Dear Fluka experts,I have a question for you about dumping event particle
> information with mgdraw. I built my subroutine in order to know all energies
> deposition  by every particle in the detector. I was wondering how the
> dumping on a file works. More precisely, which is the order in which the
> particle's information is dumped?
> 
> After I run simulations, I pass data to a colleague which applies a
> clustering algorithm, to reconstruct the clusters. 
> She noticed that sometime happen the following issue: the dumping is
> switching between two particles close one to each other instead of dumping
> every step of one particle and then the other one (I put a screenshot of an
> example, look at the ev (second column) 1, a negative pion and an electron
> (pdg_code in the third column) are dumped in such a way. I also put an input
> file and the mgdraw.f  I am using).
> 
> Is it related to the different tracks they belong to? Thus it happens only
> with delta rays for example? 
> 
> The problem that I have is not strictly speaking with Fluka, it's just that
> the algorithm she is using works in a precise way and I should try to have
> the output of my simulations more similar as possible to the output
> requested, but I was hoping you can give me some hint about this issue.
> 
> Thank you in advance for your help,
> 
> Giovanni Costantini
> 
> 
> Informativa sulla Privacy: http://www.unibs.it/node/8155
> 
>

__________________________________________________________________________
You can manage unsubscription from this mailing list at https://www.fluka.org/fluka.php?id=acc_info

Received on Wed Jan 20 2021 - 17:13:46 CET