<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">P.S. Dear Donghyeon Lee, <div class=""><br class=""></div><div class="">I noticed a made mistake in my message from yesterday. The last sentence should read : </div><div class=""><br class=""></div><div class="">This means that every 15 bytes following this header will form an event record consisting of 8 bytes for the time stamp, followed by 2 bytes for the detector id, 2 bytes for the gantry angular position, 2 bytes for the bed position, and 1 byte for the deposited energy.</div><div class=""><br class=""></div><div class="">Sorry about this. Kind regards, Christian Morel</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">Le 14 oct. 2018 à 17:03, MOREL Christian <<a href="mailto:morel@cppm.in2p3.fr" class="">morel@cppm.in2p3.fr</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear Donghyeon Lee,<div class=""><br class=""></div><div class="">Since you are using only 16 bits to store your detector ID, the first 5 u16 are employed the way you have decoded it. Then, the bytes following these 5 u16 are read and decoded on their own. Therefore, you do not have to revert the byte order anymore, which should read:</div><div class=""><br class=""></div><div class="">1111111111111100 : 1st u16</div><div class="">111111100100000: 2nd u16 for the crystal ID rule</div><div class="">0101001110111111: 3rd u16 for the general topology</div><div class="">010100100000111: 4th u16 for the tangential topology</div><div class="">0000000110000111: 5th u16 for the axial topology</div><div class="">00000000</div><div class="">00000001: 1 record type only</div><div class="">00000110: TTTcdEn corresponding to event record tag (TTTT= 0000), consisting of singles (c = 0), with storage of detecor ID (d = 1) and energy (E = 1).</div><div class="">00110000: NNgbsGZR corresponding to the second byte describing the event tag, here with storage of the gantry angular position (g = 1) and the gantry axial (bed) position (b = 1)</div><div class=""><br class=""></div><div class="">This means that every 15 bytes following this header will form an event record consisting of 8 bytes for the time stamp, followed by two bytes for the gantry angular position, 2 bytes for the bed position, 2 bytes for the detector id and 1 byte for the deposited energy.</div><div class=""><br class=""></div><div class="">Hope this helps, regards, Christian Morel</div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">Le 27 sept. 2018 à 08:05, Donghyeon Lee <<a href="mailto:leedhyun85@kaist.ac.kr" class="">leedhyun85@kaist.ac.kr</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">Dear <span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">Christian</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><br class=""></span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">I sincerely think you for your detail answer.</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">The answer you wrote is exactly what I wanted.</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">I checked the output and compared your answer.</div><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">But there are a little differences.</div><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">The following is the encorded output I got:</div><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">11111111111111<strong class=""><span style="color: rgb(255, 0, 0); font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">00</span></strong></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">1111111001000000</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0101001110111111 - x</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0101001000000111 - y</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0000000110000111 - z</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="color: rgb(0, 85, 255); font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0000000100000000</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="color: rgb(0, 85, 255); font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0011000000000110</span></div><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">As you can notice, first u16 refers to the size of integer values. <strong class=""><span style="color: rgb(255, 0, 0); font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">00</span></strong> stands for 'u16'. 01 for <span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">'u32'</span> and 10 for <span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">'u64'</span>, for example.</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">Then I think next16 bits encoding rule is followed:</span><br style="font-size: 14.6667px;" class=""><br style="font-size: 14.6667px;" class="">7 bits Rsectors<br style="font-size: 14.6667px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">2 bits Modules </span><br style="font-size: 14.6667px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">1 bit Submodule</span><br style="font-size: 14.6667px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">7 bits Crystals </span><br style="font-size: 14.6667px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0 bit Layer </span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><br class=""></span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">In my opinion, the reason why Rsectors has 7 bits is that there is only one layer and it dose require any bit to record.</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">And the followings have same rules you wrote.</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><br class=""></span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">But I couldn't understand the number emphasized by blue.</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">It doesn't seem to follow the rule. </span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">I am still confused about the event record part....</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><br class=""></span></div><div style="line-height: 17.6px; font-size: 14.6667px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class="">11111111111111<strong class=""><span style="color: rgb(255, 0, 0); font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px; font-family: 돋움;" class="">00</span></strong></div><div style="line-height: 17.6px; font-size: 14.6667px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class="">1111111001000000</div><div style="line-height: 17.6px; font-size: 14.6667px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class="">0101001110111111 - x</div><div style="line-height: 17.6px; font-size: 14.6667px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class="">0101001000000111 - y</div><div style="line-height: 17.6px; font-size: 14.6667px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class="">0000000110000111 - z</div><div style="line-height: 17.6px; font-size: 14.6667px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class=""><span style="color: rgb(0, 85, 255); font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px; font-family: 돋움;" class="">0000000100000000</span></div><p style="font-size: 14.6667px; line-height: 17.6px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="line-height: 17.6px; font-size: 14.6667px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class=""><span style="color: rgb(0, 85, 255); font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px; font-family: 돋움;" class="">0011000000000110</span></div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0000000000000000</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0000000000000000</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">0010110100000000</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">1111111101111111</div><p style="font-size: 14.6667px; line-height: 17.6px; font-family: 돋움; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">1011001100011010</div><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">I copy and paste first 12 of 'u16' if it would help you to make out the output.</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">Thank you.</div><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">Best regard,</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class="">Donghyeon Lee.</div><div style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 14.6667px; font-family: 돋움; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""><br class=""></span></div><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p><blockquote style="border-left: #000 2px solid;padding:0 0 0 5px;margin-left:5px;" class=""><div style="line-height: 18px; font-size: 9pt; font-family: Dotum; padding: 0px 0px 5px; margin-top: 0px; margin-bottom: 0px;" class="">-----------------------원본메일-----------------------<br class="">보낸사람 : MOREL Christian <<a href="mailto:morel@cppm.in2p3.fr" class="">morel@cppm.in2p3.fr</a>><br class="">받는사람: <a href="mailto:gate-users@lists.opengatecollaboration.org" class="">gate-users@lists.opengatecollaboration.org</a><br class="">보낸날짜: 2018-09-21 02:52:43 GMT +0900 (Asia/Seoul)<br class="">제목: Re: [Gate-users] LMF '***.css' analysis</div>
Dear Donghyeon Lee,
<br class="">
<br class=""> The first u16 is used to set the number of bits used to store detector ID. Integer values of 0, 1, and 2 are used to set it to 16-, 32- and 64-bits, respectively. If the first bit of the LMF encoding header is equal to 1, detector ID is encoded over 16 bits by default. In this case, the LMF encoding header starts directly by the rule used to store the encoding rule for detector ID described below. Since you are encoding your detector id on 16 bits, the first u16 directly specifies your scanner topology, e.g. 1111110010000001, i.e.:
<br class="">
<br class=""> 111111 [for numbering 42 Rsectors (numbered from 0 to 41) on 6 bits allowing to identify 64 Rsectors]
<br class=""> 00 [for numbering 4 Modules (numbered from 0 to 3) on 2 bits]
<br class=""> 1 [for numbering 1 Submodule (numbered 0) on 1 bit]
<br class=""> 000000 [for numbering 64 Crystals (numbered from 0 to 64) on 6 bits]
<br class=""> 1 [for numbering 1 Layer (numbered 0) on 1 bit]
<br class="">
<br class=""> Then this 16 bits encoding rule is followed by the very description of your scanner topology: i.e. 1010011101111110, i.e.:
<br class="">
<br class=""> 101001 [=41+1 Rsectors]
<br class=""> 11 [=3+1 Modules]
<br class=""> 0 [=0+1 Submodule]
<br class=""> 111111 [=63+1 Crystals]
<br class=""> 0 [=0+1 Layer]
<br class="">
<br class=""> The following two u16 describe the tangential and axial topology. In your case, the tangential encoding will be 1010010000001110, i.e.:
<br class="">
<br class=""> 101001 [=41+1 Rsectors]
<br class=""> 00 [=0+1 Modules]
<br class=""> 0 [=0+1 Submodule]
<br class=""> 000111 [=7+1 Crystals]
<br class=""> 0 [=0+1 Layer]
<br class="">
<br class=""> and the axial encoding will be 0000001100001110, i.e.:
<br class="">
<br class=""> 000000 [=0+1 Rsectors]
<br class=""> 11 [=3+1 Modules]
<br class=""> 0 [=0+1 Submodule]
<br class=""> 000111 [=7+1 Crystals]
<br class=""> 0 [=0+1 Layer]
<br class="">
<br class=""> Hence the encoding header of your ccs file will comprise 6 u16:
<br class="">
<br class=""> 1111110010000001
<br class=""> 1010011101111110
<br class=""> 1010010000001110
<br class=""> 0000001100001110
<br class=""> 0000000000000001
<br class=""> 0000011000110000
<br class="">
<br class=""> The 5th one is used to store the number of record types (1 in your case) and the 6th one to describe the event format (event record header), i.e. in your case:
<br class="">
<br class=""> 0000 [this record is an event record]
<br class=""> 0 [this is a single]
<br class=""> 1 [id is stored on 16 bits]
<br class=""> 1 [energy is stored on 8 bits]
<br class=""> 0 [no energy and DOI from neighboring crystals]
<br class=""> 00 [not used since no energy from neighboring crystals]
<br class=""> 1 [azimuth position stored on 16 bits (you do not need this if your scanner is not rotating)]
<br class=""> 1 [axial position stored on 16 bits (you also do not need this if your bed is not moving axially)]
<br class=""> 0000 [not used in your case]
<br class="">
<br class=""> Thus, each event record will be stored on 64 bits for tag (first bit set to 0) and time (63 following bits) + 16 bits (for detector id) + 8 bits (for energy) + 16 bits (for azimuthal position) + 16 bits (for axial position) = 120 bits (15 bytes).
<br class="">
<br class=""> Then, all the following block of 120 bits (15 bytes) are used to store events, one event per block of 120 bits.
<br class="">
<br class=""> Hope this answers your question.
<br class="">
<br class=""> With kind regards, Christian Morel
<br class="">
<br class=""> > Le 20 sept. 2018 à 10:18, Donghyeon Lee <<a href="mailto:leedhyun85@kaist.ac.kr" class="">leedhyun85@kaist.ac.kr</a>> a écrit :
<br class=""> >
<br class=""> > Hello, Christian Morel
<br class=""> >
<br class=""> > Thank you for your answer.
<br class=""> > What I wrote in '.mac' is to get output below:
<br class=""> >
<br class=""> > /gate/output/lmf/enable
<br class=""> > /gate/output/lmf/setFileName benchmarkPET
<br class=""> > /gate/output/lmf/setDetectorIDBool 1
<br class=""> > /gate/output/lmf/setEnergyBool 1
<br class=""> > /gate/output/lmf/setGantryAxialPosBool 1
<br class=""> > /gate/output/lmf/setGantryAngularPosBool 1
<br class=""> > /gate/output/lmf/setSourcePosBool 0
<br class=""> > /gate/output/lmf/setNeighbourBool 0
<br class=""> > /gate/output/lmf/setNeighbourhoodOrder 0
<br class=""> > /gate/output/lmf/setCoincidenceBool 0
<br class=""> > /gate/output/lmf/setGateDigiBool 0
<br class=""> > /gate/output/lmf/setComptonBool 0
<br class=""> > /gate/output/lmf/setSourceIDBool 0
<br class=""> > /gate/output/lmf/setSourceXYZPosBool 0
<br class=""> > /gate/output/lmf/setGlobalXYZPosBool 0
<br class=""> > /gate/output/lmf/setEventIDBool 0
<br class=""> > /gate/output/lmf/setRunIDBool 0
<br class=""> >
<br class=""> > And the size of binary encording is uin16.
<br class=""> >
<br class=""> > The numbers of Rsectors, Modules, and Crystals are 42, 1*1*4, 1*8*8 for each. (x*y*z)
<br class=""> >
<br class=""> > I hope this answers are helpful for you to understand.
<br class=""> >
<br class=""> > Best regards,
<br class=""> > Donghyeon Lee.
<br class=""> >
<br class=""> >
<br class=""> >
<br class=""> > -----------------------Original Message-----------------------
<br class=""> > From: MOREL Christian <<a href="mailto:morel@cppm.in2p3.fr" class="">morel@cppm.in2p3.fr</a>>
<br class=""> > To: <a href="mailto:gate-users@lists.opengatecollaboration.org" class="">gate-users@lists.opengatecollaboration.org</a>
<br class=""> > Sent date: 2018-09-20 01:20:55 GMT +0900 (Asia/Seoul)
<br class=""> > Subject: Re: [Gate-users] LMF '***.css' analysis
<br class=""> > Dear Donghyeon Lee,
<br class=""> >
<br class=""> > Can you specify me the size of your detector id encoding (16 bits, 32 bits or 64 bits ?)
<br class=""> >
<br class=""> > Looking forward to receiving your answer, with kind regards, Christian Morel
<br class=""> >
<br class=""> >> Le 17 sept. 2018 à 06:18, Donghyeon Lee < <a href="mailto:leedhyun85@kaist.ac.kr" class="">leedhyun85@kaist.ac.kr</a>> a écrit :
<br class=""> >>
<br class=""> >> Dear all GATE users,
<br class=""> >>
<br class=""> >> Hello, I tried to get the information from the LMF(.css) output recently.
<br class=""> >> I read the four documents in the folder(LMF_v3.0) but still not clear.
<br class=""> >> In particular, 'LMF_specifs.pdf', which is about the encoding order for '***.css'.
<br class=""> >>
<br class=""> >> I successfully decorded 'the LMF encoding header' at the '***.css' file, but not following 'the LMF event record'.
<br class=""> >> To understand the encording order of it, I compared the number I got from the file and the document several times....
<br class=""> >>
<br class=""> >> Can you explain the encording order of 'The LMF event record'?
<br class=""> >> Or Is there additional materials to analyse this LMF file?
<br class=""> >>
<br class=""> >> And there were several questions which are similar with this question such as
<br class=""> >>
<a href="http://lists.opengatecollaboration.org/pipermail/gate-users/2016-October/009182.html" class="">http://lists.opengatecollaboration.org/pipermail/gate-users/2016-October/009182.html</a>
<br class=""> >> and some others. But it wasn't the one for me.
<br class=""> >>
<br class=""> >> I appreciate your attention for my question.
<br class=""> >>
<br class=""> >> Best regards,
<br class=""> >> Donghyeon Lee.
<br class=""> >>
<br class=""> >> Donghyeon Lee
<br class=""> >> Ph.D Candidate
<br class=""> >> Medical Imaging & Radiotherapeutics Lab
<br class=""> >> Dept. Nuclear and Quantum Engineering
<br class=""> >> KAIST
<br class=""> >> Office: +82-42-350-3868
<br class=""> >> Cell: +82-10-2859-6932
<br class=""> >> <a href="mailto:leedhyun85@kaist.ac.kr" class="">leedhyun85@kaist.ac.kr</a>
<br class=""> >> _______________________________________________
<br class=""> >> Gate-users mailing list
<br class=""> >> <a href="mailto:Gate-users@lists.opengatecollaboration.org" class="">Gate-users@lists.opengatecollaboration.org</a>
<br class=""> >>
<a href="http://lists.opengatecollaboration.org/mailman/listinfo/gate-users" class="">http://lists.opengatecollaboration.org/mailman/listinfo/gate-users</a>
<br class="">
<br class=""> __________________
<br class=""> Christian MOREL, PhD
<br class=""> Professeur des universités
<br class=""> Centre de Physique des Particules de Marseille (CPPM)
<br class=""> Aix-Marseille Université et CNRS/IN2P3
<br class=""> 163, Av. de Luminy, Case 902, 13288 Marseille, France
<br class="">
<br class=""> tel: +33 (0)4 91 82 76 73
<br class=""> fax: +33 (0)4 91 82 72 99
<br class=""> mobile: +33 (0)6 16 44 20 16
<br class=""> <a href="mailto:morel@cppm.in2p3.fr" class="">email: morel@cppm.in2p3.fr</a>
<br class=""> url:
<a href="http://imxgam.in2p3.fr/" class="">http://imXgam.in2p3.fr</a>
<br class="">
<br class=""> _______________________________________________
<br class=""> Gate-users mailing list
<br class=""> <a href="mailto:Gate-users@lists.opengatecollaboration.org" class="">Gate-users@lists.opengatecollaboration.org</a>
<br class="">
<a href="http://lists.opengatecollaboration.org/mailman/listinfo/gate-users" class="">http://lists.opengatecollaboration.org/mailman/listinfo/gate-users</a>
</blockquote><p style="font-family: 돋움; font-size: 14.6667px; line-height: 17.6px; margin-top: 0px; margin-bottom: 0px;" class=""> </p>
<img id="mailexp" width="0" heigh="0" border="0" src="https://mail.kaist.ac.kr/Mail?act=RECEIPT_CHECK&ukey=5bac74163fef0b017054c43d&userid=leedhyun85&mhost=kaist.ac.kr&ahost=d0001" class=""></div></blockquote></div><br class=""><div class="">
<div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">__________________<br class="">Christian MOREL, PhD<br class="">Professeur des universités<br class="">Centre de Physique des Particules de Marseille (CPPM)<br class="">Aix-Marseille Université et CNRS/IN2P3<br class="">163, Av. de Luminy, Case 902, 13288 Marseille, France<br class=""><br class="">tel: +33 (0)4 91 82 76 73<br class="">fax: +33 (0)4 91 82 72 99<br class="">mobile: +33 (0)6 16 44 20 16<br class=""><a href="mailto:morel@cppm.in2p3.fr" class="">email: morel@cppm.in2p3.fr</a><br class="">url: <a href="http://imXgam.in2p3.fr" class="">http://imXgam.in2p3.fr</a></div></div>
</div>
<br class=""></div></div>_______________________________________________<br class="">Gate-users mailing list<br class=""><a href="mailto:Gate-users@lists.opengatecollaboration.org" class="">Gate-users@lists.opengatecollaboration.org</a><br class="">http://lists.opengatecollaboration.org/mailman/listinfo/gate-users</div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">__________________<br class="">Christian MOREL, PhD<br class="">Professeur des universités<br class="">Centre de Physique des Particules de Marseille (CPPM)<br class="">Aix-Marseille Université et CNRS/IN2P3<br class="">163, Av. de Luminy, Case 902, 13288 Marseille, France<br class=""><br class="">tel: +33 (0)4 91 82 76 73<br class="">fax: +33 (0)4 91 82 72 99<br class="">mobile: +33 (0)6 16 44 20 16<br class=""><a href="mailto:morel@cppm.in2p3.fr" class="">email: morel@cppm.in2p3.fr</a><br class="">url: http://imXgam.in2p3.fr</div></div>
</div>
<br class=""></div></body></html>