Page History

...

Notes by Rob Kutschke. Corrections and comments are welcome.

We discussed how to move forward resolve problems with tracks from generated by the fast MCFastMC. The
Here are my notes from the meeting today. I am not sure if we are nearing the end of this discussion or just starting it. Corrections and comments are welcomeroot of the problem is the inconsistent use of the concept of a "reference point".

Jan's web page that Norman referenced is: httpshttp://confluence.slac.stanford.edu/display/ilc~jstrube/EvolvingA+theNew+LCIO+Track+ClassInterface^{Image Modified}
I have not yet had a chance to look at it so there is some chance that my notes below contradict it ....Other related discussions are at

After the meeting I found an old note from Tony that points to an LCIO document that defines the reference point: http://confluencewww-flc.slacdesy.stanford.edude/displaylcnotes/~jstrube/A+New+Track+Interface^{Image Removed}And a comment on this page: https://confluence.slac.stanford.edu/display/ilc/From+Rob+Kutschke^{Image Removed}
This last page describes what is actually found innotes/LC-DET-2006-004.pdf
This definition is consistent with the notes below.

That note from Tony also contains the definition of what is stored in the persistent representation of an LCIO track: From Rob Kutschke

This note is embedded in a broader discussion about tracks rooted at: Evolving the LCIO Track Class

As I understand it, our working proposal is:

...