Agenda
- A working discussion of GCRTrack and GCRSelect layouts flowchart class diagram
- How do they fit into existing recon?
- Inputs?
- What do they do (i.e. what are the functional "boxes" in the flow chart)?
- How do they talk to each other?
- Outputs
- Any other questions from Claudia and Fred (or anyone else)
- What next for GCRTrack and GCRSelect?
- Eric N. GSI analysis update
Attendees
Mark Strickman
Claudia Lavalley
Fred Piron
Sasha Chekhtman
Zach FewtrellEric Grove
Andrey Makeev
Benoit Lott
Eric Nuss
Notes
GCR Recon Discussion
- Do we assume that GCR Recon will take place in a separate "pipeline" from normal processing?
- Dedicated GCR pipeline Con:
- On one hand, much of the processing (TKRRecon CalXtalResponse) is the same as normal events
- Using same pipeline may mean that output could be in standard recon.root file (same file as normal events)
- Dedicated pipeline means a new root file (GCRRecon.root) would be required (maybe same format as recon.root)
- Dedicated GCR pipeline Pro:
- Rerunning GCR alone is more difficult (especially a problem early on)
- Full recon.root is quite large => alot of unnecessary reads
- In general, retrieval from a smaller, dedicated GCRRecon.root file would be easier
- GCRRecon.root could be merged into recon.root later if necessary
- General consensus is that dedicated GCR pipeline is desireable
- Dedicated GCR pipeline Con: