Seth R. Johnson

Inputs: - Imported data from Geant4 - Callback functions to generate input functions: physics processes - Options to construct built-in Celeritas actions (e.g. SD callback, calo, diagnostics) - Callback to...

I'd be grateful for input on this discussion from a parallelism standpoint (@amandalund) and Geant4 mechanics standpoint (@drbenmorgan). I'd like to have a structure that is compatible with all use...

I recently updated the documentation to try to better describe [how Geant4 initialization works](https://celeritas-project.github.io/celeritas/user/implementation/geant4-interface.html#running-geant4). The places where we currently use `begin_run` (which takes only the local state and is called...

Also I just learned about `G4Run::Merge`. It looks like it's called only from worker threads as they end, and not from the main thread nor in serial mode, so I'm...

@LSchwiebert This is the issue we have for refactoring the usage of the "stepper", so we can hack it to pieces in the meantime

- **Quantifier**: given particle view (and sometimes params data), return a scalar (or vector? or tuple?) - Volume ID: GeoParams -> VolumeId - Detector ID: VolumeId -> DetectorId - Distance...

@seriksen: can you check the work above? And just to confirm, the PMT hits on the bottom are still due to photon emissions in the top xenon gas layer?

Awesome @seriksen , thanks! Although we now have the PMT coordinates extracted from your `LZDetectorPMTBankCoordinates.hh` into JSON, I'm curious how the numbering system was created? Is it ordered first by...

Thanks @whokion , I've crossed out the last bullet point to reflect the feasibility of doing the sampling on GPU. It sounds like your alternate suggestion is the previous bullet...

If it's simply array data, that's great. After you establish the requirements from the geant4 side let's meet to sketch out an implementation plan. I *definitely* want to take the...