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.

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

GeoHandler: store shapes in deterministic order #1277

Merged
merged 2 commits into from
Jun 6, 2024

Conversation

andresailer
Copy link
Member

@andresailer andresailer commented May 30, 2024

From #1271, I am not sure which of these sets causes the problem, so this is an attempt to get the ball rolling.

BEGINRELEASENOTES

ENDRELEASENOTES

Copy link

github-actions bot commented May 30, 2024

Test Results

   14 files     14 suites   7h 5m 1s ⏱️
  363 tests   363 ✅ 0 💤 0 ❌
2 496 runs  2 496 ✅ 0 💤 0 ❌

Results for commit d5238ce.

♻️ This comment has been updated with latest results.

@andresailer
Copy link
Member Author

@MarkusFrankATcernch With this I get identical GDML files for SiD.xml out of Geant4.

The main change is inside m_data from set -> vector.
The collect function actually did the "scan" over the geometry, the other sets in GeometryInfo seem not important.

@MarkusFrankATcernch
Copy link
Contributor

Great. Should we ask Witek to test this branch first ?

@andresailer
Copy link
Member Author

It is apparently too hard to build the LHCb stack to test this. But the GDML comparison with SiD.xml hopefully triggered the same issue.
So merging now, tagging tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Non reproducible order of daughter volumes in Geant4 geometry.
2 participants