Abstract

The Virtual Monte Carlo (VMC) package provides a unified interface to different detector simulation transport engines such as GEANT3 and GEANT4. It has been in production use in various experiments but so far the simulation of one event was restricted to the usage of a single chosen engine. We introduce here the possibility to mix multiple engines within the simulation of a single event. Depending on user conditions the simulation is partitioned among the chosen engines, for instance to profit from each of their advantages or specific capabilities. Such conditions can depend on phase space, geometry, particle type or an arbitrary combination. As a main achievement, this development allows for the implementation of fast simulation kernels at the VMC level which can be used stand-alone or together with full simulation engines. This capability is crucial to cope with largely increasing data expected in future LHC runs.

Highlights

  • The simulation of particles traversing complex detector geometries is one of the crucial building blocks of event simulation in heavy-ion and high-energy physics

  • This paper introduces extensions to the Virtual Monte Carlo (VMC) framework allowing for the partitioning of one event among multiple different engines

  • Such a partitioning could depend on particle type or phase space, detector geometry, other user defined conditions and as such it provides the capability to dispatch the transport to a VMC based fast simulation

Read more

Summary

Introduction

The simulation of particles traversing complex detector geometries is one of the crucial building blocks of event simulation in heavy-ion and high-energy physics. The ALICE experiment at the LHC uses the Virtual Monte Carlo (VMC) [1] library which defines common interfaces and functionalities through abstract classes. In this way, the experiment’s software framework does not depend on a specific transport engine. This paper introduces extensions to the VMC framework allowing for the partitioning of one event among multiple different engines Such a partitioning could depend on particle type or phase space, detector geometry, other user defined conditions and as such it provides the capability to dispatch the transport to a VMC based fast simulation.

The VMC implementation and workflow
General considerations and workflow
Code developments and interfaces
Introducing TMCManager and TMCManagerStack
Modification and extension of TVirtualMCApplication and TVirtualMC
Mixing GEANT3 and GEANT4 simulation
Mixing GEANT4 with a custom fast-simulation-like VMC engine
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call