Message: GeometryUpdate() vs. SensitiveDetector Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question GeometryUpdate() vs. SensitiveDetector 

Forum: Event and Track Management
Date: 17 Nov, 2010
From: Maciej Sznajder <Maciej Sznajder>


I have got strange issue with my sensitive detector. When I am not updating the geometry (f.e. updating the dimmentions of the detector), my program works just fine. I can make as many beamOns as I want. Geant outputs me my data and every think works fine. The detector is ALL time sensitive.

BUT when I call BeamOn then UpdateGeometry from "Idle" and once more beamOn I have got "segmentation fault" issue. The issue disappeared when I comment the "trackerCollection" line i.e. I switch off the "sensitive" functionality:

KobeHit* newHit = new KobeHit(pos, edep); trackerCollection->Insert(newHit);

The source code is located at:

Right now I just thinking. Maybe I am not allowed to make my detector sensitive when I'm changing "something" by calling the UpdateGeometry function?

Best regards, and Thank You for any tip. Maciej Sznajder

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

1 None: Re: GeometryUpdate() vs. SensitiveDetector   (Michael H. Kelsey - 17 Nov, 2010)
 Add Message Add Message
to: "GeometryUpdate() vs. SensitiveDetector"

 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 ]