|Message: Re: OpBoundary process not called||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)|
> But, though photons > are clearly hitting the PMT, no hits are being registered. The main > reason, I think, is because the statement, > > fStep->GetPostStepPoint()->GetProcessDefinedStep() > ->GetProcessName(); > > gives "Transportation" even when the photon is getting reflected at a > boundary. Shouldn't it return "OpBoundary" in such a case?
No, the method called is 'GetProcessDefinedStep' which returns the pointer to the process that actually defined the simulation step which is always "Transportation" when the step ends at a volume boundary.
> In other > cases, like wavelength shifting, it correctly returns "OpWLS", and in > case of absorption, it correctly returns "OpAbsorption".
Yes, in that case those processes have limited (defined) the step. G4OpBoundaryProcess never limits the step. G4OpBoundaryProcess is a 'Forced' process that executes when a photon arrives at a volume boundary.
> I am using version 4.9.4.p02. My SteppingAction code is more or less the > same as the LXe code.
Well, you may want to follow that code even more closely. Obtain the pointer to the G4OpBoundaryProcess:
then use the pointer to get the 'boundaryStatus':
and then finally, if the metal surface of the PMT was hit and the photo efficiency resulted in 'Detection' you score a 'hit':