A introduction Pablo Cirrone INFNLNS 2 GEAN 4

A introduction Pablo Cirrone INFN-LNS 2° GEAN 4 International School and ROOT analisys concepts

Where you can find this material? n n Antonello Maddalena, Pablo Cirrone, Giuliana Milluzzo, Luciano Pandola, Francesco Romano, We (as Geant 4 Collaboration and as other Geant 4 Members) regularly offer tutorials and schools - see Official Geant 4 pages The official Geant 4 web pages www. cern. ch/geant 4 The Italian Geant 4 group: http: //geant 4. lngs. infn. it/

The Monte Carlo method

The Monte Carlo (MC) method: brief history

The Monte Carlo method: a definition It is a mathematical approach using a sequence of random numbers to solve a problem

The Monte Carlo method

The MC method in Physics

The Monte Carlo method n n Particles are tracked one-by-one, step-by-step and, after a reasonable number, the correct information can be extracted MC is very time consuming but n n . . . sometime necessary and. . . with many advantages

MC or analytic approach? Mathematical proofs exist demonstrating that MC is the most efficient way of estimate quantity in 3 D when compared to first-order deterministic method Plot from Alex F. Bielajew, 2001

The Buffon experiment: The MC approach for the π estimation The needle will hit the line if the closest distance to a line D is

The Buffon experiment: The MC approach for the π estimation

The Buffon experiment: The Monte Carlo approach for the π estimation

Geant 4 and the Geant 4 Collaboration

Monte Carlo codes on the market n MCNP (neutrons mainly) Geant 4 Penelope (e- and gamma) -GEometry ANd Traking n PETRA (protons) -Geant 4 - a simulation toolkit n EGSnrc (e- and gammas) n PHIT (protons/ions) n FLUKA (any particle) n Nucl. Inst. and Methods Phys. Res. A, 506 250 -303 -Geant 4 developments and applications Transaction on Nuclear Science 53, 270 -278

Facts about n Developed by an International Collaboration n n Written in C++ language n n n Established in 1998 Approximately 100 members, from Europe, US and Japan http: //geant 4. cern. ch Takes advantage from the Object Oriented software technology Open source Typically two releases per year n Major release, minor release, beta release

Basic concept of Geant 4

Toolkit and User Application n Geant 4 is a toolkit (= a collection of tools) n n n Consequences: n n i. e. you cannot “run” it out of the box You must write an application, which uses Geant 4 tools There are no such concepts as “Geant 4 defaults” You must provide the necessary information to configure your simulation You must deliberately choose which Geant 4 tools to use Guidance: many examples are provided n n Basic/Novice Examples: Examples overview of Geant 4 tools Advanced Examples: Examples Geant 4 tools in real-life applications

Basic concepts n What you MUST do: n n Describe your experimental set-up Provide the primary particles input to your simulation Decide which particles and physics models you want to use out of those available in Geant 4 and the precision of your simulation (cuts to produce and track secondary particles) You may also want n n n To interact with Geant 4 kernel to control your simulation To visualise your simulation configuration or results To produce histograms, tuples etc. to be further analysed

Main Geant 4 capabilities n n n Transportation of a particle ‘step-by-step’ taking into account all the possible interactions with materials and fields The transport ends if the particle n is slowed down to zero kinetic energy (and it doesn't have any interaction at rest) n disappears in some interaction n reaches the end of the simulation volume Geant 4 allows the User to access the transportation process and retrieve the results (USER ACTIONS) n at the beginning and end of the transport n at the end of each step in transportation n if a particle reaches a sensitive detector n Others…

News from version 10. 0 n n Released on December 6 th, 2013 Supports multi-thread approach for multi-core machines n Simulation is automatically split on an event-by-event basis n n Unique copy (master) of geometry and physics n n different events are processed by different cores All cores have them as read-only (saves memory) Backwards compatible with the sequential mode n n n The MT programming requires some care Need to avoid conflicts between threads Merge information at the end coming from the cores

Who/why is using Geant 4?

Experiments and MC n n In my knowledge, all experiments have a (more or less detailed) full-scale Monte Carlo simulation Design phase n n Evaluation of background Optimization of setup to maximize scientific yield n n Minimize background, maximize signal efficiency Running/analysis phase n Support of data analysis (e. g. provide efficiency for signal, background, coincidences, tagging, …). n often, Monte Carlo is the only way to convert relative rates (events/day) in absolute yields

Why Geant 4 is a common choice in the market n Open source and object oriented/C++ n n n No black box Freely available on all platforms Can be easily extended and customized by using the existing interfaces n n n New processes, new primary generators, interface to ROOT analysis, … Can handle complex geometries Regular development, updates, bug fixes and validation Good physics, customizable per use-cases End-to-end simulation (all particles, including optical photons)

LHC @ CERN ATLAS n All four big LHC experiments have a Geant 4 simulation n n Benchmark with test-beam data Key role for the Higgs searches M of volumes Physics at the Te. V scale CMS

Space applications n n Satellites (g astrophysics, planetary sciences) Funding from ESA GLAST Typical telescope: Tracker Calorimeter Anticoincidence AGILE

Medical applications n Treatment planning for hadrontherapy and protontherapy systems n Proton-therapy beam line n n n Medical imaging Radiation fields from medical accelerators and devices n n GEANT 4 simulation Goal: deliver dose to the tumor while sparing the healthy tissues Alternative to less-precise (and commercial) TP software n medical_linac gamma-knife brachytherapy

Dosimetry with Geant 4 Radf et # 2 R S 300 adfet /50 G 300 #4 D /3 500/ 50 B u lk D 690 /15 G 690 /15 S 690 /15 Radf Bulk DG 69 0/15 et #1 Diod #3 e DG Space science Radiotherapy 300/ 50 Effects on electronics components

Minimum software requirements • C++ n A basic knowledge is required being Geant 4 a collection of C++ libraries n It is complex but also no C++ experts can use Geant 4 • Object oriented technology (OO) n Very basic knowledge n Expertise needed for the development of complex applications • Unix/Linux n These are the standard OSs for Geant 4 and a basic knowledge is required n Principal shell commands n How to compile a program, How to install from source code

The (conceptual) recipe for a Geant 4 -based application

Interaction with the Geant 4 kernel n Geant 4 design provides tools for a user application n To tell the kernel about your simulation configuration To interact with Geant 4 kernel itself Geant 4 tools for user interaction are base classes n n You create your own concrete class derived from the base classes interface to the Geant 4 kernel handles your own derived classes transparently through their base class interface (polymorphism)

User Classes (<= 9. 6) Action classes Initialisation classes Invoked at the initialization n n G 4 VUser. Detector. Construction G 4 VUser. Physics. List Invoked during the execution loop n n n Classes having name starting with G 4 V are abstract classes (containing purely virtual methods) n n n G 4 VUser. Primary. Generator. Action G 4 User. Run. Action G 4 User. Event. Action G 4 User. Tracking. Action G 4 User. Stepping. Action

User Classes (from 10. 0) Initialisation classes Invoked at the initialization n n G 4 VUser. Detector. Construction G 4 VUser. Physics. List Action classes Invoked during the execution loop G 4 VUser. Action. Initialization n n Global: only one instance of them exists in memory, shared by all threads (readonly). Managed only by the master thread. n n n G 4 VUser. Primary. Generator. Action G 4 User. Run. Action (*) G 4 User. Event. Action G 4 User. Tracking. Action G 4 User. Stepping. Action Local: an instance of each action class exists for each thread. (*) Two Run. Action's allowed: one for master and one for threads

User Classes - 2 Mandatory classes in ANY Geant 4 User Application G 4 VUser. Detector. Construction describe the experimental set-up G 4 VUser. Physics. List select the physics you want to activate G 4 VUser. Primary. Generator. Action generate primary events

Geant 4 concept G 4 Run. Manager VGeometry My. Geom VPhysics My. Physics Geant 4 kernel VPrimary My. Primary Run. Action Given concrete (dummy) implementation. User MAY give an alternative implementation Evt. Action Only virtual interface provided users MUST implement their concrete implementation Step. Action My. Step

Select physics processes n n Geant 4 doesn’t have any default particles or processes Derive your own concrete class from the G 4 VUser. Physics. List abstract base class n n define all necessary particles define all necessary processes and assign them to proper particles define g/d production thresholds (in terms of range) Pure virtual methods of G 4 VUser. Physics. List Construct. Particles() Construct. Processes() Set. Cuts() must be implemented by the user in his/her concrete derived class

Physics Lists n n Geant 4 doesn’t have any default particles or processes Partially true: there is no default, but there a set of "ready-for-use" physics lists released with Geant 4, tailored to different use cases. Mix and match: n n Different sets of hadronic models (depending on the energy scale and modeling of the interactions) Different options for neutron tracking n n Do we need (CPU-intensive) description of thermal neutrons, neutron capture, etc? Different options for EM physics n n Do you need (CPU-intensive) precise description at the lowenergy scale (< 1 Me. V)? E. g. fluorescence, Doppler effects in the Compton scattering, Auger emission, Rayleigh diffusion Only a waste of CPU time for LHC, critical for many lowbackground experiments

Optional user classes - 1 n Five concrete base classes whose virtual member functions the user may override to gain control of the simulation at various stages n n n G 4 User. Run. Action G 4 User. Event. Action G 4 User. Tracking. Action G 4 User. Stepping. Action e. g. actions to be done at the beginning and end of each event Each member function of the base classes has a dummy implementation (not purely virtual) n Empty implementation: does nothing

Optional user classes - 2 n The user may implement the member functions he desires in his/her derived classes n n E. g. one may want to perform some action at each tracking step Objects of user action classes must be registered to G 4 Run. Manager run. Manager-> Set. User. Action(new My. Event. Action. Class);

Methods of user classes - 1 G 4 User. Run. Action - Begin. Of. Run. Action(const G 4 Run*) // book histos - End. Of. Run. Action(const G 4 Run*) //store histos G 4 User. Event. Action -Begin. Of. Event. Action(const G 4 Event*) //initialize event -End. Of. Event. Action (const G 4 Event*) // analyze event G 4 User. Tracking. Action - Pre. User. Tracking. Action(const G 4 Track*) //decide to store/not store a given track -Post. User. Tracking. Action(const G 4 Track*)

Methods of user classes - 2 G 4 User. Stepping. Action - User. Stepping. Action(const G 4 Step*) //kill, suspend, pospone the track, draw the step, … G 4 User. Stacking. Action -Prepare. New. Event() //reset priority control -Classify. New. Track(const G 4 Track*) // Invoked when a new track is registered (e. g. kill, pospone) - New. Stage() // Invoked when the Urgent stack becomes empty (re-classify, abort event)

The main() program - 1 n Geant 4 does not provide the main() n n n Geant 4 is a toolkit! The main() is part of the user application In his/her main(), the user must n n construct G 4 Run. Manager (or his/her own derived class) notify the G 4 Run. Manager mandatory user classes derived from n n G 4 VUser. Detector. Construction G 4 VUser. Physics. List G 4 VUser. Primary. Generator. Action In MT mode, use G 4 MTRun. Manager n n n G 4 VUser. Detector. Construction G 4 VUser. Physics. List G 4 VUser. Action. Initialization (takes care of Primary)

The main() program - 2 n The user may define in his/her main() n n optional user action classes Vis. Manager, (G)UI session The user also has to take care of retrieving and saving the relevant information from the simulation (Geant 4 will not do that by default) Don’t forget to delete the G 4 Run. Manager at the end

An example of (sequential) main() { … // Construct the default run manager G 4 Run. Manager* run. Manager = new G 4 Run. Manager; // Set mandatory user initialization classes My. Detector. Construction* detector = new My. Detector. Construction; run. Manager->Set. User. Initialization(detector); My. Physics. List* physics. List = new My. Physics. List; run. Manager->Set. User. Initialization(my. Physics. List); // Set mandatory user action classes run. Manager->Set. User. Action(new My. Primary. Generator. Action); My. Primary. Generator. Action // Set optional user action classes My. Event. Action* event. Action = new My. Event. Action(); run. Manager->Set. User. Action(event. Action); My. Run. Action* run. Action = new My. Run. Action(); run. Manager->Set. User. Action(run. Action); … }

An example of (MT) main() { … // Construct the default run manager G 4 MTRun. Manager* run. Manager = new G 4 MTRun. Manager; // Set mandatory user initialization classes My. Detector. Construction* detector = new My. Detector. Construction; run. Manager->Set. User. Initialization(detector); My. Physics. List* physics. List = new My. Physics. List; run. Manager->Set. User. Initialization(my. Physics. List); // Set mandatory user action classes run. Manager->Set. User. Action(new My. Action. Initialization); My. Action. Initialization … }

My. Action. Initialization (MT mode) n Register thread-local user actions void My. Action. Initialization: : Build() const { //Set mandatory classes Set. User. Action(new My. Primary. Generator. Action()); () // Set optional user action classes Set. User. Action(new My. Event. Action()); Set. User. Action(new. My. Run. Action()); } n Register Run. Action for the master void My. Action. Initialization: : Build. For. Master() const { // Set optional user action classes Set. User. Action(new. My. Master. Run. Action()); }

Geant 4 concept G 4 Run. Manager VGeometry My. Geom VPhysics My. Physics Geant 4 kernel VPrimary My. Primary Run. Action Given concrete (dummy) implementation. User MAY give an alternative implementation Evt. Action Only virtual interface provided users MUST implement their concrete implementation Step. Action My. Step

Geant 4 concept (MT) G 4 MTRun. Manager VGeometry My. Geom VPhysics My. Physics Geant 4 kernel VAction. In VPrimarry My. Primary Run. Action Evt. Action Step. Action My. Step

Optional: select (G)UI n n In your main(), taking into account your computer environment, instantiate a G 4 UIsession concrete/derived class provided by Geant 4 and invoke its Session. Start() method mysession->Session. Start(); Geant 4 provides: n n n n G 4 UIterminal csh or tcsh like character terminal G 4 GAG Opacs G 4 UIBatch batch job with macro file …

Optional: select visualization n n In your main(), taking into account your computer environment, instantiate a G 4 Vis. Executive and invoke its Initialize() method Geant 4 provides interfaces to various graphics drivers: n n n n DAWN (Fukui renderer) WIRED Ray. Tracer (ray tracing by Geant 4 tracking) Open. GL Open. Inventor VRML X 11 -compliant

General recipe for novice users Experienced users may do much more, but the conceptual process is still the same… n n Design your application… requires some preliminar thinking (what is it supposed to do? ) Create your derived mandatory user classes n n Create optionally your derived user action classes n n My. User. Run. Action, My. User. Event. Action, … Create your main() n n My. Detector. Construction My. Physics. List My. Primary. Generator. Action Instantiate G 4 Run. Manager or your own derived My. Run. Manager Notify the Run. Manager of your mandatory and optional user classes Optionally initialize your favourite User Interface and Visualization That’s all!

Installation tips

Download and installation tips n n n You can download the compiled libraries of Geant 4 but the compilation in your computer is strongly suggested Download the source file from the Geant 4 web site Two ways to proceed: n n Using cmake via terminal Using the GUI version of cmake

cmake Geant 4 installation n n n cmake version greater than 2. 8. 3 Locate the source folder Ex: /home/Username/geant 4 -09 -05 Create the build folder Ex: /home/Username/geant 4 -09 -05 -build Create the install folder Ex: /home/Username/geant 4 -09 -05 -install cmake -DCMAKE_INSTALL_PREFIX=/home/Username/geant 4 -09 -05 -install/ Define and/or activate the additional features/package you require using the same cmake interface n make -j. N n make install

cmake Geant 4 installation

cmake Geant 4 installation options n n If GEANT 4_INSTALL_DATA is ON the additional external data libraries are automatically downloaded (e. g. –DGEANT 4_INSTAL_DATA=ON) If GEANT 4_INSTALL_EXAMPLES is ON Examples are installed If GEANT 4_USE_SYSTEM_CLHEP is ON external CLHEP are searched See documentation for details for the complete variables list and explanation

cmake Geant 4 installation

GUI version of cmake A friendly way to do the same things (on Windows and Mac)

If everything is ok…

Initialization Describe your experimental set -up Activate physics processes appropriate to your experiment

Beam On Generate primary events according to distributions relevant to your experiment

Event loop Generate primary events according to distributions relevant to your experiment