For GCR, can we do CalXtalAlg -> GCRRecon or do we have to do CalXtalAlg -> 0TKRRecon -> CALRecon -> TKRRecon -> CALRecon -> GCRRecon (similar to curren recon)?
Do we need to find Z in GCRTrack? It's required for MIPfinder (since MIPfinder needs energy), but we may only need MIPfinder in track if we can't use TKR (Fred thinks Z might be useful in Track)
We may want to set flags in Track that get monitored by filters in Select
Benoit suggests a root macro "toy" version of code to study algorithms. Could also be a UserAlg. Andrey and Eric N.'s work to date are steps in this direction
GSI Analysis Status (see Eric N. presentation above)
Fred is creating a roottreeanalysis to apply Erics analyses to simulated data
Sasha is surprised at the pattern in layer to layer energy deposition using full calibration. Could layer indexing be wrong? He'll check. Could be that one end uses X0-X3,Y0-Y3, the other uses X0Y0X1Y1...
Sasha also points out potential problem from big diode to small diode xtalk, since for Si, LEX1 is heavily saturated meaning serious xtalk to HE. Could try same analysis with Carbon, where LEX1 would not be saturated, but Eric N. points out that beam spreading is a problem.
Actions
Suggest refinements/changes to flow of GCRSelect (Fred et al)
Redo GCRTrack boxes in flow chart (Mark)
Redo GCRSelect boxes in flow chart based on Fred suggestions (Mark)
Revise "ID and Copy" box to make understandable (Mark)
Contact ISOC re work flow (Mark)
Contact Tracy (again) re TKRRecon (Mark)
Check on layer order in GSI analysis/calibration (Sasha, Eric N.)