|Message: Re: problems with optical surfaces||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'll deal first with your second problem. A sensitive detector registers hits only for steps taken inside it. Therefore, if a photon is absorbed as it hits your light detector it'll never actually step inside it. Hence, no hits in the usual G4 sense. Please, see example/extended/optical/LXe to learn how to tally optical photons that hit a photon sensitive surface (LXeSteppingAction.cc). You basically have to trigger the (hit) counting in SteppingAction when the G4OpBoundaryProcess returns 'Detection'. Reflected photons do do a reallocation step inside your light detector and so you get the usual G4VHit. In summary, the sensitive volume concept of Geant4 is not suitable for use with optical photons.
At present, it is not possible to specify different optical properties for different sides of a volume's surface except by the 'trick' you have arrived at; a geometry volume construct redefinition whereby the sides are adjacent to different physical volumes.
It took me some time but I found your bug why the reflectivity is ignored for your housing wall:
myST2->AddProperty("REFLECTIVTY", Ephoton, ReflectivityRHS, num);
it should read "REFLECTIVITY"! (There is nothing I could do programming wise to prevent you from making this spelling mistake because the MaterialPropertiesTable is designed so the user can add any named property to the table he wishes to) The G4OpBoundaryProcess looks for the correctly named property "REFLECTIVITY" and if it is not found, the default is 1.
|Inline Depth:||Outline Depth:||Add message:|