Tracker Specific Software

1. Tracker Specific Software • Offline • Modeling • Simulation • Digitisation • Reconstruction • Online • Calibration • Alignment • Decoding • QA/Fabrication requirements • AFEIIt firmware and DAQ issues • Event Display • WIRED • Next Steps Malcolm Ellis - Tracker Meeting - 6th August 2006

2. Modeling • Current model of the tracker in G4MICE includes: • All fibres (core and two layers of cladding) • Glue • mylar sheet • Spectrometer cylinder • coils (calculating fields from currents) • Current model does NOT include: • carbon fibre supports • carbon fibre station • wave guides • patch panel • connectors • internal engineering details of spectrometer solenoid • VLPC cryostat/electronics/pumps/etc... Malcolm Ellis - Tracker Meeting - 6th August 2006

3. Modeling – Next Steps • Makoto and Hideyuki have agreed to do some work on the G4MICE models: • CKOV (first priority) • Spectrometer solenoid (second priority) • Aim to include more realistic implementation of the material inside the spectrometer, including the wave guides and other material that may be important when studying the downstream PID detectors. • Would be useful to have a consensus on what is needed in the upgraded model to avoid wasting time and effort on fine details... Malcolm Ellis - Tracker Meeting - 6th August 2006

4. Simulation • Simulation (with regards the tracker) has not changed for some time. • Recent work has included an upgrade of the BeamTools/Optics code to support the new MiceModules scheme. • Only tracker-related work required at the moment is the testing and upgrade of the RF background simulation. • Rikard and Terry will work together to modify the RF background routines so that there will no longer be the need for post-processing after performing an RF background simulation job. • Hope that this will be completed and released by the end of the upcoming software workshop (Fermilab after NuFact06). Malcolm Ellis - Tracker Meeting - 6th August 2006

5. Digitisation • Digitisation of the tracker has remained unchanged for over a year. • Once we have one or more concrete schemes for using the AFEIIt boards in MICE, the expected output style and any effects due to rate increases can be implemented. • It is expected that this work may be done by IIT (Terry) after the RF background work is completed and once a realistic readout scheme has been developed and tested. Malcolm Ellis - Tracker Meeting - 6th August 2006

6. Reconstruction • Most of the reconstruction has remained unchanged so far this year. • There are two major areas of work for the upcoming data challenge: • Better seed for the Kalman fit. • Ability to “swim” Kalman states through a field map. • Aron has already started working on an improved seed (see his talk). His algorithm is being tested in Monte Carlo and will be used to finish the analysis of the KEK test beam data and compare with the Osaka group’s analysis. • The ability to propagate tracks through a non uniform magnetic field exists in the RecPack package, however appears to have one or more problems. • I am in the process of debugging this with assistance from the developers as well as Jon Paley from Indiana who is using this package for the MIPP experiment. • The aim is for a release of the Reconstruction that includes the new seed to be made at the end of the software workshop at Fermilab and a release with track swimming at the software workshop before the CM at RAL in October. Malcolm Ellis - Tracker Meeting - 6th August 2006

7. Calibration • The calibration code and data files scheme were implemented in G4MICE last year and have not been changed since. • Unless there are new requirements, not foreseen last year, this should prove adequate initially for the QA/construction process and for phase 1 data taking. • We should still give consideration to the requirements of a conditions data base and associated calibration/etc for all detectors as part of the overall process of defining the DAQ and slow controls and monitoring scheme. • Perhaps the tracker group can give this some more thought in preparation for the DAQ workshop at DL at the end of September? Malcolm Ellis - Tracker Meeting - 6th August 2006

8. Alignment • The MiceModules scheme was designed with the requirements of detector (as well as beam line and cooling channel components) alignment in mind. • The scheme allows for arbitrary rotations and translations of any component with respect to any other. • The analysis of the KEK data done by Aron for the last CM was the first use of this scheme, and translations were determined from the real data and applied to the model of the KEK tracker. • With a more refined analysis, we should be able to look for rotations in a similar manner to the analysis performed by Hideyuki. • Some thought should be given to how the results of the CMM measurements and surveys that are made once the tracker(s) are installed will be fed into the relevant models. Malcolm Ellis - Tracker Meeting - 6th August 2006

9. Decoding • This has been a long term issue, but would appear to be approaching a conclusion. • Takashi has determined a set of decoding files (and produced corresponding C++ code) based on the logs of the tracker fabrication and the results of the “autopsy”. • This decoding should be able to be compared with that produced by Hideyuki and in addition will allow Aron to study light yield as a function of wave guides/patch panel connectors/etc. Malcolm Ellis - Tracker Meeting - 6th August 2006

10. Decoding Requirements? • Disclaimer: I’ve not had a chance to look properly at Takashi’s code (due to the computing problems at IC) • I’m under the impression that the code, while delivering the required mapping from any part of the readout chain to any other part, does so from data files that have folded into them multiple stages of the readout sequence. • By this, I mean that there are not separate files (or parts of a file) to describe, for example, each waveguide as an independent entity. • IF this is the case, then I think it is necessary for the tracker group to decide the exact requirements for the decoding code. • If what has been done so far is going to be adequate, then we will just import it into G4MICE. • If not, then we may be able to finish this work off at IIT (some summer students) thus freeing up Takashi for other tasks. Malcolm Ellis - Tracker Meeting - 6th August 2006

11. QA/Fabrication Requirements • This slide is really a request rather than a statement or report. • Presumably we will require software to perform the QA process and possibly other parts of the tracker fabrication. • Assuming that we wish to use the software tools on station 5 that will be used for the “real trackers” (or if not, then something close), we need to define exactly what is required of any software (other than that already being developed to drive stages, measure signals from CCD cameras, etc). Malcolm Ellis - Tracker Meeting - 6th August 2006

12. AFEIIt Firmware • The past month has seen progress at FNAL and RAL. • Terry Hart and Bill Luebke have been working with the D0 experts on new firmware for MICE. • They have made progress on a scheme that will cause the discriminator bitmap pattern to be used to selectively digitise only those channels that are above threshold. • It is hoped that this will allow a greater rate of events to be recorded without compromising on the quality of the analogue data that is recorded. • At RAL Craig has setup a test stand that has all the equipment required for testing and fixing AFEIIt boards for MICE. • We have successfully performed the complete power up and initialisation of a production board and using firmware supplied by FNAL (Tom Fitzpatrick) applied a software trigger and readout data through the 1553 interface. • Once updated firmware to allow readout over LVDS is available this will be tested on the stand at RAL. • Senerath will be assisting with the Firmware development at RAL and will use the test stand in order to test the firmware. Malcolm Ellis - Tracker Meeting - 6th August 2006

13. AFEIIt Board at RAL Malcolm Ellis - Tracker Meeting - 6th August 2006

14. Event Display • With the release announced at the past collaboration meeting, there is a new interface to allow visualisation. • This code currently writes a HepRep XML file that can be visualised by programs such as WIRED. • The code currently only draws the geometry that has been defined in the MiceModules. • The HepRep format allows for the visualisation of tracks, hits, space points, etc (including the ability to “pick” such objects to find out their attributes). • At some stage we need to implement the additional code required to take Monte Carlo and reconstructed objects from the MICEEvent and extract the physics quantities and write these out into the HepRep file. • Any volunteers? Malcolm Ellis - Tracker Meeting - 6th August 2006

15. WIRED Display Malcolm Ellis - Tracker Meeting - 6th August 2006

16. A Picked Object Malcolm Ellis - Tracker Meeting - 6th August 2006

17. Next Steps • If possible at this meeting, it would be good to get some “official” requirements on paper for the tracker-related software. • Specifically: • What is required in the model of the tracker and solenoid (and to what detail/precision)? • What additional requirements (if any) are there for the Calibration code? • In what format will the CMM and survey information be provided and how do we put this into G4MICE? • What situation do we require with regards to the decoding? • What sort of things do we need the software to do in order to help with the QA and tracker fabrication? Malcolm Ellis - Tracker Meeting - 6th August 2006