<br><font size=2 face="sans-serif">First, let me copy my old email about this question in 2004, </font>
<br>
<br>
<br><font size=2 face="sans-serif">/*****************************************************************************************</font>
<br>
<br><font size=2 face="sans-serif">I spent some time read the source code of GATE recently and found out why the</font>
<br><font size=2 face="sans-serif">spectrum looks different.</font>
<br>
<br><font size=2 face="sans-serif">The GATE program first generates two gamma photons, let's say S0 and S1. </font>
<br><font size=2 face="sans-serif">Then GATE will traces down the two photons respectively, and generates</font>
<br><font size=2 face="sans-serif">a Hits list. After that, the program will generates Adder_list and Readout_list</font>
<br><font size=2 face="sans-serif">one after another before generates the Single_list. </font>
<br>
<br><font size=2 face="sans-serif">If you check the ASCII output files, you will find that in the Singles_Adder file,</font>
<br><font size=2 face="sans-serif">for each photon, if a Compton backscatter event happened, then the event of energy</font>
<br><font size=2 face="sans-serif">deposit after backscatter will be listed in front of all other events in the Adder_list. </font>
<br><font size=2 face="sans-serif">So for each photon-pair with one Compton backscatter event, we should have two </font>
<br><font size=2 face="sans-serif">possible event lists as:</font>
<br>
<br><font size=2 face="sans-serif">Case 1:</font>
<br><font size=2 face="sans-serif">(1). S0 backscatter in detector B (or A), but deposits energy (0.17MeV) in detector A (or B)</font>
<br><font size=2 face="sans-serif">(2). S0 deposits remained energy (0.34MeV) in detector B (or A)</font>
<br><font size=2 face="sans-serif">(3). S1_photoelectric_absorption (0.511MeV) in detector A (or B)</font>
<br><font size=2 face="sans-serif">or </font>
<br>
<br><font size=2 face="sans-serif">Case 2:</font>
<br><font size=2 face="sans-serif">(1). S0_photoelectric_absorption (0.511MeV) in detector A (or B)</font>
<br><font size=2 face="sans-serif">(2). S1 backscatter in detector B (or A), but deposits energy (0.17MeV) in detector A (or B)</font>
<br><font size=2 face="sans-serif">(3). S1 deposits remained energy (0.34MeV) in detector B (or A)</font>
<br>
<br><font size=2 face="sans-serif">when GATE process the Adder_lsit, in Case1, it will add the energy from enevt3 to enevt1 and</font>
<br><font size=2 face="sans-serif">update the other information of event1 with event3, and keep the event2, then generates the</font>
<br><font size=2 face="sans-serif">Readout_list with two events:</font>
<br><font size=2 face="sans-serif">(1). S1 (energy 0.17+0.511MeV) in detector A (or B)</font>
<br><font size=2 face="sans-serif">(2). S0_remained_energy (0.34MeV) in detector B (or A)</font>
<br>
<br><font size=2 face="sans-serif">for Case2, GATE will add the energy from enevt2 to enevt1 and</font>
<br><font size=2 face="sans-serif">keep the original information of event1, then generates the</font>
<br><font size=2 face="sans-serif">Readout list as:</font>
<br><font size=2 face="sans-serif">(1). S0 (energy 0.17+0.511MeV) in detector A (or B)</font>
<br><font size=2 face="sans-serif">(2). S1_remained_energy (0.34MeV) in detector B (or A)</font>
<br>
<br><font size=2 face="sans-serif">Therefore, no matter the Compton backscatter event was happened with photon S0 or S1, or in </font>
<br><font size=2 face="sans-serif">detector A or detector B, in the Singles_Readout List, the high energy Single always comes </font>
<br><font size=2 face="sans-serif">first. Then later, this Single will appears in the first column in the coincidence list. </font>
<br><font size=2 face="sans-serif">Which means that the first and the second photons in the coincidence pairs do not always </font>
<br><font size=2 face="sans-serif">correspond with the original two gamma photons S0 and S1.</font>
<br>
<br><font size=2 face="sans-serif">***********************************************************************************************/</font>
<br>
<br><font size=2 face="sans-serif">2. When GATE processing the data it will in the order of digitizer chain.</font>
<br><font size=2 face="sans-serif"> and it always like this:</font>
<br><font size=2 face="sans-serif"> hits -> adder -> readout -> (blur) -> coincidence</font>
<br><font size=2 face="sans-serif"> |</font>
<br><font size=2 face="sans-serif"> -> delay -> delaycoincidence</font>
<br>
<br><font size=2 face="sans-serif"> As what I explained in the old email, all these steps is happened in the process of </font>
<br><font size=2 face="sans-serif">"adder" when GATE was processing the Compton back scatter events. So whenever the </font>
<br><font size=2 face="sans-serif">"coincidence" or "delay" module began to process the singles list, the sequence of </font>
<br><font size=2 face="sans-serif">the singles was already fixed in the singles list, and cannot be changed.</font>
<br>
<br><font size=2 face="sans-serif">I don't know what's your meaning about "</font><font size=2><tt>sort by detector or detector pair</tt></font><font size=2 face="sans-serif">". Whenever</font>
<br><font size=2 face="sans-serif">you sort one detector, for example, detector0, it will appear both in the first</font>
<br><font size=2 face="sans-serif">column and second column, and you don't know which event belong to the gamma1 and</font>
<br><font size=2 face="sans-serif">which event belong to the gamma2. So all you can do is just add up all the events</font>
<br><font size=2 face="sans-serif">from column1 and column2 (and divide by 2 if you like), and that's the spectra for detector0.</font>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">Dr. Yuxuan ZHANG <br>
Dept. Experimental Diagnostic Imaging<br>
Univ. Texas, MD Anderson Cancer Center<br>
1515 Holcombe Blvd, Unit 217<br>
Houston, TX 77030-4095<br>
<br>
Tel: +1-713-745-1671 <br>
Fax: +1-713-745-1672</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Paul Vaska <vaska@bnl.gov></b></font>
<p><font size=1 face="sans-serif">08/27/2007 12:00 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: yuxuan.zhang@di.mdacc.tmc.edu</font>
<br><font size=1 face="sans-serif"> cc: Irène Buvat <buvat@imed.jussieu.fr>, gate-users-bounces@lists.healthgrid.org, gate-users@lists.healthgrid.org, Wonho Lee <wlee@bnl.gov>, Sudeepti Southekal <southekal@bnl.gov></font>
<br><font size=1 face="sans-serif"> Subject: Re: [Gate-users] Fwd: FW: Difference in energy spectrum for first and second event in cylindrical PET system</font></table>
<br>
<br>
<br><font size=2><tt>Hi Andrew,<br>
<br>
I don't really understand this answer. We have found a different <br>
pattern concerning the ordering in the coincidence output. Maybe the <br>
code has changed. From looking at time difference spectra for a <br>
given detector pair (i.e. time of det b minus time of det a, _not_ <br>
time of column 2 minus time of column 1) it appears that true and <br>
random coincidences are treated differently. For trues, it seems <br>
that the order can be either way (don't know what determines the <br>
order) but for randoms, the 2nd single is always the later one. <br>
Given this, it is still disconcerting to me that the energy spectra <br>
are different. True and random coincidences can have different <br>
energy spectra (due to different constraints on geometry) but I don't <br>
see how this could explain your effect. Hopefully if you sort by <br>
detector or detector pair instead of the position of the data in the <br>
file, the energy and time spectra would make sense.<br>
<br>
Paul<br>
<br>
Paul Vaska, Ph.D.<br>
Medical Department, Building 490<br>
Brookhaven National Laboratory<br>
Upton, NY 11973<br>
vaska@bnl.gov (631)344-6228 fax:(631)344-4146<br>
<br>
<br>
<br>
On Aug 27, 2007, at 11:09 AM, yuxuan.zhang@di.mdacc.tmc.edu wrote:<br>
<br>
><br>
> Hi,<br>
><br>
> This effect is not something new. One or two years ago someone <br>
> already found this and reported here.<br>
> At that time I was also curious about this so I spent some time <br>
> looking into it. After reading the source<br>
> code, my conclusion is that this result is caused by the GATE code <br>
> about how it processing the energy<br>
> deposit from hits.<br>
><br>
> When two gamma ray photons travel inside the material, GATE records <br>
> all the energy deposit in an array.<br>
> Then in the "adder" process, GATE will add up all the energy <br>
> deposits from the same gamma photon and<br>
> stored in one of the cells in the same array. During this step, the <br>
> gamma photon with a higher total deposited<br>
> energy will always stored in front of the other gamma photon (or <br>
> after, I can remember clearly). So in<br>
> the output file the photon1 and photon2 are just a label, it does <br>
> not represents the original photon1 or<br>
> photon2.<br>
><br>
> So if you really want the spectrum of the coincidences, just add <br>
> the photon1 and photon2 together.<br>
><br>
> Yuxuan<br>
><br>
><br>
><br>
><br>
> Irène Buvat <buvat@imed.jussieu.fr><br>
> Sent by: gate-users-bounces@lists.healthgrid.org<br>
> 08/26/2007 09:19 AM<br>
><br>
><br>
> To: gate-users@lists.healthgrid.org<br>
> cc:<br>
> Subject: [Gate-users] Fwd: FW: Difference in energy <br>
> spectrum for first and second event in cylindrical PET system<br>
><br>
><br>
><br>
> X-Ids: 165<br>
> X-Greylist: delayed 857 seconds by postgrey-1.21 at ns2919.ovh.net;<br>
> Sat, 25 Aug 2007 00:17:05 CEST<br>
> X-IronPort-AV: E=Sophos;i="4.19,305,1183352400";<br>
> d="mac'?jpg'145?scan'145,208,217,145";a="310266"<br>
> Subject: FW: Difference in energy spectrum for first and second <br>
> event in<br>
> cylindrical PET system<br>
> Date: Fri, 24 Aug 2007 16:54:28 -0500<br>
> Thread-Topic: Difference in energy spectrum for first and second <br>
> event in<br>
> cylindrical PET system<br>
> Thread-Index: Acfmlfu0s1jG3B4WQ1WCyGHMNxLkBQAAzp2w<br>
> From: "Andrew Goertzen" <AGoertzen2@exchange.hsc.mb.ca><br>
> To: <gate-users-owner@lists.healthgrid.org><br>
> X-OriginalArrivalTime: 24 Aug 2007 21:54:28.0267 (UTC)<br>
> FILETIME=[57E9BFB0:01C7E699]<br>
> Sender: mailman-bounces@lists.healthgrid.org<br>
> X-Virus-Scanned: ClamAV 0.88.7/4054/Fri Aug 24 18:55:59 2007 on </tt></font>
<br><font size=2><tt>> shiva.jussieu.fr<br>
> X-Virus-Status: Clean<br>
> X-Miltered: at shiva.jussieu.fr with ID 46CF5710.007 by Joe's j- <br>
> chkmail (http://j-chkmail.ensmp.fr)!<br>
> The following message was rejected by the address 'gate- <br>
> users@lists.healthgrid.org'. Could you please post it on my behalf?<br>
> Thanks,<br>
> Andrew<br>
><br>
> Hi All,<br>
> I am simulating a cylindrical PET system in GATE 3.0.0 with the <br>
> geometry of a microPET R4 and I am hoping someone can help explain <br>
> the behaviour I am seeing. My source is a 1.25 MBq line source at <br>
> the centre of the FOV. Data is written to an ASCII text file. <br>
> When I create an energy histogram from the coincidence data output <br>
> file I notice that the events identified as 'single 1' in a <br>
> coincidence event (i.e. columns 1-21 of a coincident event in ascii <br>
> format as described in section 10.1 of the user manual) have a <br>
> different energy spectrum than events identified as 'single 2'. I <br>
> have included an example of this in the attached jpg image. I do <br>
> not think it is time related because I get this behaviour with and <br>
> without 1.5ns of time blurring. Also, the timestamp for single 1 <br>
> is not always less than for single 2. I do not think it is energy <br>
> related because the energy of single 1 is neither always greater <br>
> than or always less than single 2.<br>
> So I am hoping that someone can answer the following questions:<br>
> How does GATE determine the order of singles that make up a <br>
> coincident event?<br>
> Has anyone else observed this sort of difference between the first <br>
> and second single?<br>
> I have included the .mac file I am using.<br>
> Regards,<br>
> Andrew Goertzen<br>
> Department of Radiology<br>
> University of Manitoba<br>
> <<EnergyHistogram.jpg>> <<microPETR4.mac>><br>
><br>
> Content-Type: image/jpeg;<br>
> name="EnergyHistogram.jpg"<br>
> Content-Description: EnergyHistogram.jpg<br>
> Content-Disposition: attachment;<br>
> filename="EnergyHistogram.jpg"<br>
><br>
><br>
> Content-Type: application/octet-stream;<br>
> name="microPETR4.mac"<br>
> Content-Description: microPETR4.mac<br>
> Content-Disposition: attachment;<br>
> filename="microPETR4.mac"<br>
><br>
><br>
> This email and/or any documents in this transmission is intended <br>
> for the<br>
> addressee(s) only and may contain legally privileged or <br>
> confidential information. Any unauthorized use, disclosure, <br>
> distribution, copying or dissemination is strictly prohibited. If <br>
> you receive this transmission in error, please notify the sender <br>
> immediately and return the original.<br>
><br>
> Ce courriel et tout document dans cette transmission est destiné à <br>
> la personne ou aux personnes à qui il est adressé. Il peut contenir <br>
> des informations privilégiées ou confidentielles. Toute <br>
> utilisation, divulgation, distribution, copie, ou diffusion non <br>
> autorisée est strictement défendue. Si vous n'êtes pas le <br>
> destinataire de ce message, veuillez en informer l'expéditeur <br>
> immédiatement et lui remettre l'original.<br>
><br>
><br>
> -- <br>
><br>
> Irene Buvat, PhD<br>
> Equipe "Imagerie de la perfusion et des échanges moléculaires"<br>
> U678 INSERM<br>
> CHU Pitié Salpêtrière<br>
> 91 Boulevard de l'Hôpital<br>
> 75634 Paris Cedex 13<br>
> France<br>
> Tel : 01 53 82 84 19<br>
> Fax : 01 53 82 84 48<br>
> email : buvat@imed.jussieu.fr<br>
> http://www.guillemet.org/ <br>
> irene_______________________________________________<br>
> Gate-users mailing list<br>
> Gate-users@lists.healthgrid.org<br>
> http://lists.healthgrid.org/mailman/listinfo/gate-users<br>
><br>
><br>
> _______________________________________________<br>
> Gate-users mailing list<br>
> Gate-users@lists.healthgrid.org<br>
> http://lists.healthgrid.org/mailman/listinfo/gate-users<br>
<br>
</tt></font>
<br>
<br>