AIDASoft/DD4hep: v01-02

v01-02

• 2017-08-11 Andre Sailer (PR#213)

  • CMake:: dd4hep_generate_rootmap: use CMAKE_INSTALL_LIBDIR if it is set. If the macro is called from other libraries this variable might be set and should be used for consistency. Fixes #212

• 2017-08-15 Yorgos Voutsinas (PR#216)

  • Adding variable "nocore" for beam pipe (with default value = false) In case the variable appears in the BP xml file as "true", the BP sections will have no core of beam material, in order that someone might add various BP walls made of different materials while avoiding G4 overlaps. Example of use:<detector name="BeBeampipe" type="DD4hep_Beampipe_o1_v01" insideTrackingVolume="true" nocore="true" vis="BeamPipeVis">

• 2017-08-15 Jan Strube (PR#215)

  • LCIOEventReader: adding parameter for the name of the MCParticle collection: MCParticleCollectionName

• 2017-08-14 Markus Frank (PR#217) ## Enhance ROOT Detector Description Persistency Conditions slices from the DD4hep conditions store can now be saved to ROOT files ans named objects. Conditions persistency examples are added to the examples/Conditions section. The examples are derived from the Telescope and CLICSiD example:

  • Conditions_Telescope_root_save
  • Conditions_Telescope_root_load_iov
  • Conditions_Telescope_root_load_pool
  • Conditions_CLICSiD_root_save_LONGTEST
  • Conditions_CLICSiD_root_load_iov_LONGTEST
  • Conditions_CLICSiD_root_load_usr_LONGTEST
  • Conditions_CLICSiD_root_load_cond_LONGTEST

  ## Fix Handle Problem when Accessing Materials from Volumes
  A cast problem was not spotted in the last commit, which manifested itself in accessing invalid materials from volumes. This commit resolves #211 , reported by @jhrdinka.

  A set of tests checks this behaviour in the ClientTests: ClientTests_volume_materials_<text>, where the volume tree is scanned and for all sensitive volumes and access the corresponding materials/TGeoMedium entities from the volume object.

• 2017-07-19 Markus Frank (PR#209)

  • Implement dd4hep::Tube using TGeoTubeSeg (See also Issue AIDASoft/DD4hep#203 for details)

• 2017-07-21 Markus Frank (PR#210) ## Implement ROOT persistency mechanism for the conditions

  Conditions pools can now be made persistent provided all the dictionaries for the payload objects are provided. A new class ConditionsRootPersistency allows to save and re-load conditions pools to/from a ROOT file. Such pools can either be:

  • Simple ConditionsPool objects
  • The entire IOV indexed pool set (class ConditionsIOVPool) or
  • A the pool used by a ConditionsSlice (class UserPool).
  • A std::vector<Condition> which belong all to the same IOV

  In any case the restoration of the saved conditions is performed through the ConditionsManager interface in order to ensure proper management of the added condition objects.

  Some example plugin tasks were added in examples/Conditions:

  • DD4hep_ConditionExample_save to save conditions to a ROOT file.
  • DD4hep_ConditionExample_load to restore conditions from file.

  Others to come.

  ## Split of dictionary files The ROOT dictionary creation in DDCore was getting increasingly large. Now the ROOT dictionaries are created in several files, what firstly allows them to be produced in parallel and secondly eases the compilation due to smaller generated file sizes.