Message: Re: Ntuple fills per-event instead of per-hit Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: Ntuple fills per-event instead of per-hit 

Forum: Analysis
Re: Question Ntuple fills per-event instead of per-hit (Matt Taggart)
Date: 09 Apr, 2013
From: Matt Taggart <Matt Taggart>

Thank you both for your swift replies.

The simulation generates a fission event in the SponFissIsotope class which creates a range of neutron and gamma primaries according to standard multiplicity distributions. I'm presently reading out the number of particles, and then for each primary their initial energies and direction of emission.

I also wish to include the energy deposited by a particle in my sensitive detector, as well as the time since the fission event of that particle. At present this information is recorded by the EventAction in EndOfEventAction(). Regardless of the event multiplicity (0-20 for each n and g) it only ever records a single particle (I varied the size of my detector to maximise solid angle coverage), I assume that this is the last primary dealt with, so if that happens to not hit my detector it obviously returns a 0 for energy deposition.

If I can fill the nTuple through PreUserTrackingAction() that would seem to avoid the once-per-event issue, but then the question becomes whether you can call the hitCollection at that stage too?

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: Re: Ntuple fills per-event instead of per-hit   (Ivana Hrivnacova - 11 Apr, 2013)
 Add Message Add Message
to: "Re: Ntuple fills per-event instead of per-hit"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews

[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]