1. Tracker Software 1M.Ellis - CM23 - Harbin - 15th January 2009  Four key areas that currently need some work: u Digitisation u Decoding files u Unpacking DATE data u Helix Kalman fit

2. Digitisation  Now that we have calibration and decoding for the first MICE tracker the digitisation is going to be enhanced: u Read in actual calibration and cabling files. u Use these to generate ADC values with the same pedestal and gain as the real VLPCs. u Take into account the real dead channels in the tracker.  As a result, when we compare the light yield plots per plane between MC and data, it should be possible to achieve a very good agreement. 2M.Ellis - CM23 - Harbin - 15th January 2009

3. Decoding Files  The solution to the waveguide issues shown in CM22 has been done by Hideyuki in his own particular format.  G4MICE can read this (and an earlier format that he also produced), but neither are very flexible in terms of swapping waveguides or AFE boards.  So the 3 correct decoding files that we currently have for the R8 cosmic ray test need to be moved to the “Imperial” format and put in CVS. 3M.Ellis - CM23 - Harbin - 15th January 2009

4. Unpacking DATE data  G4MICE can read the data produced by DATE and extract the payloads that correspond to a given VME device.  Other code in G4MICE can take the blocks of data from the 4 VLSB memory banks and turn them into VlpcHits for reconstruction.  The final step is to add the code to the unpacking library and to the classes that handle DATE data to extract the hits from the DATE files.  This can be tested in advance of the next cosmic ray test as I think Hideyuki took some data with DATE last year. 4M.Ellis - CM23 - Harbin - 15th January 2009

5. Helix track fit  Aron’s thesis analysis on the KEK test beam data has shown a very strange issue where only a small sub-set of tracks found by the pattern recognition are being successfully fitted by the RecPack package.  To date this has not been seen in the standard Unit Tests, nor in the simulations of MICE Stage 6, and so it is likely some subtle bug that has not been covered by our tests.  Need to understand the cause and fix this urgently. 5M.Ellis - CM23 - Harbin - 15th January 2009