1. Implementation of Simulation
Holger Kluck (HEPHY Vienna)
CRESST / EDELWEISS / EURECA Software Workshop
22 May 2014

2. The purpose of this talk is to …
give a short overview of the existing CRESST simulation code.
present a very preliminary roadmap.
ask what to we want from a simulation.
 May in general also interesting for EURECA.
22 May 2014
Holger Kluck (HEPHY Vienna)

3. Existing CRESST simulation code
Improved CRESST Simulation (ImpCRESST) Geant4 9.4p02 by St. Scholl
14k lines of code, some difficulties:
22 May 2014
Holger Kluck (HEPHY Vienna)

4. Existing CRESST simulation code
Improved CRESST Simulation (ImpCRESST) Geant4 9.4p02 by St. Scholl
14k lines of code, some difficulties:
Non-standard, non-OO user interface
Non-standard, non-OO binary data format
22 May 2014
Holger Kluck (HEPHY Vienna)

5. Existing CRESST simulation code
Improved CRESST Simulation (ImpCRESST) Geant4 9.4p02 by St. Scholl
14k lines of code, some difficulties:
Non-standard, non-OO user interface
Non-standard, non-OO binary data format
Complete (?) geometry
Various particle sources implemented
Improved physics for low-energy neutrons
22 May 2014
Holger Kluck (HEPHY Vienna)

6. Existing CRESST simulation code
Improved CRESST Simulation (ImpCRESST) Geant4 9.4p02 by St. Scholl
14k lines of code, some difficulties:
Non-standard, non-OO user interface
Non-standard, non-OO binary data format
Complete (?) geometry
Various particle sources implemented
Improved physics for low-energy neutrons
 Use it as starting point for ongoing development
22 May 2014
Holger Kluck (HEPHY Vienna)

7. Holger Kluck (HEPHY Vienna)
Preliminary roadmap
Goal: Improve code design, so more people (e.g. future master students) can do the actual simulations (e.g. detector response).
22 May 2014
Holger Kluck (HEPHY Vienna)

8. Holger Kluck (HEPHY Vienna)
Preliminary roadmap
Goal: Improve code design, so more people (e.g. future master students) can do the actual simulations (e.g. detector response).
Code clean-up
Migration to Geant4 10.0p01
Create specification sheet
Minimize dependencies
Improved data format
Check/update of geometry and sources
Do actual simulation
22 May 2014
Holger Kluck (HEPHY Vienna)

9. Specification sheet needed
Most general simulation design would be nice, but need also lots of man power. Need actual use case:
Who should finally run the simulation code?
How long should be the lifetime of the code?
Can we agree on a fixed backend for the data I/O, e.g. ROOT?
Etc.
 Determine the design of the UI and the level of abstractness.
22 May 2014
Holger Kluck (HEPHY Vienna)

10. Thoughts about minimizing dependencies
Use standard Geant4 messenger classes to encapsulate all UI commands specific for a given class (and to improve batch capability).
Split simulation in 4 packages:
St. Scholls improved physics list
Geometry of the set-up (if needed with dynamical detector placement)
Geometry and specification of the actual detectors  Can be shared with EURECA simulation
Data I/O
22 May 2014
Holger Kluck (HEPHY Vienna)

11. Thoughts about data I/O
Use two levels: Raw simulation data and processed data by a detector response model:  Create several data sets with different detector response parameter but need only one simulation run.
Use a ROOT based data format, ideally close to the one used for experimental data:  Use the same analysis tools.
Document also state of the simulation run, e.g. code version, used parameter, random seeds, etc.  Reproduce the data if needed.
22 May 2014
Holger Kluck (HEPHY Vienna)

12. What simulations are needed?
Detector response model
Including light propagation?
Developing phonon propagation?
Background
from rock
from muons
from U/Th, (α,n) …
22 May 2014
Holger Kluck (HEPHY Vienna)

13. Holger Kluck (HEPHY Vienna)
Outlook
Compile a more detailed draft of the roadmap/specification sheet, including your input and suggestions.
Continuing coding!
Thank you!
22 May 2014
Holger Kluck (HEPHY Vienna)