|Message: Moving Volumes Between Events||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 have a large and complicated geometry described by > 10^5 volumes. I want to simulate the dose absorbed by a set of dust particles moving through the geometry. Everything in the geometry is stationary except for the dust particles, whose position depends on the event number. From what I understand, the proper approach is to describe the particles with a parametrized volume and let ComputeTransformation depend on the event number as explained e.g. on slides 17-19 here:
I have two questions. Firstly, the slides say that the moving objects should not be allowed to leave their original voxel. Therefore, voxelization should be turned off for the mother volume of the moving objects using "motherLogical->SetSmartless(number_of_daughters_or_larger);" This is confusing, and I'm sure there's something I've misunderstood. Wouldn't calling SetSmartless with a large number (10^5 in my case) lead to a huge number of voxels, practically guaranteeing that the moving volumes will leave their original voxel? Shouldn't I call SetSmartless(0) to turn off voxelization? (Note that I'm very happy if I don't have to call SetSmartless(0) because that causes the simulation to slow to a crawl!)
My second question concerns multithreading. It is my understanding that there is only one instance of the geometry, and it is shared between all threads. If I make the geometry depend on the event number as described above, won't this lead to problems with different threads trying to alter the geometry at the same time? Are parametrized volumes somehow thread-local?
Thanks in advance!
|Inline Depth:||Outline Depth:||Add message:|