|Message: Re: Smart voxelization for parameterised volume||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 for your reply! Let me clarify.
> if with your parameterisation you generate a sphere randomly, > then you cannot use the voxelisation, as the voxels structure gets > generated statically at the beginning and does not change during the > run.
At the start of my program, I read in a text file that contains some randomly generated coordinates. The coordinates are stored in a container class that returns a coordinate as a function of the event number. An instance of this class is then copied to wherever it is needed (e.g. PrimaryGeneratorAction and the parameterised volume). The "random coordinate" is thus uniquely defined by the event number and does not change within an event. It is not the case that I generate a new coordinate for each call to ComputeTransformation.
> Your parameterisation must be 'predictable', such that dimensions > and positions can be reproduced for the same run.
The dimensions for a given copyNo do not change. The position for a given copyNo changes between events, but not within an event. Does this fulfill the predictability criterion?
> Note also that parameterisations can only apply to a single volume > (associated to a solid) and you cannot have two parameterisations > daughters of the same mother.
The mother volume has only one parameterised daughter. It is a G4Sphere whose dimensions depend on the copyNo. For the sake of example, let's say copyNo 0 has rMin = 0 and rMax = 5mm while copyNo 1 has rMin = 5mm and rMax = 10mm. I plan to simulate multiple balls in the future (each one would add an additional two copies to the parameterisation), but the problem is present with just one.
|Inline Depth:||Outline Depth:||Add message:|