|Message: Re: Reduce Processing 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)|
Can you establish how long your simulation takes for two (2) events without trajectories; e.g. without:
then with the above but without:
and finally with:
> Last time /vis/scene/endOfEventAction was setted as accumulate. > Now I changed it to refresh (or just commented cause refresh is default setting.) > Now it takes ~3 minutes for each events uniformly.
I don't understand why the type of drawing trajectories should have any bearing on the length it takes to simulate photon tracks in the event. Sure, with storing and filling large number of trajectories so they can be drawn will slow the simulation somewhat, but not whether the scene is refreshed or not at the end of event....
> (Before it was getting slower and slower event by event.)
This sure is strange. I am not an expert with the visualization but even with 'accumulate' the trajectories of one event should be deleted after they have been drawn and before the next event starts. You must be doing something more with the trajectories - perhaps they don't get deleted(?)
|Inline Depth:||Outline Depth:||Add message:|