Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Warnings volume deletion at end of simulation run #1191

Closed
benedikt-voelkel opened this issue Jun 11, 2018 · 2 comments
Closed

Warnings volume deletion at end of simulation run #1191

benedikt-voelkel opened this issue Jun 11, 2018 · 2 comments

Comments

@benedikt-voelkel
Copy link
Contributor

benedikt-voelkel commented Jun 11, 2018 •
edited
Loading

After the simulation run there are now 4 new warnings in case of TGeant4

WARNING - Attempt to delete the physical volume store while geometry closed !
WARNING - Attempt to delete the logical volume store while geometry closed !
WARNING - Attempt to delete the solid store while geometry closed !
WARNING - Attempt to delete the region store while geometry closed !

Does this have any impact on the simulation?
This seems to be related to the method G4RunManager::ReinitializeGeometry cleaning these stores in exactly the same order the warnings appear in.
@sawenzel
Copy link
Collaborator

Can you post the warnings here?

@benedikt-voelkel
Copy link
Contributor Author

Warnings do not appear anymore.

mikesas pushed a commit to mikesas/AliceO2 that referenced this issue Dec 13, 2022
@aimeric-landou
lambdakzeroanalysis(MC) - fix efficiencies, add collision Z cut where…
88114f3 
… missing, some cleanup (AliceO2Group#1191)

* lambdakzeroanalysisMC - fix mcparticle counter: correct efficiency

* lambdakzeroanalysis(MC) - clean event selection and add posZ cut where forgotten

* lambdakzeroanalysis(MC) - add process_switch checks and small fixes

* lambdakzeroanalysis(MC) - clang fixes

Co-authored-by: alandou <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sawenzel @benedikt-voelkel