Minimal fetch and use of G4VG for in-memory Geant4<->VecGeom conversion #273
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use FetchContent to get and make available g4vg from current upstream master.
|
Can one of the admins verify this patch? |
agheata
approved these changes
Feb 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed at the last AdePT/Celeritas standup, and for this afternoon's hackathon, this shows the minimal steps for use of celeritas-project/g4vg in AdePT. This is just:
FetchContentto get the code and add it to the buildG4VG.hhpublic header and linking tolibg4vgIt's been tested on a centos9 with gcc11/cuda12 and seems to build and run o.k., but it is trivial!
Also pinging @sethrj for info/double check.