|Message: Re: Min step size for optical photons?||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)|
thanks a lot for explanation. Now I'm sure that the biasing of my simulation is what I need, rather than a change of step length.
On Tue, 07 May 2013 23:41:19 GMT, Gumplinger Peter wrote:
> Hello Pawel, > > > I'm wondering whether there is a way to set the minimum step size > > for produced photons to make tracking less accurate, but also less CPU > > consuming? I've searched forum, but found only examples of setting > > maximum step size, which is not the case. If such a possibility exists, > > I'd be grateful for every hint. > > The steps optical photons take during the simulation are already the > minimum step size they can take. Optical photon steps are only limited > by geometry and discrete processes. The geometry has to be interrogated > to find the next volume boundary - I am not aware of any way to make > this 'less accurate' but faster. > > If you find the CPU consum prohibitive you may bias the number of > optical photons you track. For example, you can remove every other > photon in your UserStackingAction. This reduces the statistical accuracy > but you may still get a result that is statistical significant for your > setup. > > Best regards, Peter >