|Message: Modifying the geometry via messenger class||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)|
My problem is the following:
The detector I have defined basically consists of a lot of PMTs placed in some grid within an optical medium while the basic parameters of the grid (size of grid and spacing of PMTs) are stored as private members of the detector construction class an accessible via set/get methods. I also have a detector messenger class to change those parameters interactively.
This complete thing SEEMS to work as reasonable things happen on the first glance, i.e. I get fewer hits when I increase the spacing between the PMTs and so on.
BUT: I also write the hit information to a file where among other things the positions of the PMTs that were hit are stored, and there it looks as the detector geometry wouldn't have been changed at all. The PMT positions are always the same as in the default detector setting, even if I made all spacings way larger before!
Also, when I use some visualization the viewer doesn't change the displayed geometry either.
And no, I didn't forget to type /run/geometryModified or /vis/viewer/refresh each time I changed something. By the way, this is also a question I have: What does exactly happen after /run/geometryModified and what doesn't?
Pooh, that was a long thing but now I'm finished. I hope someone out there can help me in some way...
Thank you and merry Christmas! Lukas
|Inline Depth:||Outline Depth:||Add message:|