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

Understand how input and output work in Geant4 #8

Open
Tracked by #9
andrewgait opened this issue May 15, 2024 · 2 comments
Open
Tracked by #9

Understand how input and output work in Geant4 #8

andrewgait opened this issue May 15, 2024 · 2 comments
Assignees

Comments

@andrewgait
Copy link
Contributor

Following running an example in Geant 4 #7, understand how input and output work.

@andrewgait
Copy link
Contributor Author

Some work was done towards this goal in the first sprint of the project, but more work is required to understand how the links between Geant4 and Mitsuba3 work.

@andrewgait
Copy link
Contributor Author

Input in Geant4 is done programmatically by specifying various (predefined) objects in code in a DetectorConstruction class as defined in eg. basic example 1 at https://geant4-userdoc.web.cern.ch/Doxygen/examples_doc/html/ExampleB1.html.

Output from Geant4 in these basic examples is what you see in the visualiser once the run has been successful. For the purposes of previous work in the Manchester group, the Rich1.gdml file is effectively an output file of what can be seen in the visualiser when setting up a RICH1 detector. More work may be required in the future to understand the code that created this GDML file.

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

No branches or pull requests

1 participant