Export / import Geant4 XS tables, volume, material, and element information #55
Conversation
|
Can one of the admins verify this patch? |
|
@stognini Hey, I'm seeing a few "warnings-as-errors" on emmet: basically that |
Geant-exporter app now exports material and volume information using the GeantMaterialTable class. RootImporter loads data from the ROOT file into memory. The ImportMaterialTable class maps volume ids with their respective material ids, as well as providing methods to retrieve ImportMaterial and ImportVolume data. The material id allows finding the XS table of said material stored in ImportPhysicsTable objects.
sethrj
force-pushed
the
g4importer-tables
branch
from
05ec7fb
to
42ff00e
Compare
Damn, ok. I can fix them if you prefer.
I could not fix a compiler problem that appeared with that flag, so I disabled it until I could fix it. I'll try to get that running correctly (and compile things on emmet for the time being) to avoid future missing warnings. |
|
No problem, already done (and I squashed a lot of the work-in-progress-y commits to a very few). I'd be curious if you can reproduce the compiler problem; that small warning was the only thing I saw on my build. |
sethrj
added
io
external
Add functionality to geant-exporter app to export XS tables, material, element, and volume information into a root file.
Add capability for Celeritas to import data from the root file, as well as retrieve volume, material, element, and XS table information as needed.
The import tool will run once and the imported data will be moved into future host/device classes, similar to the current ParticleParams.