Message: Readout geometry and sensitive detector process hits Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Readout geometry and sensitive detector process hits 

Forum: Event and Track Management
Date: 05 Jul, 2014
From: Balint Radics <Balint Radics>

Hi,

I have a sensitive detector the MySensitiveDetector::ProcessHits(...) function of which never gets called, or the TouchableHistory or G4Track objects are null when it is called..

Which is strange because when I visualize the detector and tracks I can see that many track goes through my sensitive volume. It is registered in SDManager in my detector constructor. Also with /tracking/verbose 1 I can see that the track actually step through the volume. I even set a step limiter and it works too.

Can it be that there is some problem with volume overlaps?

I also have a corresponding Readout geometry class. It seems that whenever I register the dummy sensitive volume in the Reaadout geometry class to SDManager the original sensitive detector's MySensitiveDetector::ProcessHits(...) is not even called at all. While if I do not register the Readout geometry then MySensitiveDetector::ProcessHits(...) gets called but TouchableHistory or G4Track objects are null.

Also, Geant4 still runs, but there is no error in the output that would suggest that something is wrong with my sensitive detector or readout geometry.

How can I debug this problem?

Thanks, Balint

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

1 None: Re: Readout geometry and sensitive detector process hits   (Balint Radics - 05 Jul, 2014)
 Add Message Add Message
to: "Readout geometry and sensitive detector process hits"

 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 ]