Nuclearizer errors with voxel or simple detector in massmodel-em

[parshadkp]

Some hits have no corresponding volume. All of these happen on the rounded intersection areas (see image below). I am using my branch of nuclearizer with GR and Shield veto changes (https://github.com/parshadkp/nuclearizer_parshad_fork/tree/develop/em-dee-triggers) with the updated mass model single detector in (https://github.com/parshadkp/massmodel-cosi-em/tree/single-det-voxel3D) or (https://github.com/parshadkp/massmodel-cosi-em/tree/single-det-simple).

I am using the .source file here (Cs137_singleDetBGO-em-Voxel3D.txt). Github did not let me upload .source files so note that you'll have to change this to .source.

I get <10 errors in more than 100,000 hits, so this may not be a very important issue. Some pictures of the error hits are also attached. Reddish dots, first image: bottom right in top left detector, second image: top right in top left detector.

Errors are like this:

Warning:
No detector volume could be found for the hit at position -9.7443299999999997141, 1.0029300000000000992, 3.5640999999999998238
The deepest volume is: Cryostat_Interior
Possible reasons are:
* The hit is just (+-1e-06 cm) outside the border of the volume:
-> Make sure you have stored your simulation file with enough digits
(cosima keyword "StoreScientific") so that the volume borders can be separated
-> Make sure your search tolerance given in the geometry file (geomega keyword
"DetectorSearchTolerance") is not too small
* The current and the simulation geometry are not identical
* There are overlaps in your geometry:
-> No simple overlaps found, but you might do a full overlap check anyway...
Searching for a detector within 1e-06 cm around the given position...
--> No suitable volume found!

This hit at (-9.74433, 1.00293, 3.5641) has no corresponding detector volume!
--> It will not show up in the later analysis!