|Message: Re: Optical photon transport and cpu time||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 didn't see anything wrong with your code; nothing that would cause an inflation of CPU time. I don't know how much energy you hope to detect in your scintillator but from:
I see that you request 7000 scintillation photons for every MeV dumped into your scintillator. That's a lot of tracks to simulate. You may find that you will get a statistical representative sample by biasing your yield (down) if you just simulated a fraction of them (you'll weight your result accordingly).
Now, there is one more, probably significant, CPU gain you can achieve by defining your interface between the scintillator and your ground reflector as:
This option allows you to define your thin air gap not as a distinct volume in the G4 geometry, but as something 'known' to the G4OpBoundaryProcess internally. Please, see the documentation for details (Example 5.8). It looks to me that your surface specifications are perfectly suited for this build in speed-up:
OpAirHousingSurface->SetFinish(ground); OpAirHousingSurface ->SetPolish(0.);
This is the same as Lambertian reflection, which is what the back reflector is simulated as in 'groundbackpainted'.