The Virtual MonteCarlo D.Adamova 2, V.Berejnoi 1, R.Brun 1, F.Carminati 1, A.Fassó 1, E.Futo 1, I.Gonzalez 3, I.Hrivnacova 4, A.Morsch 1 1 CERN, Geneva; 2 NPI, Rez; 3 IFCA, Cantabria; 4 IPN, Orsay For the ALICE Collaboration Presented by I. Hrivnacova Conference for Computing in High Energy and Nuclear Physics La Jolla, 27 March 2003

I. HrivnacovaCHEP 2003, La Jolla, 27 March Outline  Interfaces  Available MCs  Examples  Distribution  Future

I. HrivnacovaCHEP 2003, La Jolla, 27 March The VMC Concept  The Virtual MonteCarlo (VMC) has been developed in order to –Run the same user application with all supported transport Monte Carlos –Run different transport Monte Carlo programs without changing the user code and therefore the geometry definition, the detector response simulation, or input and output formats  VMC decouples the dependence of a user code from a concrete MC

I. HrivnacovaCHEP 2003, La Jolla, 27 March VMC Concept User Code VMC Geant4 VMC Particles Hits Geant4 Geant3 Output Fluka VMC Fluka Input Geant3 VMC

I. HrivnacovaCHEP 2003, La Jolla, 27 March Virtual Monte Carlo

I. HrivnacovaCHEP 2003, La Jolla, 27 March Interfaces (1)  TVirtualMC –Interface to the Monte Carlo program –Generalization of Geant3 functions for definition of simulation task Provides methods for definition of geometry and physics setup; for access to tracked particle properties during stepping; for run control –Implementations: TGeant3, TGeant4, TFluka (coming soon) Are provided for the user Methods For Building & Accessing Geometry Methods For Building & Accessing Materials Methods For Setting Physics Methods For Accessing Tracked Particle During Stepping Methods For Run Control Virtual MC

I. HrivnacovaCHEP 2003, La Jolla, 27 March Interfaces (2)  TVirtualMCApplication –Interface to a user application –Defines user actions at each stage of a simulation run –Mandatory –Implementation has to be done by a user ConstructGeometry InitGeometry GeneratePrimaries BeginEvent BeginPrimary PreTrack Stepping PostTrack FinishPrimary FinishEvent Virtual MC Application

I. HrivnacovaCHEP 2003, La Jolla, 27 March Interfaces (3)  TVirtualMCStack –Interface to a user defined particles stack –Mandatory –User can use the concrete stack classes provided in the examples or implement their own stack class  TVirtualMCDecayer –Interface to an external decayer –Eg. Pythia6 –Optional

I. HrivnacovaCHEP 2003, La Jolla, 27 March ConstructGeometry InitGeometry GeneratePrimaries BeginEvent BeginPrimary PreTrack Stepping PostTrack FinishPrimary FinishEvent User MC Application void MyMCApplication::Construct Geometry() { Double_t trackerTube[3]; trackerTube[0] = 0.; trackerTube[1] = 60.; trackerTube[2] = 50.; gMC->Gsvolu("TRTU", "TUBE", fImedAl, trackerTube, 3); Double_t posX = -100.; Double_t posY = 0.; Double_t posZ = 0.; gMC->Gspos("TRTU", 1, "EXPH", posX, posY, posZ, 0, "ONLY"); } Use of VMC Geometry Construction  Geometry is defined by calls to TVirtualMC interface

I. HrivnacovaCHEP 2003, La Jolla, 27 March void MyMCApplication::GeneratePrimaries() { // Define particle properties: // PDG encoding // position: vx, vy, vz, vt // momentum: px py, pz, e // … // Add particle to MC stack gMC->GetStack() ->SetTrack(toBeDone, -1, pdg, px, py, pz, e, vx, vy, vz, t, …); } Use of VMC Primary Particles  Primary particles are defined by calls to the TVirtualMCStack interface ConstructGeometry InitGeometry GeneratePrimaries BeginEvent BeginPrimary PreTrack Stepping PostTrack FinishPrimary FinishEvent User MC Application

I. HrivnacovaCHEP 2003, La Jolla, 27 March void MyMCApplication:: Stepping() { // Get track position Double_t x, y, z; gMC->TrackPosition(x, y, z); // Get energy deposit Double_t edep = gMC->Edep(); // Create user hit mySD->AddHit(x, y, z, edep); } Use of VMC Hits Production  The user stepping function is called by MC at each step  User gets the properties of the tracked particle by calls to TVirtualMC and saves them in their own hits objects ConstructGeometry InitGeometry GeneratePrimaries BeginEvent BeginPrimary PreTrack Stepping PostTrack FinishPrimary FinishEvent User MC Application

I. HrivnacovaCHEP 2003, La Jolla, 27 March Available MCs  Geant3, Geant4 –Geant3 VMC and Geant4 VMC in production  Fluka –Fluka VMC in development

I. HrivnacovaCHEP 2003, La Jolla, 27 March Available MCs Geant3 VMC  Provided within a single package together with Geant321 (FORTRAN)  Straightforward implementation –VirtualMC was largely inspired by Geant3  Geant3 Geometry Browser –Provided within TGeant3 – people/morsch/Geant3GUI.html

I. HrivnacovaCHEP 2003, La Jolla, 27 March Available MCs Geant4 VMC (1)  Provided within a package - geant4_vmc –Requires Geant4 installation  Access to Geant4 –Switching between Root UI and Geant4 UI –Geant4 classes are not processed by CINT – G4 objects are not accessible from the Root UI  Use of G3toG4 –TVirtualMC has been inspired by Geant3 –An effort has been made to minimize the limitations of the G3toG4 tool – in Geant4 4.0: Support for reflections Limited support for “MANY” volume positions

I. HrivnacovaCHEP 2003, La Jolla, 27 March Available MCs Geant4 VMC (2)  Geant4 VMC extensions: –Geant4 VMC Geometry Browser Analogy to Geant3 Geometry browser –Geometry XML Convertor Enables to export Geant4 geometry to XML (AGDD) and then to browse and visualize using GraXML More on GraXML: in the presentation: “GraXML – Modular Geometric Modeller” (J. Hrivnac)

I. HrivnacovaCHEP 2003, La Jolla, 27 March Available MCs Fluka VMC  In development by the ALICE collaboration and FLUKA team –TFluka in AliRoot  Implemented: –Functions for building/accessing geometry Use of Geant4 VMC + Flugg –Functions for accessing tracked particle during stepping –Recording particles in VMC stack –Functions for run management  To be done: –Functions for setting physics –External decayer

I. HrivnacovaCHEP 2003, La Jolla, 27 March Examples  3 examples provided in geant4_vmc –In spite of being provided within Geant4 VMC, they are built independently and do not require Geant4 installation in case a user wants to run them with Geant3 only  Geant4 novice examples N01, N02 and N03 rewritten with use of Virtual Monte Carlo  Implement MC Application and MC Stack  All examples are executed in the same way: –cd geant4_vmc/examples/E0n –root –root[0].x run_g3.C or run_g4.C

I. HrivnacovaCHEP 2003, La Jolla, 27 March { // Load basic libraries gROOT->LoadMacro(“basiclibs.C”); basiclibs(); // Load this example library gSystem->Load("libexample01"); // MC application Ex01MCApplication* appl = new Ex01MCApplication("Example01", "The example01 MC application"); appl->RunMC(1); } E01 run_g3.C run_g4.C // Load Geant3 libraries gROOT->LoadMacro(“g3libs.C”); g3libs(); // Load Geant4 libraries gROOT->LoadMacro(“g4libs.C”); g4libs(); appl->InitMC("g3Config.C");appl->InitMC("g4Config.C");

I. HrivnacovaCHEP 2003, La Jolla, 27 March void Config() { // RunConfiguration for Geant4 TG4RunConfiguration* runConfiguration = new TG4RunConfiguration(); // Geant4 VMC new TGeant4("TGeant4", "The Geant4 Monte Carlo", runConfiguration); } void Config() { new TGeant3("C++ Interface to Geant3"); } E01 g3Config.C g4Config.C

I. HrivnacovaCHEP 2003, La Jolla, 27 March Examples AliRoot  AliRoot Framework –Integrates simulation, reconstruction and analysis software for the ALICE experiment  Simulation based on Virtual Monte Carlo –A complex “example” of VMC usage –No MC specific code in user code –PPR production with Geant3  More on AliRoot – in the presentations: –“The AliRoot Framework, status and perspectives” (F.Carminati) –“Simulation in ALICE” (A. Morsch) –“ALICE experience with Geant4” (I. Gonzalez)

I. HrivnacovaCHEP 2003, La Jolla, 27 March Dimuon Arm AliRoot Geometry

I. HrivnacovaCHEP 2003, La Jolla, 27 March AliRoot Hits Production Geant3Geant4

I. HrivnacovaCHEP 2003, La Jolla, 27 March VMC Future (1)  Integration of the new Root geometrical modeller (TGeo) in VMC – in progress –Will then be able to define MC geometry directly via TGeo  Geant3, Fluka –Replacement of the native geometry with TGeo inside the program itself –Geant3: Already operational, close to completion Production release in coming weeks –Fluka: Work is ongoing

I. HrivnacovaCHEP 2003, La Jolla, 27 March VMC Future (2)  Geant4 –Discussions about using the Root geometry modeller through an abstract interface to Geant4 geometry have been started –RootToG4 converter Converter from Root geometry to Geant4 native geometry Already operational, close to completion Production release will follow the release of the new Geant3 version  More on TGeo – in the presentation: “A Geometrical Modeller for HEP” (A. Gheata)

I. HrivnacovaCHEP 2003, La Jolla, 27 March Distribution  ROOT CVS server –mc – core package (interfaces), in Root –geant3, geant4_vmc 2 independent modules (parallel to root): –cvs -d co –P geant3 –cvs -d co –P geant4_vmc  ROOT Web – –Distribution of sources: geant321+_vmc.version.tar.gz geant4_vmc.version.tar.gz

I. HrivnacovaCHEP 2003, La Jolla, 27 March Summary  VMC allows the user to run different transport MonteCarlo’s from the same user code –On the menu today: Geant3, Geant4 –Coming soon: Fluka  VMC available from –