Marc Verderi, Paulo Mora de Freitas job list.

• G4Transportation and switch mechanism: The idea for the switch mechansim would be to change on the fly the world volume of the navigator for tracking. This navigator can be shared by all processes thanks to the G4TransportationManager class.

  However the G4Transportation and the G4Stepping- Manager keep both internally two touchables histories, making the above change of the world volume in the navigator ineffective.

  We would like to understand the respective role of those touchables and see if it could be avoided that the memory of the world volume is kept somewhere else than in the navigator for tracking.

• Navigation in ghosts with magnetic field: y When using ghosts, the parameterisation provides the navigation in the ghost geometries. When a mag-field is present and when the param limits the step on a ghost volume boudary, numerical precision problems during the integration make the endpoint computed by the G4Transportation not always on the ghost surface.
• parameterisation domain: Should it go up to the level of geometry, run... ? Generic shower parameterisation may use the hits+digi domain. PAI model may use the tracking domain.
• bugs : needed by the Geant4 Tesla applications, here you have a couple of Geant4 bugs we insist to find a true solution :
  • Invalid call in G4Box::DistanceToOut(p), point p is outside(PR#150)
  • Invalid enum in G4Box::CalcNormal (PR#101)
  • G4IntersectionSolid G4Exception (PR#98, it's not RESSO and it's not the same as the PR#150!!!)
  It concerns mainly the geometry/solids/Boolean and geometry/solids/CSG/.../Box. Perhaps the navigation also.