Message: Importance store after geometry update Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Importance store after geometry update 

Forum: Biasing and Scoring
Date: 28 Sep, 2017
From: Michael Carson <Michael Carson>

Following example B01 I create an importance store in DetectorConstruction using AddImportanceGeometryCell() for different physical volumes. The code runs without issue. After changing a physical volume dimension (during run time via a messenger class) and a ReinitializeGeometry(), the code seg faults with:

#0  0x00002aaaaed66721 in operator<<(std::ostream&, G4GeometryCell const&) () from ~/geant4/geant4.10.01.p01-install/lib/
#1  0x00002aaaaed66614 in operator<<(std::ostream&, std::map<G4GeometryCell, double, G4GeometryCellComp, std::allocator<std::pair<G4GeometryCell const, double> > > const&) ()
   from ~/geant4/geant4.10.01.p01-install/lib/
#2  0x00002aaaaed67938 in G4IStore::GetImportance(G4GeometryCell const&) const () from ~/geant4/geant4.10.01.p01-install/lib/

It looks like the cell importance can't be determined.

Do I need to re-build the importance store after a geometry update? If so, how?

 Add Message Add Message
to: "Importance store after geometry update"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews