<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Gate 3.1.2 vs Gate 4.0</TITLE> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.6000.16788" name=GENERATOR></HEAD> <BODY> <DIV> Hi Seb, I'm working with Hyejoo on this and we have confirmed that we are using the correct low EM processes. The differences that we have seen in the sinograms for identical models and input parameters are dramatic (I've attached the figures to this email, sinogramS top and sinogramTheta bottom).  These differences seem too large to be due to a refinement in the low energy model associated with the new release of G4.  We are going to perform another GATE run with a simple asymmetric phantom (I'm thinking an elliptical cylinder phantom with a 4:1 hot cylinder offset) and run it with both standard GATE shapes and as a voxelized phantom and see if we can pin down the culprit.  Any ideas on your side? Cheers, ross            <IMG alt="Picture (Device Independent Bitmap)" src="No AttachName">       <IMG alt="Picture (Device Independent Bitmap)" src="No AttachName-1"> -----Original Message----- From: gate-users-bounces@lists.healthgrid.org [<A href="mailto:gate-users-bounces@lists.healthgrid.org">mailto:gate-users-bounces@lists.healthgrid.org</A>] On Behalf Of Seb Sent: Monday, January 05, 2009 9:44 AM To: Kang, Hyejoo/Medical Physics Cc: gate-users@lists.healthgrid.org Subject: Re: [Gate-users] Gate 3.1.2 vs Gate 4.0 Hyejoo, If I remember well, you used the low energy EM processes ? If yes: - For GateV4, you need to use the EM data files version 5.1 with Geant4 9.1 - For GateV3.1.2, you need to use the EM data files version 4.3 with Geant4 9.0 This point should be explain these differences. Seb   kangh@mskcc.org a écrit : > Dear Niklas, > > I am using the same mac-files for the two gate versions for voxelized phantom and source. Here are the macros. > > > Voxelized Phantom : > > /gate/world/daughters/name hof_brain > /gate/world/daughters/insert compressedMatrix > /gate/hof_brain/geometry/insertReader interfile > /gate/hof_brain/interfileReader/insertTranslator range > /gate/hof_brain/interfileReader/rangeTranslator/readTable range_CT.dat > /gate/hof_brain/interfileReader/rangeTranslator/describe 1 # # list > the organs which should not compressed # > #/gate/hof_brain/compression/excludeList Lung Adipose Water Muscle > Heart Liver SpineBone Bone #/gate/hof_brain/interfileReader/readFile > hof3.h33 /gate/hof_brain/interfileReader/readFile newptmodpixelCT.h33 > /gate/hof_brain/placement/setTranslation 0. 0. 0. mm > /gate/hof_brain/placement/setRotationAxis 1 0 0 > /gate/hof_brain/placement/setRotationAngle 0 deg > /gate/hof_brain/attachVoxelPhantomSD > /gate/hof_brain/addOutput doseOutput > /gate/output/doseOutput/saveUncertainty true > /gate/output/doseOutput/setFileName hof_brain_paraDose.bin > > > > Voxelized Source : > > /gate/source/addSource voxel_lung voxel > > /gate/source/voxel_lung/reader/insert interfile > /gate/source/voxel_lung/interfileReader/translator/insert linear > /gate/source/voxel_lung/interfileReader/linearTranslator/setScale 1. > Bq # # the following way to convert pixel values within a certain > range # to the correct activity by reading from a table > (activity*.dat) # /gate/source/voxel_lung/interfileReader/readFile > newptmodpixelPET.h33 > > /gate/source/voxel_lung/setType backtoback > /gate/source/voxel_lung/gps/particle gamma > /gate/source/voxel_lung/setForcedUnstableFlag true > /gate/source/voxel_lung/setForcedHalfLife 6586.2 s > /gate/source/voxel_lung/gps/energytype Mono > /gate/source/voxel_lung/gps/monoenergy 0.511 MeV # # The deafult > position of the voxellized source is in the 1^{st} # quarter. So the > voxellized source has to be shifted over half its # dimension in the > negative direction on each axis (x,y & z) dimensions # are from header > file of interfile # > /gate/source/voxel_lung/setPosition -218. -148. -117.72 mm > /gate/source/voxel_lung/gps/confine NULL > /gate/source/voxel_lung/gps/angtype iso /gate/source/voxel_lung/dump 1 > /gate/source/list > > > Thank you, > > Hyejoo > > > -----Original Message----- > From: gate-users-bounces@lists.healthgrid.org > [<A href="mailto:gate-users-bounces@lists.healthgrid.org">mailto:gate-users-bounces@lists.healthgrid.org</A>] On Behalf Of Niklas > Rehfeld > Sent: Wednesday, December 31, 2008 10:55 AM > To: gate-users@lists.healthgrid.org > Subject: Re: [Gate-users] Gate 3.1.2 vs Gate 4.0 > > Dear Hyejoo, > > Could you please post the two mac-Files? > > Thank you! > > Happy new year! > > Niklas ></DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: gate-users-bounces@lists.healthgrid.org [mailto:gate-users-bounces@lists.healthgrid.org] On Behalf Of Kang, Hyejoo/Medical Physics Sent: Wednesday, December 31, 2008 10:33 AM To: sebastien.jan@cea.fr; gate-users@lists.healthgrid.org Subject: [Gate-users] Gate 3.1.2 vs Gate 4.0 </DIV> <DIV></DIV> Hi Seb and gate users, I rad simulation jobs with the same macro with Gate 3.1.2 and Gate 4.0 separately.  Following figures show the results of sinogramS and sinogramTheta. I ran a voxelized phantom and source to generate these plots. In my previous email, I asked whether the difference I saw in those two parameters might come from using the fictitious tracking algorithm.  I think there are basic differences between two versions as shown in the figures.   The peak at 0 of the plot of sinogramS for Gate3.1.2 becomes less distinct for Gate 4.0.  Also, the dip around 180 degrees for sinogramTheta becomes bigger for Gate 4.0.  This is the same tendency I saw with the fictitious tracking option.   Did anyone see the difference between two versions? Also, are  these differences expected or not important? Thanks and happy new year! Hyejoo              <IMG alt="Picture (Device Independent Bitmap)" src="No%20AttachName">       <IMG alt="Picture (Device Independent Bitmap)" src="No%20AttachName-1"> <PRE wrap> ===================================================================== Please note that this e-mail and any files transmitted with it may be privileged, confidential, and protected from disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this communication or any of its attachments is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting this message, any attachments, and all copies and backups from your computer. </PRE> </BODY></HTML>