<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dear Ida,<br>
<br>
I write from the perspective of a Geant4 developer - but the
observations should apply equally to any GATE application.<br>
<br>
- It is unexpected that using visualisation should change the result
of any geometry check.<br>
- The results of the recursive_test should be reasonably accurate;
that is at the limit of high statistics you should get a correct
answer, and using default number of trial lines you should get an
answer which does not vary from run to run.<br>
<br>
There is another method to check a Geant4 geometry, which involves
checking every volume which is positioned to see that it does not
overlap with a volume at the same level or protrude from its parent
volume. I am not certain whether this capability is exploited already
in Gate, in all or recent releases. <br>
<br>
Best regards,<br>
John A.<br>
<br>
Ida Häggström wrote:
<blockquote
cite="mid:ff2bc2ff0910020348x6edb38f9v72d2983b5c153216@mail.gmail.com"
type="cite">
<div class="gmail_quote">Dear all, <br>
<br>
I've recently posted some questions regarding segmentation violations,
geometry test errors and voxelized phantoms. I've experienced a lot of
problems with getting a proper run from GATE, and I've spent many hours
(piuh!) troubleshooting! =) Anyway, I discovered something that I'm not
sure is a bug in GATE or if it's my code that is erroneous...<br>
<br>
I run a geometry check as I initialize my run, to check that there are
no geometry overlaps etc since I believe this can cause segmentation
violations which aborts the entire run. <br>
<span style="color: rgb(51, 51, 255);">-------------<br>
/run/initialize</span><br style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/geometry/test/recursive_test</span><br>
-------------<br>
I usually keep the visualization disabled since this saves a lot of
time for longer runs:<br>
<span style="color: rgb(51, 51, 255);">-------------<br>
/vis/disable</span><br>
-------------<br>
I noticed that I get errors regarding my voxelized phantom
(overshooting daughter volume) which I don't think should be there
(emphasis on THINK!). When I turn the visualization ON however, the
errors disappear and I only get results like:<br>
----------<br>
<span style="color: rgb(51, 51, 255);">GeomTest: no daughter volume
extending outside mother detected.</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">GeomTest: no overlapping
daughters detected.</span><br>
---------<br>
from the geometry check. My visualization macro is very simple:<br>
----------<br>
<span style="color: rgb(51, 51, 255);"># Visualization.mac</span><br>
<span style="color: rgb(51, 51, 255);">/vis/open OGLSX</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/vis/viewer/reset</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/vis/drawView 45 45</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/vis/viewer/zoom 2</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/vis/viewer/set/style surface</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/vis/drawVolume</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/tracking/storeTrajectory 1</span><br
style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/vis/scene/endOfEventAction
accumulate</span><br style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/vis/viewer/update</span><br>
------------<br>
and I don't think the visualization should have anything to do with the
geometry setup at all?(!) Can this be a GATE bug? Note that the only
thing I change in my main macro is changing<span
style="color: rgb(0, 0, 0);"> </span><span
style="color: rgb(51, 51, 255);"><span style="color: rgb(0, 0, 0);">"/vis/disable"
to</span><br>
----------<br>
#/vis/disable</span><br style="color: rgb(51, 51, 255);">
<span style="color: rgb(51, 51, 255);">/control/execute
Visualization.mac</span><br>
----------<br>
and I get no errors. I've also tried to disable all visualization of
the phantom (in the range.dat file, setting visualization to "false")
but this has no affect on the run results (no matter if I have the main
visualization on or off).<br>
<br>
I have attached my main macro, GATE run output log, voxelized phantom
macro with related .dat files and a screenshot of my setup with camera
and phantom.<br>
<br>
Please, if anyone has any idea what could cause these problems, please
let me know! I'm really running out of ideas... =) It's not a good
option to always have to run with visualization on for longer runs...<br>
Thanks!<br>
<font color="#888888">Ida<br>
</font></div>
<br>
<br>
<hr size="4" width="90%"><br>
<center><img src="cid:part1.08050303.00050405@cern.ch"></center>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Gate-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gate-users@lists.healthgrid.org">Gate-users@lists.healthgrid.org</a>
<a class="moz-txt-link-freetext" href="http://lists.healthgrid.org/mailman/listinfo/gate-users">http://lists.healthgrid.org/mailman/listinfo/gate-users</a>
</pre>
</blockquote>
</body>
</html>