|Message: Re: problem with a modified hadrontherapy example||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
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:||Outline Depth:||Add message:|