-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flsimulate warnings when using new gveto and wall vertex generators #193
Comments
I think this is almost certain to be an issue with overlapping volumes - the PMTs are defined in terms of a with polycone data taken from: https://github.com/SuperNEMO-DBD/Falaise/tree/develop/resources/geometry/PMT The first thing to do would be to check if there are any obvious typos or bad data in those. The underlying Geant4 definition of polygon is here in case that's useful. There's a guide on how to check overlaps in Geant4 here: but that's mostly runnable through UI commands. The simulation does have the facility to run like this, but has never been enabled. I'll have a look at how best to add that in so we can see if those facilities can help. NB: we're still running a pretty old Geant4, latest Bayeux (and upcoming tag) provide provisional support for 10.5, so might need those to get "best" overlap checking. I've assigned to us for now, but add any others you want! |
bxgeomtools_inspector probably could be used to track overlap.... |
Position : (781.558,-646.909,-520.447) is related to the back of a 8 inch PMT glass. (base side) If overlap exist that's between 8 inch PMT shape and its envelop.... My point of view, that's not an issue... to confirm with @fmauger |
Your feeling ? |
I have no immediate good idea right now but I believe we should search for a bad positioning |
Discussed in SI meeting this morning - will postpone until after next release, which should be in the next couple of weeks. We'll then revisit and find people to look at this in detail. |
In flsimulate using the new vertex generators detailed in pull request 182 I got the following warnings:
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomNav1002
issued by : G4Navigator::ComputeStep()
Track stuck or not moving.
Track stuck, not moving for 10 steps
in volume -calo.PMT_HAMAMATSU_R5912.model.log_PV- at point (781.62,1683.88,258.336)
direction: (0.894453,-0.186827,0.406263).
Potential geometry or navigation problem !
Trying pushing it of 1e-07 mm ...Potential overlap in geometry!
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomNav1002
issued by : G4Navigator::ComputeStep()
Track stuck or not moving.
Track stuck, not moving for 10 steps
in volume -calo.PMT_HAMAMATSU_R5912.model.log_PV- at point (781.558,-646.909,-520.447)
direction: (0.514698,-0.193035,0.835358).
Potential geometry or navigation problem !
Trying pushing it of 1e-07 mm ...Potential overlap in geometry!
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------`
I believe this is what @emchauve was asking about. This did not cause a crash however.
The text was updated successfully, but these errors were encountered: