geant4-project

To set up a Geant4 detector simulation, you need a standard project layout with CMakeLists.txt, a main entry point, detector geometry, and action initialization. Generating a compile-ready codebase lets you run beam and target simulations without manually assembling boilerplate code.

For general-purpose Geant4 particle transport, the FTFP_BERT physics list is recommended. You should switch to alternative built-in physics lists based on your specific energy ranges and particle types to ensure accurate physics modeling.

To add ROOT output for energy deposition, implement data collection using RunAction, EventAction, and SteppingAction. This pattern ensures correct per-event aggregation flow, allowing you to record hits and positions accurately for later analysis.

Yes, you can use OpenGL visualization to check detector geometry and particle trajectories in Geant4. By running an init_vis.mac starter macro, you can quickly validate your geometry setup and visualize particle paths during simulation debugging.

Debugging Geant4 detector geometry requires best practices like overlap checking, unit validation, and proper material definitions. Making modular geometry changes and using consistent naming conventions helps identify issues quickly when updating existing simulation projects.

To configure a primary generator action for a neutron beam in Geant4, use the PrimaryGeneratorAction pattern to define the particle type and energy. This setup allows you to simulate specific particles like 10 MeV neutrons striking a target.