index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>VMC Project on VMC</title>
    <link>https://vmc-project.github.io/</link>
    <description>Recent content in VMC Project on VMC</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://vmc-project.github.io/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Build Options</title>
      <link>https://vmc-project.github.io/installation/examples/build-options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/examples/build-options/</guid>
      <description>&lt;p&gt;Overview of the available options for building VMC examples and their default values:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;VMC_WITH_Geant4       Build with Geant4            OFF&#xA;VMC_WITH_Geant3       Build with Geant3            OFF&#xA;VMC_WITH_Multi        Build with multiple engines  OFF&#xA;VMC_INSTALL_EXAMPLES  Install examples libraries and programs  ON&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Geant4 VMC build options are automatically exported in &lt;code&gt;Geant4VMCConfig.cmake&lt;/code&gt;. If Geant4 VMC  was built with VGM, the VGM installation path has to be provided via &lt;code&gt;-DVGM_DIR&lt;/code&gt; option.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Build Options</title>
      <link>https://vmc-project.github.io/installation/geant4_vmc/build-options/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/geant4_vmc/build-options/</guid>
      <description>&lt;p&gt;Geant4 VMC includes the G4Root package and examples, which are independent from Geant4 VMC and can be build and used stand-alone. Use of G4Root, VGM, Geant4 G3toG4, UI and VIS packages in Geant4 VMC library is optional and can be switched on/off during CMake build.&lt;/p&gt;&#xA;&lt;p&gt;Overview of available options and their default values:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Geant4VMC_BUILD_G4Root       Build G4Root        ON&#xA;Geant4VMC_BUILD_MTRoot       Build MTRoot        ON&#xA;Geant4VMC_BUILD_Geant4VMC    Build Geant4VMC     ON&#xA;Geant4VMC_BUILD_EXAMPLES     Build VMC examples  ON&#xA;&#xA;Geant4VMC_USE_G4Root         Build with G4Root                ON&#xA;Geant4VMC_USE_VGM            Build with VGM                   OFF&#xA;Geant4VMC_USE_GEANT4_UI      Build with Geant4 UI drivers     ON&#xA;Geant4VMC_USE_GEANT4_VIS     Build with Geant4 Vis drivers    ON&#xA;Geant4VMC_USE_GEANT4_G3TOG4  Build with Geant4 G3toG4 library OFF&#xA;&#xA;Geant4VMC_INSTALL_EXAMPLES   Install examples    ON&#xA;&lt;/code&gt;&lt;/pre&gt;</description>
    </item>
    <item>
      <title>Building examples application programs - With 3.00.b01</title>
      <link>https://vmc-project.github.io/installation/examples/examples-old/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/examples/examples-old/</guid>
      <description>&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;</description>
    </item>
    <item>
      <title>Geometry Definition &amp; Navigation</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/geometry-definition-navigation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/geometry-definition-navigation/</guid>
      <description>&lt;h3 id=&#34;geometry-definition&#34;&gt;Geometry definition&lt;/h3&gt;&#xA;&lt;p&gt;The VMC supports two ways of geometry definition:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;via &lt;a href=&#34;https://root.cern/doc/master/group__Geometry.html&#34;&gt;Root geometry package (TGeo)&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;via &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMC.html&#34;&gt;TVirtualMC interface&lt;/a&gt; (historically the first way)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The first (newer) way is recommended for new users, the way via VMC is kept for a backward compatibility.&lt;/p&gt;&#xA;&lt;p&gt;Since the version 2.0, user can choose between Geant4 native navigation and G4Root navigation, if geometry is define via TGeo. The choice of the navigation is done via the option specified with creating &lt;a href=&#34;https://vmc-project.github.io/geant4_vmc/g4vmc_html/classTG4RunConfiguration.html&#34;&gt;TG4RunConfiguration&lt;/a&gt; object (see  &lt;a href=&#34;https://vmc-project.github.io/geant4_vmc/examples_html/index.html&#34;&gt;VMC examples&lt;/a&gt; for more details):&lt;/p&gt;</description>
    </item>
    <item>
      <title>Installing Geant3 - Older Versions</title>
      <link>https://vmc-project.github.io/installation/geant3/geant3-old/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/geant3/geant3-old/</guid>
      <description>&lt;p&gt;The following instructions apply to the installation of the versions &amp;lt; 2.0.&lt;/p&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;</description>
    </item>
    <item>
      <title>Installing Geant4 VMC - Older Versions</title>
      <link>https://vmc-project.github.io/installation/geant4_vmc/geant4_vmc-old/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/geant4_vmc/geant4_vmc-old/</guid>
      <description>&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;pre&gt;&lt;code&gt;&amp;lt;li&amp;gt;&amp;lt;b&amp;gt;OpenGL visualization &amp;lt;/b&amp;gt; &amp;lt;br&amp;gt;&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt;It is recommended to build Geant4 X11 OpenGL visualization driver used&#xA;in the VMC examples. It is handled in Geant4 CMake build via the following CMake option:&lt;br&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;-DGEANT4_USE_OPENGL_X11=ON&#xA;&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;pre&gt;&lt;code&gt;&amp;lt;/li&amp;gt;&#xA;&amp;lt;li&amp;gt; &amp;lt;h3&amp;gt; Geant4 VMC &amp;lt;/h3&amp;gt;&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;&lt;!-- raw HTML omitted --&gt;</description>
    </item>
    <item>
      <title>Installing VMC</title>
      <link>https://vmc-project.github.io/installation/vmc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/vmc/</guid>
      <description>&lt;p&gt;VMC requires &lt;a href=&#34;https://root.cern.ch/&#34;&gt;ROOT&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://vmc-project.github.io/user-guide/vmc/vmc-library&#34;&gt;vmc core package&lt;/a&gt; was separated from the ROOT source into a new stand-alone &lt;a href=&#34;https://github.com/vmc-project/vmc&#34;&gt;vmc&lt;/a&gt; package in the GitHub &lt;a href=&#34;https://github.com/vmc-project&#34;&gt;vmc-project&lt;/a&gt; organization.  The motivation for this step was a gain in flexibility and faster workflow for new developments of multiple engine mode. The &lt;code&gt;vmc&lt;/code&gt; package in ROOT is deprecated since ROOT version 6.18 (its compilation is optional) and it is going to be removed in the next ROOT version, 6.26. The VMC stand-alone is then needed for building Geant3 and Geant4 VMC when using ROOT compiled with the vmc disabled (default).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Magnetic Field</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/magnetic-field/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/magnetic-field/</guid>
      <description>&lt;p&gt;The user magnetic field is in VMC defined via &lt;a href=&#34;http://root.cern.ch/root/html/TVirtualMagField.html&#34;&gt;TVirtualMagField&lt;/a&gt; interface and then set to VMC using &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMC.html&#34;&gt;TVirtualMC::SetMagField(TVirtualMagField*)&lt;/a&gt; function. The propagation of tracks inside the magnetic field in Geant4 can be performed to a user-defined accuracy. See more details in the &lt;a href=&#34;http://geant4-userdoc.web.cern.ch/geant4-userdoc/UsersGuides/ForApplicationDeveloper/html/Detector/electroMagneticField.html&#34;&gt;Electromagnetic Field section&lt;/a&gt; in the Geant4 User Guide for Application Developers. Note that while Geant4 allows magnetic, electric and electromagnetic fields, the VMC is currently limited to magnetic fields only.&lt;/p&gt;&#xA;&lt;h3 id=&#34;local-fields&#34;&gt;Local fields&lt;/h3&gt;&#xA;&lt;p&gt;Since Geant4 VMC version 3.2, it is possible to define local magnetic fields. The local field is defined in the same way as a global field, via &lt;a href=&#34;http://root.cern.ch/root/html/TVirtualMagField.html&#34;&gt;TVirtualMagField&lt;/a&gt; interface, but then it has to be associated with a selected volume using &lt;a href=&#34;https://root.cern.ch/root/htmldoc/TGeoVolume.html&#34;&gt;TGeoVolume::SetField(TObject*)&lt;/a&gt; function. The local magnetic field is applied also to all volume daughters, it is possible to combine a global field with one or more local fields. Note that the local fields are supported only with Geant4 and an equivalent global magnetic field has to be provided for Geant3 simulation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mailing List</title>
      <link>https://vmc-project.github.io/support/mailing-list/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/support/mailing-list/</guid>
      <description>&lt;p&gt;The mailing list is used to keep you up to date about new developments in VMC packages, releases and bug fixes. This list is also used to discuss use of VMC with other users and with the developers. If you want to report a bug, please, use &lt;a href=&#34;https://vmc-project.github.io/support/bug-reports/&#34;&gt;Bug Reports&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;To join the &lt;a href=&#34;mailto:root-vmc@cern.ch&#34;&gt;root-vmc@cern.ch&lt;/a&gt; mailing list, do the following:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;If you don&amp;rsquo;t have a CERN account, create a &lt;a href=&#34;https://account.cern.ch/account/Externals&#34;&gt;light weight CERN account&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Add yourself to the &lt;a href=&#34;https://e-groups.cern.ch/e-groups/Egroup.do?egroupId=10060132&amp;amp;AI_USERNAME=RDM&amp;amp;searchField=0&amp;amp;searchMethod=0&amp;amp;searchValue=&amp;amp;pageSize=30&amp;amp;hideSearchFields=false&amp;amp;searchMemberOnly=false&amp;amp;searchAdminOnly=false&amp;amp;AI_SESSION=d2pfPsKDGpw5kQw5CvJnhT1GNPl7QkbMW7pyTctBLrXG3Q7vWkrT!-1625067136!1340887240667&#34;&gt;root-vmc mailing list&lt;/a&gt;, by clicking on the&#xA;&amp;ldquo;Members&amp;rdquo; tab and then on the &amp;ldquo;Add me&amp;rdquo; button.&lt;/li&gt;&#xA;&lt;li&gt;To remove yourself from the mailing list click on the &amp;ldquo;Remove me&amp;rdquo; button on the same above &amp;ldquo;Members&amp;rdquo; page.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Mailing list archive: &lt;a href=&#34;https://groups.cern.ch/group/root-vmc&#34;&gt;VMC Digest&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Publications List</title>
      <link>https://vmc-project.github.io/publications/publications-list/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/publications/publications-list/</guid>
      <description>&lt;p&gt;Please refer to the paper below when publishing results base on simulations with VMC:&lt;/p&gt;&#xA;&#xA;&lt;div class=&#34;notices info&#34; &gt;&lt;p&gt;&lt;strong&gt;Reference paper&lt;/strong&gt;&lt;br&gt;&#xA;Hřivnáčová I et al: The Virtual MonteCarlo,&lt;br&gt;&#xA;ECONF C0303241:THJT006,2003; &lt;a href=&#34;https://arxiv.org/abs/cs/0306005&#34;&gt;e-Print: cs.SE/0306005&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&#xA;&lt;p&gt;All publications listed in time reversed order:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.epj-conferences.org/articles/epjconf/pdf/2020/21/epjconf_chep2020_02005.pdf&#34;&gt;New Developments in the VMC Project&lt;/a&gt;,&lt;br&gt;&#xA;I Hřivnáčová, B Volkel 2020 &lt;em&gt;EPJ Web Conf.&lt;/em&gt; &lt;strong&gt;Volume 245&lt;/strong&gt; 02005&lt;br&gt;&#xA;doi: 10.1051/epjconf/202024502005&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.epj-conferences.org/articles/epjconf/pdf/2020/21/epjconf_chep2020_02008.pdf&#34;&gt;Using multiple engines in the Virtual Monte Carlo package&lt;/a&gt;,&lt;br&gt;&#xA;B Volkel et al  2020 &lt;em&gt;EPJ Web Conf.&lt;/em&gt; &lt;strong&gt;Volume 245&lt;/strong&gt; 02008&lt;br&gt;&#xA;doi: 10.1051/epjconf/202024502008&lt;/p&gt;</description>
    </item>
    <item>
      <title>Running examples</title>
      <link>https://vmc-project.github.io/installation/examples/running-examples/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/examples/running-examples/</guid>
      <description>&lt;p&gt;First, make sure that you have included all libraries paths in your shared library path.&lt;/p&gt;&#xA;&lt;p&gt;For all MCs:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/your_path/root_install/lib&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/your_path/vmc_install/lib&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For Geant3 only:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;path to Pythia6 library&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/your_path/geant3_install/lib[64]&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/your_path/examples_install_g3/lib[64]&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For Geant4 only:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/your_path/geant4_install/lib[64]&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/your_path/geant4_vmc_install/lib[64]&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/your_path/examples_install_g4/lib[64]&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4 id=&#34;running-examples-from-root-session&#34;&gt;Running examples from Root session&lt;/h4&gt;&#xA;&lt;p&gt;The example can be run by calling the provided macros from Root session:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;$ cd geant4_vmc/examples/E01&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;$ root&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;root&lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;0&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt; .x load_g4.C   &lt;span style=&#34;color:#75715e&#34;&gt;# load all libraries needed to run with Geant4&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;root&lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;1&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt; .x run_g4.C    &lt;span style=&#34;color:#75715e&#34;&gt;# run with Geant4&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;or&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;root&lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;0&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt; .x load_g3.C   &lt;span style=&#34;color:#75715e&#34;&gt;# load all libraries needed to run with Geant3&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;root&lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;1&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt; .x run_g3.C    &lt;span style=&#34;color:#75715e&#34;&gt;# run with Geant3&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4 id=&#34;running-examples-application-programs&#34;&gt;Running examples application programs&lt;/h4&gt;&#xA;&lt;p&gt;The example can be also run by calling the executable from the examples installation directory:&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMC Concept</title>
      <link>https://vmc-project.github.io/user-guide/introduction/vmc-concept/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/introduction/vmc-concept/</guid>
      <description>&lt;p&gt;The Virtual Monte Carlo (VMC) allows to run different simulation Monte Carlo without changing the user code and therefore the input and output format as well as the geometry and detector response definition.&lt;/p&gt;&#xA;&lt;p&gt;The core of the VMC is the category of classes &lt;strong&gt;vmc&lt;/strong&gt;. It provides a set of interfaces which completely decouple the dependencies between the user code and the concrete Monte Carlo, two of which have the key role:&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMC Examples</title>
      <link>https://vmc-project.github.io/examples/vmc-examples/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/examples/vmc-examples/</guid>
      <description>&lt;p&gt;A set of examples of usage of VMC is included in &lt;strong&gt;geant4_vmc&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Though provided within Geant4 VMC, they can be built independently and do not require Geant4 installation in case you want to run them with GEANT3 only.&lt;/p&gt;&#xA;&lt;p&gt;See more details on the &lt;a href=&#34;https://vmc-project.github.io/geant4_vmc/examples_html/&#34;&gt;VMC Examples&lt;/a&gt; web page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMC Project</title>
      <link>https://vmc-project.github.io/user-guide/introduction/vmc-project/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/introduction/vmc-project/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/vmc-project&#34;&gt;vmc-project&lt;/a&gt; GitGub organization provides the following packages:&lt;/p&gt;&#xA;&lt;h2 id=&#34;vmc--httpsgithubcomvmc-projectvmc&#34;&gt;vmc &lt;a href=&#34;https://github.com/vmc-project/vmc&#34;&gt;-&amp;gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The core of the VMC provides the &lt;strong&gt;interfaces&lt;/strong&gt; and classes independent from the Monte Carlo transport code.&lt;/p&gt;&#xA;&lt;p&gt;See more in the &lt;a href=&#34;../../vmc-core&#34;&gt;VMC Core&lt;/a&gt; section.&lt;/p&gt;&#xA;&lt;h2 id=&#34;geant3--httpsgithubcomvmc-projectgeant3&#34;&gt;geant3 &lt;a href=&#34;https://github.com/vmc-project/geant3&#34;&gt;-&amp;gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The updated version of &lt;strong&gt;Geant3.21&lt;/strong&gt; that includes several bug fixes compared to the standard version in CERNLIB. The directory TGeant3 contains the classes which &lt;strong&gt;implement the TVirtualMC interface&lt;/strong&gt; for Geant3&lt;/p&gt;&#xA;&lt;p&gt;See more in the &lt;a href=&#34;../../geant3+vmc&#34;&gt;Geant3&lt;/a&gt; section.&lt;/p&gt;&#xA;&lt;h2 id=&#34;geant4_vmc--httpsgithubcomvmc-projectgeant4_vmc&#34;&gt;geant4_vmc &lt;a href=&#34;https://github.com/vmc-project/geant4_vmc&#34;&gt;-&amp;gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Geant4 VMC contains the classes which &lt;strong&gt;implement the TVirtualMC interface for &lt;a href=&#34;http://geant4.cern.ch&#34;&gt;Geant4&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bug Reports</title>
      <link>https://vmc-project.github.io/support/bug-reports/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/support/bug-reports/</guid>
      <description>&lt;p&gt;We use &lt;a href=&#34;http://www.atlassian.com/software/jira/overview&#34;&gt;JIRA&lt;/a&gt; to track bugs and to gather feature requests.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://sft.its.cern.ch/jira/browse/VMC&#34;&gt;Report a bug in VMC packages.&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Experiment Frameworks</title>
      <link>https://vmc-project.github.io/examples/experiment-frameworks/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/examples/experiment-frameworks/</guid>
      <description>&lt;p&gt;VMC was developed by the &lt;a href=&#34;http://aliceinfo.cern.ch/Offline/&#34;&gt;ALICE Software Project&lt;/a&gt; and,&#xA;since then it was adopted by other experiment frameworks.&lt;/p&gt;&#xA;&lt;h4 id=&#34;alice&#34;&gt;ALICE&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://alice-offline.web.cern.ch&#34;&gt;AliRoot&lt;/a&gt; - the ALICE software framework (for LHC Run 1 and 2)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/AliceO2Group/AliceO2&#34;&gt;O2&lt;/a&gt; - the new ALICE software framework in development (for LHC Run 3 and 4)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h4 id=&#34;fair&#34;&gt;FAIR&lt;/h4&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/FairRootGroup/FairRoot&#34;&gt;FairRoot&lt;/a&gt; - A simulation, reconstruction and analysis framework, based on the ROOT system, for FAIR experiments&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Installing Geant4 VMC - Special Installations</title>
      <link>https://vmc-project.github.io/installation/geant4_vmc/special-installations/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/geant4_vmc/special-installations/</guid>
      <description>&lt;!-- raw HTML omitted --&gt;&#xA;&lt;pre&gt;&lt;code&gt;&amp;lt;li&amp;gt; &amp;lt;h3&amp;gt;Geant4 configuration (version &amp;gt;= 9.5) &amp;lt;br&amp;gt;&#xA;         with manual installation (with GNUmake) &amp;lt;/h3&amp;gt;&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;p&gt;If you install Geant4 with the GNUmakefile build system and your own environment setting, you need to have set the following environment variables. This way of installation requires an experience in Geant4 and so it is not recommended for novice users.&lt;br&gt;&#xA;&lt;!-- raw HTML omitted --&gt;&#xA;G4LIB_BUILD_SHARED set to 1 (required)&#xA;G4LIB_USE_G3TOG4 set to 1 (required)&#xA;G4VIS_BUILD_OPENGLX_DRIVER set to 1 (recommended)&#xA;G4VIS_USE_OPENGLX set to 1 (recommended)&#xA;&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Required and Optional Packages</title>
      <link>https://vmc-project.github.io/installation/geant4_vmc/required-optional-packages/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/installation/geant4_vmc/required-optional-packages/</guid>
      <description>&lt;p&gt;Geant4 VMC requires &lt;a href=&#34;https://root.cern.ch/&#34;&gt;ROOT&lt;/a&gt; and &lt;a href=&#34;http://geant4.web.cern.ch/&#34;&gt;Geant4&lt;/a&gt; installed, then the &lt;a href=&#34;https://vmc-project.github.io/user-guide/vmc/vmc-library&#34;&gt;VMC core package&lt;/a&gt; if using ROOT built without &lt;code&gt;vmc&lt;/code&gt; enabled, and optionally, it can be built with &lt;a href=&#34;https://github.com/vmc-project/vgm&#34;&gt;VGM&lt;/a&gt;. See below tips for configuration and installation of these packages.&lt;/p&gt;&#xA;&lt;p&gt;The path to required and optional packages installations can be defined in the standard CMake way, via the paths to the CMake configuration file:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Geant4_DIR      ... path to Geant4Config.cmake&#xA;ROOT_DIR        ... path to ROOTConfig.cmake&#xA;VMC_DIR         ... path to VMCConfig.cmake&#xA;VGM_DIR         ... path to VGMConfig.cmake&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;CMake will also find the CMake configuration files (for ROOT and Geant4) if you source the relevant script from the packages installations (CMAKE_INSTALL_PREFIX) so that they are available in the sestem paths:&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMC</title>
      <link>https://vmc-project.github.io/download/git-vmc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/download/git-vmc/</guid>
      <description>&lt;p&gt;Development version (the whole repository):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git clone http://github.com/vmc-project/vmc.git&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To switch to &amp;lsquo;pro&amp;rsquo; tagged version 2.1:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd vmc&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git checkout v2-1&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To switch to the &amp;lsquo;old&amp;rsquo; tagged version 1.1.p1:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd vmc&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git checkout v1-1-p1&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The list of new developments, bug fixes and the required versions of ROOT and Geant4 for each version can be found in the &lt;a href=&#34;https://github.com/vmc-project/vmc/blob/master/History&#34;&gt;History&lt;/a&gt; file.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMC Core</title>
      <link>https://vmc-project.github.io/user-guide/vmc/vmc-core/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/vmc/vmc-core/</guid>
      <description>&lt;p&gt;The core of the VMC, &lt;code&gt;vmc&lt;/code&gt;, provides a set of interfaces which completely decouple the dependencies between the user code and the concrete Monte Carlo:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMC.html&#34;&gt;TVirtualMC&lt;/a&gt;: Interface to the concrete Monte Carlo program&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCApplication.html&#34;&gt;TVirtualMCApplication&lt;/a&gt;: Interface to the user&amp;rsquo;s Monte Carlo application&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCStack.html&#34;&gt;TVirtualMCStack&lt;/a&gt;: Interface to the particle stack&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCDecayer.html&#34;&gt;TVirtualMCDecayer&lt;/a&gt;: Interface to the external decayer&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCSensitiveDetector.html&#34;&gt;TVirtualMCSensitiveDetector&lt;/a&gt;: Interface to the user&amp;rsquo;s sensitive detector&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The implementation of the TVirtualMC interface is provided for two Monte Carlo transport codes, GEANT3 and &lt;a href=&#34;http://geant4.web.cern.ch/geant4/&#34;&gt;Geant4&lt;/a&gt;, with the VMC packages listed below. The implementation for the third Monte Carlo transport code, FLUKA, has been discontinued by the FLUKA team in 2010.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Geant4 VMC</title>
      <link>https://vmc-project.github.io/download/git-geant4_vmc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/download/git-geant4_vmc/</guid>
      <description>&lt;p&gt;Development version (the whole repository):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git clone http://github.com/vmc-project/geant4_vmc.git&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To switch to the &lt;strong&gt;&amp;lsquo;pro&amp;rsquo;&lt;/strong&gt; tagged version &lt;strong&gt;6.7&lt;/strong&gt; (compatible with &lt;em&gt;vmc 2.1, Geant4 11.3&lt;/em&gt;):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd geant4_vmc &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git checkout v6-7&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To switch to the &lt;strong&gt;&amp;lsquo;old&amp;rsquo;&lt;/strong&gt; tagged version &lt;strong&gt;6.6.p3&lt;/strong&gt; (compatible with &lt;em&gt;vmc 2.x, Geant4 11.2.x&lt;/em&gt;):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd geant4_vmc &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git checkout v6-6-p3&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The list of new developments, bug fixes and the required versions of ROOT and Geant4 for each version can be found in the &lt;a href=&#34;https://github.com/vmc-project/geant4_vmc/blob/master/history&#34;&gt;history&lt;/a&gt; file.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Multiple VMC Engines</title>
      <link>https://vmc-project.github.io/user-guide/vmc/multiple-vmc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/vmc/multiple-vmc/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;The VMC package allows splitting the event simulation among multiple engines. The criteria of how to split the simulation have to be defined by the user and among others the decision which engine to be used could depend on&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;geometry&lt;/li&gt;&#xA;&lt;li&gt;particle phase space&lt;/li&gt;&#xA;&lt;li&gt;particle type&lt;/li&gt;&#xA;&lt;li&gt;any combination of that&lt;/li&gt;&#xA;&lt;li&gt;&amp;hellip;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Running multiple engines is fully supported for&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/vmc-project/geant3&#34;&gt;GEANT3_VMC&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/vmc-project/geant4_vmc&#34;&gt;GEANT4_VMC&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This also allows the user to implement his/her own class deriving from &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMC.html&#34;&gt;TVirtualMC&lt;/a&gt; to be used in a split simulation. The communication between the engines is handled by a singleton object of type &lt;a href=&#34;https://vmc-project.github.io/vmc/classTMCManager.html&#34;&gt;TMCManager&lt;/a&gt; such that the user does not have to deal with special implementation details. Hence, pausing an engine, re-starting it or transferring tracks between them is done automatically and at the same time the user stack is kept up-to-date. Furthermore, the same user application derived from &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCApplication.html&#34;&gt;TVirtualMCApplication&lt;/a&gt; together with the same user stack derived from &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCStack.html&#34;&gt;TVirtualMCStack&lt;/a&gt; can be used for both a single engine run or a simulation split among multiple ones.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sensitive Detectors and Volumes</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/sensitive-volumes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/sensitive-volumes/</guid>
      <description>&lt;h2 id=&#34;sensitive-detectors&#34;&gt;Sensitive Detectors&lt;/h2&gt;&#xA;&lt;p&gt;Recently (since ROOT version v6.13.04) a new interface to user sensitive detector, &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCSensitiveDetector.html&#34;&gt;TVirtualMCSensitiveDetector&lt;/a&gt;, has been added in the set of VMC interfaces. The support for this new way of definig sensitive detector is available since geant3 2.6 and geant4_vmc 4.0.&lt;/p&gt;&#xA;&lt;p&gt;The user sensitive detectors object should be associated to the selected volumes in the new dedicated MCApplication function:&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-cpp&#34; data-lang=&#34;cpp&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#66d9ef&#34;&gt;void&lt;/span&gt; TVirtualMCApplication&lt;span style=&#34;color:#f92672&#34;&gt;::&lt;/span&gt;SetSensitiveDetectors()&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/p&gt;&#xA;&lt;p&gt;using the new TVirtualMC function:&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-cpp&#34; data-lang=&#34;cpp&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#66d9ef&#34;&gt;void&lt;/span&gt; TVirtualMC&lt;span style=&#34;color:#f92672&#34;&gt;::&lt;/span&gt;SetSensitiveDetector(&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#x9;&lt;span style=&#34;color:#66d9ef&#34;&gt;const&lt;/span&gt; TString&lt;span style=&#34;color:#f92672&#34;&gt;&amp;amp;&lt;/span&gt; volumeName,&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&#x9;TVirtualMCSensitiveDetector&lt;span style=&#34;color:#f92672&#34;&gt;*&lt;/span&gt; userSD);&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;Users can also choose whether scoring should be performed exclusively via sensitive detectors or via both sensitive detectors and &lt;code&gt;MCApplication::Stepping()&lt;/code&gt; using the function&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-cpp&#34; data-lang=&#34;cpp&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#66d9ef&#34;&gt;void&lt;/span&gt; VirtualMC&lt;span style=&#34;color:#f92672&#34;&gt;::&lt;/span&gt;SetExclusiveSDScoring(Bool_t);&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;If exclusive scoring is selected, the &lt;code&gt;MCApplication::Stepping()&lt;/code&gt; is not called by MC.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Geant3</title>
      <link>https://vmc-project.github.io/download/git-geant3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/download/git-geant3/</guid>
      <description>&lt;p&gt;Development version (the whole repository):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git clone http://github.com/vmc-project/geant3.git&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To switch to the &lt;strong&gt;&amp;lsquo;pro&amp;rsquo;&lt;/strong&gt; tagged version &lt;strong&gt;4.4&lt;/strong&gt; (compatible with &lt;em&gt;vmc 2.x, ROOT 6.x&lt;/em&gt;):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd geant3&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git checkout v4-4&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To switch to the &lt;strong&gt;&amp;lsquo;old&amp;rsquo;&lt;/strong&gt; tagged version &lt;strong&gt;3.9.p1&lt;/strong&gt; (compatible with &lt;em&gt;vmc 1,x, ROOT 6.x&lt;/em&gt;):&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd geant3 &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git checkout v3-9-p1&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To switch to the &lt;strong&gt;&amp;lsquo;old&amp;rsquo;&lt;/strong&gt; tagged version &lt;strong&gt;2.7.p2&lt;/strong&gt; (compatible with &lt;em&gt;ROOT 5.x&lt;/em&gt;):&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;cd geant3 &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;git checkout v2-7-p2&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For older versions see the correspondent tag and the required version of ROOT in&#xA;the &lt;a href=&#34;https://github.com/vmc-project/geant3/blob/master/history&#34;&gt;history&lt;/a&gt; file.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Physics Lists</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/physics-lists/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/physics-lists/</guid>
      <description>&lt;h2 id=&#34;physics-list-selection&#34;&gt;Physics list selection&lt;/h2&gt;&#xA;&lt;h3 id=&#34;physics&#34;&gt;Physics&lt;/h3&gt;&#xA;&lt;p&gt;Geant4 VMC does not provide a default physics list. User have to choose the physics list from the physics lists provided in Geant4 (see the &lt;a href=&#34;http://geant4-userdoc.web.cern.ch/geant4-userdoc/UsersGuides/PhysicsListGuide/html/index.html&#34;&gt;Geant4 Physics List Guide&lt;/a&gt; or include their own physics list. The choice of the physics list is done via the option specified with creating &lt;a href=&#34;https://vmc-project.github.io/geant4_vmc/g4vmc_html/classTG4RunConfiguration.html&#34;&gt;TG4RunConfiguration&lt;/a&gt; object. This option is passed as&lt;em&gt;the second argument&lt;/em&gt; in &lt;code&gt;TG4RunConfiguration&lt;/code&gt; constructor (see &lt;a href=&#34;examples&#34;&gt;examples&lt;/a&gt; for more details).&lt;!-- raw HTML omitted --&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Stacking of Particles</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/stacking-of-particles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/stacking-of-particles/</guid>
      <description>&lt;p&gt;The user &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMCStack.html&#34;&gt;VMC stack&lt;/a&gt; is used differently in Geant3 VMC and Geant4 VMC. Geant3 VMC pops both primary and secondary particles as they are provided by &lt;code&gt;TVirtualMCStack::PopNextTrack()&lt;/code&gt;, while Geant4 VMC pops only primary particles using &lt;code&gt;TVirtualMCStack::PopPrimaryForTracking()&lt;/code&gt; from the VMC stack.&lt;/p&gt;&#xA;&lt;p&gt;Stacking of secondary particles is then handled by Geant4 kernel and the user VMC stack only monitors this stacking. By default, Geant4 VMC saves each secondary particle when it starts its tracking (at the the pre-track phase). User can customize this default behaviour and choose also not to save secondary particles at all or to save them in the step of their parent particle, immediately after their creation.&#xA;This can be done using the command (see in the section on  &lt;a href=&#34;https://vmc-project.github.io/user-guide/geant4_vmc/switching-user-interfaces&#34;&gt;Switching User Interfaces&lt;/a&gt; how to apply Geant4 commands in a Root user session):&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tar Files</title>
      <link>https://vmc-project.github.io/download/tar-files/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/download/tar-files/</guid>
      <description>&lt;h3 id=&#34;pro-versions&#34;&gt;Pro versions&lt;/h3&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th style=&#34;text-align: left&#34;&gt;Package&lt;/th&gt;&#xA;          &lt;th style=&#34;text-align: left&#34;&gt;Version&lt;/th&gt;&#xA;          &lt;th style=&#34;text-align: left&#34;&gt;Tar file&lt;/th&gt;&#xA;          &lt;th style=&#34;text-align: left&#34;&gt;Tested with&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;vmc&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;2.1&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://github.com/vmc-project/vmc/archive/v2-1.tar.gz&#34;&gt;vmc-2-1.tar.gz&lt;/a&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;&lt;em&gt;ROOT 6.32/08&lt;/em&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;geant4_vmc&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;6.7&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://github.com/vmc-project/geant4_vmc/archive/v6-7.tar.gz&#34;&gt;geant4_vmc-6-7.tar.gz&lt;/a&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;&lt;em&gt;vmc 2.1, ROOT 6.32/08&lt;/em&gt;,&lt;!-- raw HTML omitted --&gt; &lt;em&gt;Geant4 11.3 (with embedded CLHEP 2.4.7.1),&lt;/em&gt; &lt;!-- raw HTML omitted --&gt; &lt;em&gt;VGM 5.3.1,&lt;/em&gt; &lt;!-- raw HTML omitted --&gt; &lt;em&gt;Garfield 5.0&lt;/em&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;geant3&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;4.4&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;&lt;a href=&#34;https://github.com/vmc-project/geant3/archive/v4-4.tar.gz&#34;&gt;geant3-4-4.tar.gz&lt;/a&gt;&lt;/td&gt;&#xA;          &lt;td style=&#34;text-align: left&#34;&gt;&lt;em&gt;vmc 2.0, ROOT 6.32/01 (alice)&lt;/em&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt;In general, the VMC packages can be built with the Root version which they were tested with and higher, and Geant4 VMC with the Geant4 version which it was tested with including the patches. Note that the Geant4 patches released after the Geant4 VMC tag do not appear in the table above, it is however recommended to update Geant4 with each patch release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Geant3 &#43; VMC Content</title>
      <link>https://vmc-project.github.io/user-guide/geant3&#43;vmc/geant3&#43;vmc-content/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant3&#43;vmc/geant3&#43;vmc-content/</guid>
      <description>&lt;div class=&#34;notices warning&#34; &gt;&lt;p&gt;Only the &lt;strong&gt;Geant3.21&lt;/strong&gt; code itself and the implementation of the &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMC.html&#34;&gt;TVirtualMC&lt;/a&gt; interface, &lt;strong&gt;TGeant3&lt;/strong&gt;, provided in &lt;a href=&#34;https://github.com/vmc-project/geant3&#34;&gt;geant3&lt;/a&gt; are maintained by the VMC project.&lt;/p&gt;&#xA;&lt;/div&gt;&#xA;&#xA;&lt;h3 id=&#34;geant321&#34;&gt;Geant3.21&lt;/h3&gt;&#xA;&lt;p&gt;The updated version of Geant3.21 that includes several bug fixes compared to the standard version in CERNLIB.&#xA;In this version all Geant3 gxxxxx routines have been renamed g3xxxxx.&lt;/p&gt;&#xA;&lt;p&gt;The old &lt;code&gt;Makefile&lt;/code&gt; system was replaced with a &lt;code&gt;CMake&lt;/code&gt; based system since version 2.0.&lt;/p&gt;&#xA;&lt;p&gt;See also &lt;a href=&#34;https://vmc-project.github.io/geant.pdf&#34;&gt;Geant3.21 User Guide&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;tgeant3-geant3-vmc&#34;&gt;TGeant3 (Geant3 VMC)&lt;/h3&gt;&#xA;&lt;p&gt;The directory &lt;code&gt;TGeant3&lt;/code&gt; contains the classes &lt;a href=&#34;https://github.com/vmc-project/geant3/blob/master/TGeant3/TGeant3.h&#34;&gt;TGeant3&lt;/a&gt; and &lt;a href=&#34;https://github.com/vmc-project/geant3/blob/master/TGeant3/TGeant3TGeo.h&#34;&gt;TGeant3TGeo&lt;/a&gt;,&#xA;which implement the &lt;a href=&#34;https://vmc-project.github.io/vmc/classTVirtualMC.html&#34;&gt;TVirtualMC&lt;/a&gt; interface.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Special Cuts and Regions</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/special-cuts-and-regions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/special-cuts-and-regions/</guid>
      <description>&lt;p&gt;The way of applying cuts is different in Geant3 and Geant4. In Geant3, the cuts are defined as a limit in energy, which is applied both as an energy threshold (a secondary particle is not produced if its energy is beyond the threshold) and a tracking cut (a particle is stopped when its energy gets below the cut).&lt;/p&gt;&#xA;&lt;p&gt;Inn Geant4, there is defined a unique cut in range which is then converted to an energy threshold per particle and material. The advantage is that you keep the same spatial resolution of your energy deposit over the whole detector. It is also possible to define cuts per regions, as in big experimental setups you may want to speed up your simulation by setting a higher cut in the support structures etc. See more details at the Geant4 User Guide for Application Developers, &lt;a href=&#34;http://geant4-userdoc.web.cern.ch/geant4-userdoc/UsersGuides/ForApplicationDeveloper/html/TrackingAndPhysics/thresholdVScut.html&#34;&gt;section Production Threshold versus Tracking Cut&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>User Geant4 Classes</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/user-geant4-classes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/user-geant4-classes/</guid>
      <description>&lt;p&gt;The default Geant4 VMC behaviour, defined by the Geant4 user mandatory classes and user action classes implemented in Geant4 VMC, can be customized by a user by providing his own class derived from &lt;code&gt;TG4RunConfiguration&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Such customization is recommended for including a user own physics list. User has also the possibility to override detector construction and/or primary generation action classes and use an existing Geant4 geometry/primary generator definition with VMC. In other cases, though the customisation is possible and allowed by the design, it has not been tested and so it is not recommended especially for the novice users.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meetings (Old)</title>
      <link>https://vmc-project.github.io/publications/meetings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/publications/meetings/</guid>
      <description>&lt;!-- raw HTML omitted --&gt;</description>
    </item>
    <item>
      <title>Visualization</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/visualization/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/visualization/</guid>
      <description>&lt;p&gt;Geant4 visualization and UI drivers can be in Geant4 VMC enabled via dedicated CMake configuration options. See more details in &lt;a href=&#34;https://vmc-project.github.io/installation/geant4_vmc/&#34;&gt;Installing Geant4 VMC&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The G3-like functions for visualization defined in TVirtualMC are overcome with the interactive visualization capabilities of both Root and Geant4 geometry modellers, that&amp;rsquo;s why user is encouraged to use these modeller directly. User can set Geant4 visualization options using Geant4 visualization commands, as it is illustrated in the &lt;a href=&#34;https://vmc-project.github.io/geant4_vmc/examples_html/index.html&#34;&gt;VMC examples&lt;/a&gt; in &lt;code&gt;g4vis.in&lt;/code&gt; macro.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Switching User Interfaces</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/switching-user-interfaces/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/switching-user-interfaces/</guid>
      <description>&lt;p&gt;The VMC interface provides a common denominator for all implemented MC&amp;rsquo;s and cannot cover all commands available in a Geant4 user session through Geant4 user interface (UI). Switching between the Root UI and the Geant4 UI gives a user the possibility of working with the native Geant4 UI. It is also possible to process a foreign command or a foreign macro in both UIs:&lt;/p&gt;&#xA;&lt;h3 id=&#34;from-root-to-geant4-ui&#34;&gt;From Root to Geant4 UI&lt;/h3&gt;&#xA;&lt;p&gt;Switching UI:&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-cpp&#34; data-lang=&#34;cpp&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;root [&lt;span style=&#34;color:#ae81ff&#34;&gt;0&lt;/span&gt;] ((TGeant4&lt;span style=&#34;color:#f92672&#34;&gt;*&lt;/span&gt;)gMC)&lt;span style=&#34;color:#f92672&#34;&gt;-&amp;gt;&lt;/span&gt;StartGeantUI();&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Multi-threaded Processing</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/multi-threaded-processing/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/multi-threaded-processing/</guid>
      <description>&lt;h3 id=&#34;geant4-vmc-with-multi-threading-geant4&#34;&gt;Geant4 VMC with Multi-threading Geant4&lt;/h3&gt;&#xA;&lt;p&gt;Since version 3.00, Geant4 VMC supports running Geant4 in multi-threading (MT) mode. The VMC application will run automatically in MT mode when Geant4 VMC is built against Geant4 MT. This default behaviour can be changed via the option specified with creating &lt;a href=&#34;https://vmc-project.github.io/geant4_vmc/g4vmc_html/classTG4RunConfiguration.html&#34;&gt;TG4RunConfiguration&lt;/a&gt; passed as the fifth argument in TG4RunConfiguration constructor. &lt;em&gt;(Note that the fourth argument, specialStacking option, cannot be omitted in this case.)&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;The VMC application which has not been migrated to MT should be run in a sequential mode, either with Geant4 VMC built against Geant4 sequential libraries or with Geant4 VMC built against Geant4 MT libraries with disabled multi-threading mode in &lt;code&gt;TG4RunConfiguration&lt;/code&gt;. Otherwise its run will stop with an exception.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Verbosity</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/verbosity/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/verbosity/</guid>
      <description>&lt;p&gt;For many Geant4 VMC classes (like for Geant4 classes) the user can select a higher verbosity level and activate various printings which can help in understanding or debugging his application.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/all level&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Set the same verbose level (level &amp;gt;= 0) to all Geant4 VMC objects. If level = 0 no printing is issued, the higher the level is more printings will be issued.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/geometryManager &lt;span style=&#34;color:#ae81ff&#34;&gt;2&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Activate the debug printing from VGM geometry conversion (when geomRootToGeant4 option is selected)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/regionsManager &lt;span style=&#34;color:#ae81ff&#34;&gt;1&lt;/span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;2&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;3&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;level=1: print the number of regions added via VMC&lt;/li&gt;&#xA;&lt;li&gt;level=2: print also the list of all volumes, the cuts in energy and calculated cuts in range&lt;/li&gt;&#xA;&lt;li&gt;level=3: print also all evaluated energy values&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/composedPhysicsList &lt;span style=&#34;color:#ae81ff&#34;&gt;2&lt;/span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;3&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;[&lt;/span&gt;4&lt;span style=&#34;color:#f92672&#34;&gt;]&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;Set the same verbose level to the registed user physics lists.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Verbosity for Developers</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/vebosity-for-developers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/vebosity-for-developers/</guid>
      <description>&lt;p&gt;For many Geant4 VMC classes (like for Geant4 classes) the user can select a higher verbosity level and activate various printings which can help in understanding or debugging his application. Here we list the commands useful rather for Geant4 VMC developers, for the commands useful for users see &lt;a href=&#34;https://vmc-project.github.io/user-guide/geant4_vmc/verbosity&#34;&gt;Verbosity&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/SDConstruction  &lt;span style=&#34;color:#ae81ff&#34;&gt;2&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Print the volumes IDs (implemented via G4VSensitiveDetector objects) and the maps between volumes and volume IDs.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/runManager &lt;span style=&#34;color:#ae81ff&#34;&gt;3&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Print the logical volume store.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/trackManager &lt;span style=&#34;color:#ae81ff&#34;&gt;2&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Print particleID info from &lt;code&gt;SetTrackInformation&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/physicsManager &lt;span style=&#34;color:#ae81ff&#34;&gt;2&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Print the parameter name and value from calls to Gstpar.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/particlesManager &lt;span style=&#34;color:#ae81ff&#34;&gt;2&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Print the map between the names of special particles in Root and Geant4 (like geantino, opticalphoton, etc.); print also info about particles and ions defined by user.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/physicsProcessControlMap &lt;span style=&#34;color:#ae81ff&#34;&gt;1&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/physicsProcessMCMap &lt;span style=&#34;color:#ae81ff&#34;&gt;1&lt;/span&gt;     &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/physicsStepLimiter &lt;span style=&#34;color:#ae81ff&#34;&gt;1&lt;/span&gt;     &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;/mcVerbose/physicsUserParticles &lt;span style=&#34;color:#ae81ff&#34;&gt;1&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Print info about each constructed special process; in case of map processes (physicsProcessControlMap, physicsProcessMCMap) print also whether the mapping was successful (all physics processes in the user physics list were identified in the maps).&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Source code documentation</title>
      <link>https://vmc-project.github.io/user-guide/geant4_vmc/source-code-documentation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/user-guide/geant4_vmc/source-code-documentation/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://vmc-project.github.io/geant4_vmc/g4vmc_html/index.html&#34;&gt;Source code documentation&lt;/a&gt; has been generated from the source code by &lt;a href=&#34;http://www.stack.nl/%7Edimitri/doxygen//index.html&#34;&gt;Doxygen&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Copyright</title>
      <link>https://vmc-project.github.io/copyright/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/copyright/</guid>
      <description>&lt;p&gt;Copyright (C) 2019 CERN and copyright holders of VMC Project.&#xA;This software is distributed under the terms of the GNU General Public&#xA;License v3 (GPL Version 3), copied verbatim in the file &amp;ldquo;LICENSE&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;Copyright holders Institutions:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;European Organization for Nuclear Research (CERN), Geneva, Switzerland&lt;/li&gt;&#xA;&lt;li&gt;Institut de Physique Nucléaire dʼOrsay (IPNO), Université Paris-Sud, CNRS-IN2P3, Orsay, France&lt;/li&gt;&#xA;&lt;li&gt;Ruprecht Karls Universitaet Heidelberg (DE)*&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Credits</title>
      <link>https://vmc-project.github.io/credits/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://vmc-project.github.io/credits/</guid>
      <description>&lt;p&gt;The concept of Virtual MonteCarlo has been developed by the ALICE Software Project .&#xA;Authors: R.Brun&lt;!-- raw HTML omitted --&gt;1&lt;!-- raw HTML omitted --&gt;, F.Carminati*&lt;!-- raw HTML omitted --&gt;1&lt;!-- raw HTML omitted --&gt;&lt;em&gt;, I.Hrivnacova&lt;/em&gt;&lt;!-- raw HTML omitted --&gt;2&lt;!-- raw HTML omitted --&gt;&lt;em&gt;, A.Morsch&lt;/em&gt;&lt;!-- raw HTML omitted --&gt;1&lt;!-- raw HTML omitted --&gt;*&lt;/p&gt;&#xA;&lt;p&gt;The integration with TGeo, G4Root: A. Gheata*&lt;!-- raw HTML omitted --&gt;1&lt;!-- raw HTML omitted --&gt;*&lt;/p&gt;&#xA;&lt;p&gt;The multiple VMC engines: B. Volkel*&lt;!-- raw HTML omitted --&gt;1,3&lt;!-- raw HTML omitted --&gt;*&lt;/p&gt;</description>
    </item>
  </channel>
</rss>