[Gate-users] Distinguish original photon energy?

[Larry Pierce]

Thanks David, I do not see any documentation for “enablePrimaryEnergy”, can you provide a description or link to documentation?

Thanks,

-Larry


On Mar 7, 2022, at 1:31 AM, David Leibold <D.Leibold at tudelft.nl<mailto:D.Leibold at tudelft.nl>> wrote:

Hi Larry,

if I am not mistaken, the parentID is 0 if the current particle was emitted by the source; if the current particle is a secondary particle, then the parentID will store the parent track’s event ID. I am not sure whether this is of much help when you detect your particles with a realistic detector material, though, since the secondaries might be created inside the detector itself.

If you want to use a phase space actor instead, you can use the setting “enablePrimaryEnergy”, which stores the energy of the primary particle for every hit.

Kind regards,
David Leibold


On 3 Mar2022, at 19:26, Larry Pierce <lapierce at uw.edu<mailto:lapierce at uw.edu>> wrote:

No, I have not. Can you tell me what informationis in parentID ? Does that tell the originating particle (I-123) or the originating photon energy?

Thanks,

-Larry


On Mar 3, 2022, at 10:12 AM, Konstantinos P. Chatzipapas <konhat88 at yahoo.gr<mailto:konhat88 at yahoo.gr>> wrote:


Have you try to filter hits using ParentID leaf?

Konstantinos



Στις Πέμπτη, 3 Μαρτίου 2022, 06:40:49 μ.μ. CET, ο χρήστης Larry Pierce <lapierce at uw.edu<mailto:lapierce at uw.edu>> έγραψε:


Yes, I see, thank you!

However, there may be scattered imaging photons in the window as well as scattered high-energy photons in the window.

I want to know the fraction of imaging photons and high-energy photons that contributed to the window.

If there is a way to know this for each hit or single, that would be a great help.

Thanks for the advice!

-Larry Pierce



On Mar 3, 2022, at 9:27 AM, Konstantinos P. Chatzipapas <konhat88 at yahoo.gr<mailto:konhat88 at yahoo.gr>> wrote:

Hello there,

If you have a limited window (let's say 159 keV, 10%), you may limit your result to scatter and unscattered photons of this energy. If you are using root you may set comptonPhantom==0 or !=0, as a parameter.

Does that help?

Kind Regards,
Konstantinos


​​--
--
Konstantinos CHATZIPAPAS | PhD, CNRS | "Interactions Rayonnements Ionisants & Biologie" (iRiBio)
Centre d'Etudes Nucléaires de Bordeaux-Gradignan - UMR 5797
https://www.cenbg.in2p3.fr/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.cenbg.in2p3.fr_&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=lfXR69GFfS7NT-Wp5HZqbtBDrbYoilDdmNEG7fKW7aM&m=XeFask16dCuG41NAH2Gz2MiyeWAeGipWZNaMKb02rCU&s=TtEUJZ0pneRfjMRlxQ_SBZJ4ok_kfieV4X4aGOWQTP4&e=>



Στις Πέμπτη, 3 Μαρτίου 2022, 06:07:00 μ.μ. CET, ο χρήστης Larry Pierce <lapierce at uw.edu<mailto:lapierce at uw.edu>> έγραψε:


Dear GATE users,

I have a question regarding simulation of I-123, with 83% of the emission photons at 159 keV used for imaging. It also has 3% of the photons emitted being higher-energy up to 784 keV and these can contaminate the data and reconstructed image.

When simulating our SPECT detector, I would like to know the energy of the original photon to determine if it was an “imaging photon” or a “higher-energy photon” that led to the hit or single in the detector.

Does anyone know of a way to do this in GATE?

I have considered that we may use multiple overlapping spectrum sources with a mixture of imaging and high-energy photons and that the output source ID can then tell us if the originating photon was an imaging photon or a high-energy photon.

Still, I would like to ask the group for their input if there are other better ways to approach the issue.

Thank you for your consideration,

-Larry Pierce




_______________________________________________
Gate-users mailing list
Gate-users at lists.opengatecollaboration.org<mailto:Gate-users at lists.opengatecollaboration.org>
http://lists.opengatecollaboration.org/mailman/listinfo/gate-users<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opengatecollaboration.org_mailman_listinfo_gate-2Dusers&d=DwMGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=lfXR69GFfS7NT-Wp5HZqbtBDrbYoilDdmNEG7fKW7aM&m=XeFask16dCuG41NAH2Gz2MiyeWAeGipWZNaMKb02rCU&s=iKZVrsYG6YxPkdxsBM70ppg9C0CBKCito2-hqOwe1kw&e=>

_______________________________________________
Gate-users mailing list
Gate-users at lists.opengatecollaboration.org<mailto:Gate-users at lists.opengatecollaboration.org>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opengatecollaboration.org_mailman_listinfo_gate-2Dusers&d=DwIGaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=lfXR69GFfS7NT-Wp5HZqbtBDrbYoilDdmNEG7fKW7aM&m=XeFask16dCuG41NAH2Gz2MiyeWAeGipWZNaMKb02rCU&s=iKZVrsYG6YxPkdxsBM70ppg9C0CBKCito2-hqOwe1kw&e=


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengatecollaboration.org/pipermail/gate-users/attachments/20220308/03b96c00/attachment-0001.html>