Geometry Work Plan for 2016

Version 1.0

NOTE: Any dates assigned to items are to be considered just indicative.
- Items marked with refer to new developments.
- Items marked with will involve new man-power or contribution from external sources interested in the project.
- Items marked with will require coordination with more than one Working Group.
- Items marked with (*) may or may not be achieved.

1. Architecture:
   • Implement use of C++11 constructs in key areas - (1)/(2)

     Continue adiabatic adoption of C++11 constructs to simplify and enhance performance on key areas of the geometry modeller and navigation system.

2. Navigation & optimisation:
   • Review use of regular navigation in conjunction with multiple-scattering - (1)

     Resolve current open issue affecting regular navigation for run-time warnings being sometimes reported.

   • Profiling and optimisation of multiple navigation - (1)/(2)

     Revise the design and implementation of multiple navigation and coupled-transportation.
     Identify any open issue in application to fast-simulation, scoring and layered tracking geometries and in conjuction with magnetic field transport.
     Identify possible CPU performance penalties which may be introduced with the activation of coupled-transportation. Optimize overall performance (ATLAS request).

   • Separate safety computation and state from navigator - (2)

     Loose coupling of G4Navigator in the computation of the safety distances from geometrical boundaries, factorising out the implementation now included in G4Navigator class, to get rid of potential side effects.
     Implement strategy for a light-weight base navigator class not holding navigation state, eventually adopting template arguments.

3. New features:
   • Introduction of fast and high-order steppers in field propagation - (1)/(2)

     Revised implementation of steppers based on templates.

   • Introduction of scaled shapes construct - (1)/(2)

     Ability to define limited set of solids with applied scaling transformation.

   • Complete implementation of the Unified Solids library with progressive adoption of shapes from VecGeom - (2)

     Complete implementation of remaining solids in the Unified Solids library (VecGeom) for geometrical shapes.
     Integrate with the new vectorised implementation of the primitives from the VecGeom geometry modeller currently under development.

• Routine activities
  • Review of user documentation

(1) First semester
(2) Second semester

Created: 19 January 2016
Modified: 19 January 2016