Message: index of HitMap in primitive scorer different from the copyNumber of the touchable Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question index of HitMap in primitive scorer different from the copyNumber of the touchable 

Forum: Biasing and Scoring
Date: 14 Oct, 2015
From: Sabrina <Sabrina>

Hello,

I'm work with the Dicom example and I'm observing that the index of the hitMap I get when I use a primitive scorer (such G4SDDoseDeposit3D or G4SDEnergyDeposit) is different from the touchable copyNumber I get in the steppingAction. I observed a difference of 10 in the number.

Here is a print of the energy deposit for one voxel:

*Touchable copy number and energy deposit printed from the steppingAction: 10272 0.529704 MeV

*Voxel index and energy deposit from the primitive scorer:
    10282     0.529704 MeV

For the same energy deposit the voxel number is 10272 in the first case and 10282 in the second case. Checking the voxel number with the position of the voxel, make me thing that the correct number is the one given by the touchable copy number in the stepping action.

Any idea why the voxel index given by the primitive scorer is different?

thanks in advance.

 Add Message Add Message
to: "index of HitMap in primitive scorer different from the copyNumber of the touchable"

 Subscribe Subscribe

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