Open ojalaj opened 7 years ago
I can reproduce this in tutor7pp, even by moving the z=11 plane to 12 (to avoid overlap with the tip of the sphere).
This can also be reproduced when electron transport is turned off. As far as I can tell, this will require actual debugging and following the particle steps through the geometry. : /
@mchamberland, thanks for debugging! Do you have non-IAEA phsp files to test if this happens also with them? I apologize @blakewalters that once again we are producing IAEA phsp source related issues :)
Unfortunately, I don't since I only ever use IAEA phsp files.
I think the IAEA phase space source is a red herring. I've followed a photon through the CD geometry and this seems like just another edge case that the CD geometry howfar logic fails to properly account for. Thankfully, the geometry is very simple to follow so we should be able to find a solution for this...
(But I'm actually on vacation, so I won't have much time to spend on this in the next 2 weeks...)
As far as I can tell, the howfar of CD geometry is okay and working as intended. It's the floating point errors that end up being relatively large compared to other situations I've encountered before: ~1e-5. So, using a larger boundary tolerance than usual (say, 1e-4) seems to fix the issue (at least, up to 1e8 histories).
I tested this geometry (actually, a simplified version of it) with both the IAEA phase space source you're using and an EGS format version of it, and both produce the CD geometry error (albeit fewer errors in the case of the EGS format phase space). And while this may be an ideal situation in which to (further) firm up the roundoff error checking in EGS_CDGeometry, in the meantime, I would follow the suggestion of @mchamberland and increase the boundary tolerance (using the "boundary tolerance =" input for your CD geometry).
Thank you @mchamberland and @blakewalters for further debugging. As you may guess, this is just an oversimplified example of the geometry in which we originally encountered the error, but I'll let my PhD student to know this workaround and for now, let's hope it works for our case.
Does anyone know if this issue has been resolved through "recent" commit dealing with boundary tolerance and CD geometry errors since 2017? For example: #383, #388, fd008c25c2a33ac86fdca2946dabbca8edc86b8a.
Referencing to https://plus.google.com/108037604399060498077/posts/ZY3qZ9imN2B from my PhD student, the example below works with parallel source, but not with IAEA phsp sources. Do we have a bug here or a user error from our side?