1. 1 G4MICE Malcolm Ellis SciFi Tracker Meeting, KEK Thursday 31st March 2005

2. 2 Outline  G4MICE or “disposable” code?  Issues for Tracker test in May: Calibration and Alignment Calibration and Alignment Decoding raw data Decoding raw data Tracking in no field and solenoid field Tracking in no field and solenoid field Emittance calculation? Emittance calculation? Online monitoring? Online monitoring?  G4MICE solution: Switch for staging Switch for staging Work needed between now and mid-May Work needed between now and mid-May  Conclusions

3. 3 G4MICE vs “disposable” code  For the cosmic test, a small amount of code was written for decoding and reconstructing the data, but it can not be easily re-cycled.  We have the option of either writing new dedicated code for the test-beam, or working within G4MICE to extend it to include what we need for the test-beam.  I would prefer to use G4MICE for all the monitoring/analysis needs of this and future test beams.

4. 4 Issues: Calibration & Alignment  Need code/data to determine and store calibration constants (pedestals and gains), possibly time-varying?  Alignment information, initially from CMM, and later from data.  Old cosmic code had a simple ability to handle both.  Current G4MICE only has a simple alignment system, but can be extended to cover both needs.

5. 5 Issues: Decoding raw data  Raw data will be written in some (yet to be defined) format that contains ADC information as a function of MCM and Channel number.  Decoding information to take this data and relate it to Station/Plane/Fibre bundle will of course be needed.  G4MICE does not have this facility yet, but it can be easily added.

6. 6 Issues: Tracking  G4MICE tracking currently only considers a solenoid field.  Old cosmic code only considers straight line fit.  G4MICE can be extended to include a straight line track fit (Kalman package allows this easily).  New pattern recognition code will be needed, and some sort of switch for the Reconstruction to select which type of fit to do.  Field strength is already variable via a data-card, so perhaps if we set it == 0, then that means do a straight-line fit?

7. 7 Issues: Online monitoring  We need to make a list of what kinds of parameters/plots will be monitored during data- taking.  It should be possible to run code in the control room on data (either old runs, or as it comes in) to monitor data quality, as well as to perform calibration, alignment, etc...  What kind of interface does the user need for the online monitoring? A screen that has buttons to select histograms (in PAW for example) is one option.  Visualisation? An event display may be useful...

8. 8 G4MICE Solution  Although it will require some work, I think the optimum approach is to extend G4MICE to allow it to perform all tasks needed for the test in May.  In order to do this, we have already forseen the need for an option which selects the “stage” or “phase” (like MICE stage III, stage IV, etc..). Yagmur is currently working on this.  Once this is ready, there is a minimum set of work required to allow simulations of the test- setup (in conjunction with the G4BL work) and then further work to allow analysis/monitoring...

9. 9 Work Needed 1. To enable Simulation work: 1. Switches 2. Modified geometry (SciFiGeomDecoder) 2. To allow analysis/monitoring: 1. Extension to allow Calibration and Alignment 2. Ability to decode raw data 3. Add straight line model and PR for tracking 4. Develop “user” applications to perform specific tasks (calibration, alignment, etc) 5. Monitoring application (in addition to UniDAQ)? 6. Visualisation?

10. 10 Conclusions  G4MICE can be extended to allow a simulation of the KEK test as well as analysis of the real data.  First priority is to enable simulation effort.  Second priority is develop analysis tools similar to cosmic analysis in G4MICE.  Not much time left for these tasks, especially as my “MICE time” will still be minimal over April...