Difference between revisions of "PhysicalVolumeInfoCollection"
Jump to navigation
Jump to search
(Created page with "Actually, the definition of a data product is slightly broader than this. The <code>art::Run</code> object is just an <code>art::RunId</code> object plus a collection of data...") |
|||
| Line 10: | Line 10: | ||
volume in which the particle was born and the other describes the volume in which | volume in which the particle was born and the other describes the volume in which | ||
the particle stopped. | the particle stopped. | ||
| + | |||
| + | |||
| + | [[Category:Computing]] | ||
| + | [[Category:Computing/Code]] | ||
Revision as of 21:20, 24 March 2017
Actually, the definition of a data product is slightly broader than this.
The art::Run object is just an art::RunId object plus a collection of data products;
similarly for the art::SubRun object. An example of a data product in the Run record
is PhysicalVolumeInfoCollection. When we intialize Geant4, we do it
in the beginRun method of Mu2eG4/src/G4_plugin.cc. At the end of Geant4
initialization we
create a std::vector of all physical volumes known to G4 and we put this
information into the art::Run object as a PhysicalVolumeInfoCollection.
The SimParticle class holds two indices into this collection; one describes the
volume in which the particle was born and the other describes the volume in which
the particle stopped.