|Message: G4VPhysicalVolume->GetTranslation() from threads||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 have one question regarding the MT implementation of the geometry.
In my application, I run a simple web server in a separate thread (not master, not worker) that allows me to remotely inspect and control some aspects of the running application. However, when I try to access (some) geometry information (like PV translations, LV materials etc.), I run into an unpleasant surprise in the form of application crash. This seems to be the result of the "subinstances" being used to hold this information (these subinstances, as I understand it, are relevant only for threads initialized by the Geant4 MT mechanism).
So the question is - can I somehow get to full geometry data from an independent thread? Or is there any other suggested approach? I don't have the necessary deep understanding of Geant4 MT :-(
Thanks for any ideas, Jan
P.S. Of course, general access to geometry may be dangerous, but at least in Idle state, I don't see any reason why the information should not be readable (if not writable).
|Inline Depth:||Outline Depth:||Add message:|