GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Bugs, Fixes, Releases » Geometry Problems
Re: Geometry Problems [message #19235 is a reply to message #19234] Wed, 20 April 2016 14:08 Go to previous messageGo to previous message
StefanoSpataro is currently offline  StefanoSpataro
Messages: 2736
Registered: June 2005
Location: Torino
first-grade participant

From: *to.infn.it
StefanoSpataro wrote on 14 September 2015 16:42

Dear all,
after a long delay I put the QA macros inside macro/qa/lmd. I reduced the number of events to 1000 since it is too slow and in some computer it took more than 6 minutes for 2000.
In reality, I noticed that sometimes the sim macro is crashing and I have not understood why. In particular in my MAC I was not able to run the macros, it crash at event 0. When I am able to run, there are several geant4 errors from the geometry:

-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomNav1002
issued by : G4PropagatorInField::ComputeStep()
Particle is stuck; it will be killed.
Zero progress for 51 attempted steps.
Proposed Step is 1.99896e-05 but Step Taken is 1.99896e-05
in volume lmd_vol_cvd_disc
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------


-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomNav1002
issued by : G4PropagatorInField::ComputeStep()
Particle is stuck; it will be killed.
Zero progress for 51 attempted steps.
Proposed Step is 1.74027e-05 but Step Taken is 1.74027e-05
in volume lmd_vol_vac
*** This is just a warning message. ***

Then maybe the geometry has internal problems. Doing a CheckFullGeometry I found the following:

====================================================================
STAGE 2: Global overlap/extrusion checking within 10 microns
====================================================================
Info in <TGeoNodeMatrix::CheckOverlaps>: Checking overlaps for cave and daughters within 0.001
Warning in <TGeoChecker::CheckOverlaps>: Volume lmd_vol_ref_sys with 2 daughters but not voxelized
Check overlaps: [==========] 1589 [100.00 %]
Info in <TGeoNodeMatrix::CheckOverlaps>: Number of illegal overlaps/extrusions : 12

and

====================================================================
STAGE 3: Propagating 1000000 tracks starting from vertex
and conting number of boundary crossings...
====================================================================
Error in trying to cross boundary of SupportCylinderov831_2 00:00:00
Error in trying to cross boundary of SupportCylinderov831_2 00:00:00
Error in trying to cross boundary of SupportCylinderov831_2 00:00:00
Error in trying to cross boundary of SupportCylinderov831_1 00:00:00
Error in trying to cross boundary of SupportCylinderov831_2 00:00:00
Error in trying to cross boundary of SupportCylinderov831_1 00:00:01
Error in trying to cross boundary of SupportCylinderov831_1 00:00:01
Error in trying to cross boundary of SupportCylinderov831_2

...

I don't know if you have ever seen such problems.

Moreover, I noticed that the reco macro in my Mac is failing, since it seems the trafo_matrices_lmd.dat path is hardcoded, and if you change the path of the macro then you have the crash. If it has to be used in the common framework this should become more general, i.e. parameters should be loaded inside some ParameterClass by the standard Ascii file.

To summarize, the lmd qa macros are on the dashboard, but they can fail and the output is not well stable.

Regards

Stefano
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [FIXED] Compilation "error" in pid/rich
Next Topic: New (almost) version of SciTil geometry and real digitization
Goto Forum:
  


Current Time: Fri Apr 19 03:28:32 CEST 2024

Total time taken to generate the page: 0.01038 seconds