|Message: Re: 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)|
Hi Anders, concerning moving geometries, if the 'moving' part is implemented via parameterised volumes (and assuming the parameterisation is correctly implemented, i.e. it is thread_safe), this will work in MT mode, as the parameterised part gets automatically cloned in each thread. If the moving part is implemented via normal placements, this depends on the number of events you want to execute before a change to the geometry applies (i.e. duration of a run); during the run the execution can obviously happen in parallel. Cheers, Gabriele -------------- On Tue, 15 Sep 2015 11:39:38 GMT, herr_apa wrote: > I have now implemented my geometry and everything seems to work. At this > point I just want to confirm that I haven't done anything crazy. > > For my first question (about voxelization), I think I've figured out the > answer. The voxelization isn't flat, but hierarchial. While a volume may > move outside of a particular sub-voxel, it will never leave the mother > voxel because motherLogical->SetSmartless(number_of_daughters_or_larger) > ensures that the mother voxel contains every single daughter. > > For my second question, I would still appreciate a comment from the > experts: How are moving volumes handled in multithreaded mode? If a > particular thread moves a volume, won't that mess with the other threads > since the geometry is thread-shared? >