Message: Re: Smart voxelization for parameterised volume Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: Smart voxelization for parameterised volume 

Forum: Geometry
Re: None Smart voxelization for parameterised volume
Re: More Re: Smart voxelization for parameterised volume (Gabriele Cosmo)
Re: None Re: Smart voxelization for parameterised volume
Re: None Re: Smart voxelization for parameterised volume (John Apostolakis)
Date: 21 Jan, 2016
From: <herr_apa>

Hi,

Turns out there are two ways to get proper tracking with moving volumes. As John pointed out, the voxel data structure is built at initialization time and does not change during the run. If a volume leaves its original voxel, the tracker loses sight of it. Furthermore, it is not possible to turn off voxelization for parameterised volumes. The two options are therefore:

1) Simulate only one event per run. Provided that all volumes are stationary during that event, the voxel structure that was built at initialization time will remain valid. A new structure is then built for the next run.

2) Call SetSmartless(0) for the mother volume of the parameterised volume. This forces the tracker to use a single, big voxel that contains all the volumes. Since there is only one voxel, no translation or rotation can cause a volume to change voxels.

When using 1), a lot of time is spent building the voxel structure, but the tracking is fast. For 2), little time is spent building the voxel structure but the tracking is slow. For my application, 2) turned out to be faster overall. It's also worth pointing out that 1) does not lend itself to multithreading.

In my original question, I asked why SetSmartless(nDaughters) seemed to work for a ball but not for a ball with a surface layer. The reason was that my test case included only a single ball. In the "core only" case, there was only one volume, so only a single voxel was created even though I set Smartless > 0. In the "core + surface" case, the parameterisation contained two volumes, and setting Smartless > 0 resulted in more than one voxel being created. The tracking then failed because some moving volume changed voxels.

// Anders

 Add Message Add Message
to: "Re: Smart voxelization for parameterised volume"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]