Message: Re: problem with a modified hadrontherapy example Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

News Re: problem with a modified hadrontherapy example 

Keywords: SensitiveDetector, geometry update, hadrontherapy
Forum: Hits, Digitization and Pileup
Re: Question problem with a modified hadrontherapy example (Sara Vecchio)
Re: None Re: problem with a modified hadrontherapy example (Makoto Asai)
Re: Sad Re: problem with a modified hadrontherapy example (Sara Vecchio)
Re: None Re: problem with a modified hadrontherapy example (Makoto Asai)
Date: 14 Apr, 2006
From: Sara Vecchio <sara.vecchio@pi.infn.it>

The mass and readout geometry are correct. BuildROGeometry is invoked exactly as in the hadrontherapy example. This is confirmed by the fact that, if I comment the line ConstructSensitiveDetector() in the Construct() function of the physics list, and I call it only once, in the function UpdateGeometry() after Construction() (see my first post on the topic), no segmentation fault appear.

What I have not understood is just how to tell to the program that the readout geometry had been deeply changed, not the change in itself.

Anyway, this last trick is enough to solve the problem (though not in a very elegant way): I will not invoke ConstructSensitiveDetector() in the HadrontherapyDetectorConstruction::Construct(), but I will have to call HadrontherapyDetectorConstruction::UpdateGeometry() whatever change (even none) has been invoked in the macro.

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

 Add Message Add Message
to: "Re: problem with a modified hadrontherapy example"

 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 ]