You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am writing hoping that you can help me understand the role of group_volume in DigitizerAdderActor.
I am trying to create a simulation for a two-detector Compton camera, where each detector is pixellated. I want to use DigitizerAdderActor in combination with the DigitizerHitsCollectionActor, in order to collect all singles event across different detector pixels. Pixellated detectors are modeled with gate.geometry.utility.get_grid_repetition. The question is, when the DigitizerAdderActor's group_volume attribute is the mother volume containing these two pixellated detectors, I get singles with positions that are energy weighted across the entire mother volume, not within each individual pixel. However, when the group_volume is one of the two detectors' name, it works as intended, meaning that I get energy weighted singles from both detector pixels. Below is the minimum reproducible code.
Basically, the above code yields singles that are all aggregated, such that singles_data.groupby("EventID").nunique().max() value just gives 1. However, when I change from cc_lower.name to lower_scatterer.name, I get singles in each pixels of not only the lower_scatterer, but lower_absorber as well. What is the role of group_volume and why does it act radically differently depending on how I set it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am writing hoping that you can help me understand the role of
group_volumeinDigitizerAdderActor.I am trying to create a simulation for a two-detector Compton camera, where each detector is pixellated. I want to use
DigitizerAdderActorin combination with theDigitizerHitsCollectionActor, in order to collect all singles event across different detector pixels. Pixellated detectors are modeled withgate.geometry.utility.get_grid_repetition. The question is, when theDigitizerAdderActor'sgroup_volumeattribute is the mother volume containing these two pixellated detectors, I get singles with positions that are energy weighted across the entire mother volume, not within each individual pixel. However, when thegroup_volumeis one of the two detectors' name, it works as intended, meaning that I get energy weighted singles from both detector pixels. Below is the minimum reproducible code.Basically, the above code yields singles that are all aggregated, such that
singles_data.groupby("EventID").nunique().max()value just gives 1. However, when I change from cc_lower.name to lower_scatterer.name, I get singles in each pixels of not only thelower_scatterer, butlower_absorberas well. What is the role ofgroup_volumeand why does it act radically differently depending on how I set it?Beta Was this translation helpful? Give feedback.
All reactions