Summary of SiD Tracking Discussions, May 7-11, 2007 at SLAC

This is a summary of some issues that we decided or agreed to leave open. A separate page contains a list of work packages.

I will try to remember to put my personal comments in italics.

Persistency

• We will only persist the official LCIO objects: SimTrackerHit, RawTrackerHit, TrackerHit and the reconstructed track class ( don't know its proper name).
• We will work with LCIO to get small changes made to these objects, but not big changes. We will shoehorn our objects into the defined persistent objects.
• We will not support persistency for other information even if it cannot easily be recomputed.
• We will not persist clusters.
• We anticipate that a future evolution of the reconstructed track class ( perhaps it will be
  spelled trajectory, not track ), will allow us to persist residuals.

I view this as much too confining. We should must be able to persist anything we put into the event, even if that information
is not useful to the other collaborations. I do agree that track objects and all those downstream of them should be compatible with those used by other collaborations.

New Geometry

The new geometry is well underway but not yet finished. This is the geometry that
can describe the detector made of wafers. It can also describe a detector made of
cylinders.

RawTrackerHit

We will get LCIO to approve several mods to the RawTrackerHit class and use it as the persistent
representation of a single hit pixel or strip.

...