<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> Hello Adam,<o:p></o:p> <o:p> </o:p> Thank you for raising this point.<o:p></o:p> We should have a look in the code – I put this issue in my todo list (which is too big already J) – so I encourage you to investigate the code on your side! You could create a bug report on the github and work on a separate branch to propose a bug fixing. We could integrate your corrections in the next release after validation.<o:p></o:p> Information on how to access github, etc. shall be available in the signature below.<o:p></o:p> Cheers,<o:p></o:p> Lo�c<o:p></o:p> <o:p> </o:p> <img width="150" height="202" id="Picture_x0020_1" src="cid:image001.jpg@01D29F3D.DBEB5460" alt="Image:Uncle_Sam_pointing_finger_small.jpg"><img width="150" height="231" id="Picture_x0020_2" src="cid:image002.jpg@01D29F3D.DBEB5460" alt="Image:We-Need-You1-324x500.jpg"><img width="150" height="140" id="Picture_x0020_3" src="cid:image003.jpg@01D29F3D.DBEB5460" alt="Image:superdupont-we-need-you.jpg"><img width="150" height="190" id="Picture_x0020_4" src="cid:image004.jpg@01D29F3D.DBEB5460" alt="Image:gsam_want_gnu_small.jpg"><o:p></o:p> <o:p> </o:p> GATE is a research community, please contribute!<o:p></o:p> <o:p> </o:p> You just started? You found some errors in the examples and the documentation?<o:p></o:p> <![if !supportLists]>� <![endif]> You can correct the <a href="http://wiki.opengatecollaboration.org/index.php/Main_Page"> documentation</a> on the wiki web site<o:p></o:p> <![if !supportLists]>� <![endif]> You can share your experience on the user <a href="http://www.opengatecollaboration.org/mailinglist">mailing-list</a><o:p></o:p> <o:p> </o:p> You have a few months of experience or more?<o:p></o:p> <![if !supportLists]>� <![endif]> You can correct or even propose new <a href="http://www.opengatecollaboration.org/Examples">examples</a> <o:p></o:p> <![if !supportLists]>� <![endif]> You can propose a <a href="http://wiki.opengatecollaboration.org/index.php/GateActor"> new gate actor, it is as easy as a plug-in!</a><o:p></o:p> <o:p></o:p> You are now an official Gate addict and you need more?<o:p></o:p> <![if !supportLists]>� <![endif]> You can participate in Gate C++ source code development: debugging, propose new classes, etc.<o:p></o:p> <![if !supportLists]>� <![endif]>For new developments, <a href="http://www.opengatecollaboration.org/Git">use git</a> and contact the <a href="http://www.opengatecollaboration.org/mailinglist"> gate-devel-mailing-list</a> to be guided.<o:p></o:p> <o:p> </o:p> Thanks for your contribution, the OpenGate collaboration!<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"> From: Gate-users [mailto:gate-users-bounces@lists.opengatecollaboration.org] On Behalf Of Aitkenhead Adam (RBV) NHS Christie Tr Sent: Thursday, March 16, 2017 5:26 PM To: gate-users@lists.opengatecollaboration.org Subject: [Gate-users] Problem using the HounsfieldMaterialGenerator while applying custom ionisation potentials<o:p></o:p> </div> </div> <o:p> </o:p> Hi,<o:p></o:p> <o:p> </o:p> I'm having difficulty applying custom ionisation potentials while using the HounsfieldMaterialGenerator in Gate 7.2. The underlying problem is that custom ionisation potentials for elements don't seem to be inherited by subsequent materials.<o:p></o:p> <o:p> </o:p> For example: In Gate 7.2 the default ionisation potential for oxygen is 95 eV. If I would prefer to use the potential (106 eV) listed in ICRU report 49, then I can set this as follows:<o:p></o:p> <o:p> </o:p> /gate/geometry/setIonisationPotential Oxygen 106 eV<o:p></o:p> <o:p> </o:p> The problem is that this new ionisation potential value is not used by Gate when it uses the Bragg additivity rule to calculate the ionisation potential for any materials containing oxygen. For example, the ionisation potential of water remains at 68.998 eV, instead of increasing to 75.3 eV.<o:p></o:p> <o:p> </o:p> This isn't a problem for simple geometric simulations where a small number of materials are used, as the ionisation potentials for each material can be individually specified. E.g.:<o:p></o:p> <o:p> </o:p> /gate/geometry/setIonisationPotential Water 75.3 eV<o:p></o:p> <o:p> </o:p> However, it is a problem when a simulation uses a CT image and materials are generated using the HounsfieldMaterialGenerator. In this case, ionisation potentials are calculated based on the default element ionisation potentials - regardless of any custom element ionisation potentials that have been defined.<o:p></o:p> <o:p> </o:p> Does anyone have any suggestions - either for something I might have misunderstood, or for a workaround to allow custom ionisation potentials to be applied while using the HounsfieldMaterialGenerator?<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Adam<o:p></o:p> <o:p> </o:p> <a href="mailto:adam.aitkenhead@christie.nhs.uk">adam.aitkenhead@christie.nhs.uk</a><o:p></o:p> Christie Medical Physics & Engineering<o:p></o:p> The Christie NHS Foundation Trust Manchester, UK <o:p></o:p> <o:p> </o:p> This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you have received this e-mail in error you should not disseminate, distribute or copy it. Please notify the sender immediately and delete this e-mail from your system.<o:p></o:p> </div> <div class="WordSection1"> <o:p></o:p>Disclaimer: Please notice our E-Mail Disclaimer <a href="http://www.medaustron.at/email-disclaimer/">http://www.medaustron.at/email-disclaimer/</a><o:p></o:p><o:p> </o:p> </div> </body> </html>