|Message: Changing geometry between runs with GDML & runtime primitive scorers (the latter is not working)||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'm using primitive scoring and GDML-based geometry definition for my Geant4 application in G4v10.00.p03 on Linux. I am attempting to load new geometry between runs, as well as re-set the primitive scorer. However, I am getting segmentation faults and it appears that the primitive scoring is not happy being reset. Can anyone point me in the right direction?
My approach for the primitive scoring is taken directly from Example RE03, where I'm implementing the G4ScoringManager.hh and using run-time definition of the scorers through UI command scripts. This is paired with a GDML load approach adapted from the persistency example G02.
I just finished hammering out the GDML portion so that I could successfully load different geometries between runs without restarting Geant4. I know that this portion of the code works because I've been using it and testing it with the reloading. This thread summarizes that accomplishment:
For the primitive scorer, I can use the UI-based primitive scorer on my initial geometries, but when I go to initialize the second geometry it will crash. This is my basic UI call order:
# First Run #######################
# Second Run ######################
/run/reinitializeGeometry 1 1
/run/initialize <--Seg Fault occurs here
My understanding of the /run/reinitializeGeometry command is that the two boolean flags at the end when set to true should be purging the parallel world where the primitive scorers are defined. Is that correct? Are there any other "clean" or "reinitialize" commands that I should be using?
Thanks for any help.
|Inline Depth:||Outline Depth:||Add message:|