Abstract
Virtual Monte Carlo (VMC) provides a unified interface to different detector simulation transport engines such as GEANT3 and GEANT4. Since recently all the VMC packages (the VMC core library, also included in ROOT, and the GEANT3 and GEANT4 VMC) are distributed via the VMC Project GitHub organization. In addition to these VMC related packages, the VMC project also includes the Virtual Geometry Model (VGM), which is optionally used in GEANT4 VMC for conversion between GEANT4 and ROOT TGeo geometry models.In this contribution we will present the new organization of the VMC project at GitHub and new developments in the VMC interfaces and the VMC packages. We will cover the introduction of the sensitive detector interface in the VMC core and both GEANT3 and GEANT4 VMC and the new GEANT4-related developments.GEANT4 VMC 3.0 with the integration of multithreading processing was presented at CHEP in 2015. In this presentation we will report on new features included since this version: the improved support for magnetic fields, the integration of fast simulation, Garfield physics, GEANT4 transition radiation and monopole physics. Five new VMC examples demonstrating these new features, and serving also for tests, will be also discussed. Finally we will mention the work towards the code quality and improvements in testing, documentation and automated code formatting.
Highlights
Virtual Monte Carlo (VMC) [1] defines an abstract layer between a detector simulation user code and the Monte Carlo transport code (MC)
VMC was developed by the ALICE Offline Project and, after the complete removal of all dependencies from the experiment specific framework, it was included in ROOT [5]
The first version of the VMC interface was included in ROOT 3.03/05 in October 2002, and the packages with the implementation of the VMC interface for GEANT3 and GEANT4 were distributed at the ROOT web site
Summary
Virtual Monte Carlo (VMC) [1] defines an abstract layer between a detector simulation user code and the Monte Carlo transport code (MC) In this way the user code is independent from any specific MC and can be used with different transport codes, such as GEANT 3.21 [2], GEANT4 [3] or FLUKA [4], within the same simulation application. In past two years the VMC packages were gradually moved from ROOT into a standalone project in GitHub [8]. The introduction of the multiple engine framework in the VMC packages and new developments in VGM are covered in two separate contributions to this conference [9], [10]
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
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 callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
