<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Arial,Helvetica,sans-serif'>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em>Hello GATErs,</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br /><em> I'm trying to mimic a non-circular tomographic acquisition in GATE meaning that I'll use the minimal detector/phantom distances that were retrieved from real acquisitions.</em><br /><em> I have 2 problems:</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br /><em> 1 - Model different distances to each detector head.</em><br /><em> 2 - Since I'm using a voxelized phantom from a DICOM image, it is a cubic image and I get overlaps between the detector and the corner of the voxel image made of air (because the detector rotates closely to the phantom).</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em>Any ideas how I could simulate that ?</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em>You can see below what I have already tested and the errors I got.</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em>Thanks in advance</em></div>
<br /> <br /><em>Problem #1</em><br /><em> - With the ring repeater it won't work because I should have different distances for each detector head.</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em> - The GenericRepeaterMove repeats the detector just as I need. It sets different distances but it won't turn around the phantom (tomographic).</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em> So, my solutions for the moment is to use the genericMove with just one detector head ( but rotating 360° instead of 180° ).</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em>Problem 2</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em> - Use of a tesselated volume. However, it has too many points since it is DICOM image converted to stl. I had to kill the simulation after 4h stuck in geometry initialization.</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em> - Use of the hybrid navigator: the MergedVolumeActor. Surprisingly I get a message of overlap. </em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em> It works if using the number of particle as 100,000, but not beyond that. Furthermore, when I use the setTimeSlice method with acquisition values (0 s/40 s/2400 s) it doesn't work.</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em> This is the message I get: </em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="font-family: terminal, monaco, monospace;">-------- WWWW ------- G4Exception-START -------- WWWW -------</span><br /><span style="font-family: terminal, monaco, monospace;">*** G4Exception : GeomNav1002</span><br /><span style="font-family: terminal, monaco, monospace;"> issued by : G4Navigator::ComputeStep()</span><br /><span style="font-family: terminal, monaco, monospace;">Track stuck or not moving.</span><br /><span style="font-family: terminal, monaco, monospace;"> Track stuck, not moving for 10 steps</span><br /><span style="font-family: terminal, monaco, monospace;"> in volume -patient_physVol- at point (-26.4331,-74.707,57.1845) (local point (-0.0658974,0.488281,-0.94051))</span><br /><span style="font-family: terminal, monaco, monospace;"> direction: (-0.761641,0.500866,0.411141) (local direction: (-0.761641,0.500866,0.411141)).</span><br /><span style="font-family: terminal, monaco, monospace;"> Potential geometry or navigation problem !</span><br /><span style="font-family: terminal, monaco, monospace;"> Trying pushing it of 1e-07 mm ...Potential overlap in geometry!</span><br /><br /><span style="font-family: terminal, monaco, monospace;">*** This is just a warning message. ***</span><br /><span style="font-family: terminal, monaco, monospace;">-------- WWWW -------- G4Exception-END --------- WWWW -------</span><br /><br /><span style="font-family: terminal, monaco, monospace;"> 206 150 11.7 -33.8 0.208 0 1e-07 142 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 207 151 11.7 -34 0.208 0 0.995 143 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 208 152 11.7 -34.1 0.208 0 0.995 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 209 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 210 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 211 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 212 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 213 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 214 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 215 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 216 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 217 152 11.7 -34.1 0.208 0 0 144 patient_physVol Transportation</span><br /><br /><span style="font-family: terminal, monaco, monospace;">-------- WWWW ------- G4Exception-START -------- WWWW -------</span><br /><span style="font-family: terminal, monaco, monospace;">*** G4Exception : GeomNav1002</span><br /><span style="font-family: terminal, monaco, monospace;"> issued by : G4Navigator::ComputeStep()</span><br /><span style="font-family: terminal, monaco, monospace;">Track stuck or not moving.</span><br /><span style="font-family: terminal, monaco, monospace;"> Track stuck, not moving for 10 steps</span><br /><span style="font-family: terminal, monaco, monospace;"> in volume -patient_physVol- at point (151.855,11.743,-34.1493) (local point (0.488281,0.0242927,1.47574))</span><br /><span style="font-family: terminal, monaco, monospace;"> direction: (0.981867,0.0434805,-0.184518) (local direction: (0.981867,0.0434805,-0.184518)).</span><br /><span style="font-family: terminal, monaco, monospace;"> Potential geometry or navigation problem !</span><br /><span style="font-family: terminal, monaco, monospace;"> Trying pushing it of 1e-07 mm ...Potential overlap in geometry!</span><br /><br /><span style="font-family: terminal, monaco, monospace;">*** This is just a warning message. ***</span><br /><span style="font-family: terminal, monaco, monospace;">-------- WWWW -------- G4Exception-END --------- WWWW -------</span><br /><br /><span style="font-family: terminal, monaco, monospace;"> 218 152 11.7 -34.1 0.208 0 1e-07 144 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 219 153 11.8 -34.3 0.208 0 0.995 145 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 220 154 11.8 -34.5 0.208 0 0.995 146 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> 221 154 11.8 -34.5 0.208 0 0 146 patient_physVol Transportation</span><br /><span style="font-family: terminal, monaco, monospace;"> </span></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="font-family: terminal, monaco, monospace;"> .</span></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="font-family: terminal, monaco, monospace;"> .</span></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="font-family: terminal, monaco, monospace;"> .</span></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><em>The simulations continues but, and after the 4th run the simulation is aborted with the same message when using primary particles method with primaries over 100,000, which is the following:</em></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="font-family: terminal, monaco, monospace;">terminate called after throwing an instance of 'std::out_of_range'</span><br /><span style="font-family: terminal, monaco, monospace;"> what(): vector::_M_range_check: __n (which is 18446744073709551615) >= this->size() (which is 1)</span><br /><span style="font-family: terminal, monaco, monospace;">Aborted (core dumped)</span></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><span style="font-family: terminal, monaco, monospace;"></span><br /> <br /> <br /> <span class="sig">-- <br /> Gustavo COSTA<br /> <br /> Doctorant<br /> Centre de Recherches en Cancérologie de Toulouse<br /> UMR 1037 INSERM/UPS<br /> Team 15: Multi-resolution dosimetry for radiotherapy optimization</span></div>
</body></html>