|Message: Re: msc model for positrons||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)|
I run a geometry test and found an overlapping in 2 logical mother volumes (see the figure attached, I found difficoult to explain the geometry otherwise).
This was because the 2 sets of daughter volumes had different materials, thicknesses etc., and I did not want to parameterize everything.
Now I have revised the code, and both the sets are parameterized inside the same mother volume (geometry test does not detect any overlap ofc). A check on the daughter geometry seems fine in terms of positioning, materials and sizes (see attached files).
Attachment: http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2015/10/06/10.23-88003-now1.png http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2015/10/06/10.23-43477-now1-zoom.png http://hypernews.slac.stanford.edu/HyperNews/geant4/get/AUX/2015/10/06/10.23-54363-now2.png
However, whenever a particle enters these parameterized volumes the simulation crashes with a segmentation fault. This is the output of tracking/verbose 6 (you can find attached the complete output for this last track):
#Step# X(mm) Y(mm) Z(mm) KinE(MeV) dE(MeV) StepLeng TrackLeng NextVolume ProcName 14 1.34 -9.4 328 0.57 0 43.8 536 Filter Transportation
>>DefinePhysicalStepLength (List of proposed StepLengths): ++ProposedStep(PostStep ) = 1.797693134862316e+308 : ProcName = photonNuclear (No ForceCondition) Segmentation fault (core dump created)
I tried modifying/removing the step limiter, the sizes and the material for these volumes, but nothing changed. I really have no clue of what is going on or how to solve this.
|Inline Depth:||Outline Depth:||Add message:|