<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-IE link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi Simon,<br><br></p><p class=MsoNormal>On my side the fix is working as intended, I’ll mention it the GitHub issue!<br>I compared results for primary and secondary images produced with an .xml and an equivalent .placements file. Results are consistent and I can share them if you deem it appropriate.<br><br></p><p class=MsoNormal>Thanks for the help,<br>Gabriele</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>Da: </b><a href="mailto:simon.rit@creatis.insa-lyon.fr">Simon Rit</a><br><b>Inviato: </b>Tuesday 15 March 2022 23:36<br><b>A: </b><a href="mailto:gabriele.belotti.bergamo@gmail.com">Gabriele Belotti</a><br><b>Cc: </b><a href="mailto:gate-users@lists.opengatecollaboration.org">gate-users</a><br><b>Oggetto: </b>Re: [Gate-users] [BUG] FFDA - Displaced detector geometry and primary projections</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hi Gabriele,</p></div><div><p class=MsoNormal>I have managed to reproduce the error and I think I have a fix</p></div><div><p class=MsoNormal><a href="https://github.com/OpenGATE/Gate/pull/497">https://github.com/OpenGATE/Gate/pull/497</a></p></div><div><p class=MsoNormal>I probably never detected this because I normally don't use a source offset and a detector offset together... Can you test the fix and let me know if it works for you?</p></div><div><p class=MsoNormal>Thanks,</p></div><div><p class=MsoNormal>Simon</p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Mar 8, 2022 at 11:37 AM Simon Rit <<a href="mailto:simon.rit@creatis.insa-lyon.fr">simon.rit@creatis.insa-lyon.fr</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><div><p class=MsoNormal>Hi Gabriele,</p></div><div><p class=MsoNormal>If something is set to 0, it is probably because your collimated source is too small. Try adjusting the source size</p></div><div><p class=MsoNormal><a href="https://github.com/OpenGATE/GateContrib/blob/master/imaging/CT/fixedForcedDetectionCT/mac/fixedForcedDetectionCT.mac#L59-L73">https://github.com/OpenGATE/GateContrib/blob/master/imaging/CT/fixedForcedDetectionCT/mac/fixedForcedDetectionCT.mac#L59-L73</a></p></div><div><p class=MsoNormal>Simon</p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Mar 8, 2022 at 10:41 AM Gabriele Belotti <<a href="mailto:gabriele.belotti.bergamo@gmail.com">gabriele.belotti.bergamo@gmail.com</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><div><p class=MsoNormal>Hello everyone,<br><br>I'm posting this to inquire on a possible bug in GATE.<br>BACKGROUND:<br>I'm conducting some fixed forced detection simulations, with a voxelized phantom and a moving gantry described by an RTK .XML geometry file.<br>The specific condition in my geometry file is that I have source and detector offsets.<br>My simulation saves primary as well as attenuation images.<br>BUG(?):<br>When inspecting the primary images I have a vertical band of values that is consistently put to 0. The position of this band is on the same side of the detector offset (i.e. toward the center of the phantom being projected). At the same time, the attenuation images have no such issue and represent the complete projection consistently.<br><br>I tried changing phantom and the issue was reproduced in the same way. While if I changed the RTK geometry to one with no offsets I get correct primary and attenuation images. I will try to find a culprit with further tests but I wanted to share this with you.<br><br>PS: Issue reproduced in vGATE (GATE 9.1 and GEANT4 10.7) and on a cluster (with GATE master and GEANT4 11.0)<br><br>Gabriele Belotti</p><div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote></div></blockquote></div><p class=MsoNormal style='margin-left:9.6pt'>_______________________________________________<br>Gate-users mailing list<br><a href="mailto:Gate-users@lists.opengatecollaboration.org">Gate-users@lists.opengatecollaboration.org</a><br><a href="http://lists.opengatecollaboration.org/mailman/listinfo/gate-users">http://lists.opengatecollaboration.org/mailman/listinfo/gate-users</a></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>