Tracker Software Status M Ellis MICE Collaboration Meeting

Tracker Software Status M. Ellis MICE Collaboration Meeting 27 th June 2005 1

Outline • Simulation/Offline code (G 4 MICE) – New domains – Progress so far – Plans • DAQ/Online code – AFEII code – Plans • Conclusion 2

Simulation/Offline code • Reminder: “G 4 MICE” does NOT just refer to simulation, but to all offline code that is held under a single CVS repository. • No changes have been made to any of the core tracker code since Berkeley. Work has been towards the use of G 4 MICE as a tool for analysis of cosmic/test-beam data. • Also aim to complete station spacing study before next collaboration meeting. 3

New Domains • Additions to G 4 MICE to add functionality needed for analysis of test-beam data: – Calibration and Alignment information – Decoding information (to go from electronic channel space to physical space on the detector) – Visualisation (event display) – More flexible ability to produce applications (executables) 4

5

Progress so far • G 4 MICE has been extended to handle calibration, alignment and decoding information. Further work is needed before it will be ready to be committed. • Visualisation framework has been developed (based on the libsx wrapper of X) with a simple test program that can be extended to handle both test-beam and simulation needs. • Pattern recognition and track fitting code modified to work with no magnetic field. 6

Visualisation 7

Work still needed • Alignment scheme still needs to be fully implemented. • Once raw data format is defined, converter code in G 4 MICE is needed to read it and create low level C++ classes. • “Applications” domain to allow users to create purpose-specific executables (e. g. perform calibration, alignment, etc. . . ) 8

Plans • Due to lack of effort available, G 4 MICE activities will take a second priority to testbeam readout until it is finished. • At that stage, work described so far will be completed, hopefully in time to be used for monitoring and analysis of test-beam data. • If time is available, still aim to study optimum station spacing before next collaboration meeting. 9

DAQ/Online code • Unidaq was used successfully at the KEK test beam for the readout of CAMAC and VME ADCs and TDCs (see Makoto’s talk). • VLPC readout requires specialist code to control the different components: – 1553 – SASEQ – VLSB • C/C++ code has been developed based on existing framework (Excel/Visual Basic) used by D 0 for testing. 10

AFE II code • Code currently exists to perform most needed functions: – Initialisation of the board (including programming FPGAs, TRIP chips, etc). – Control of the SASEQ (to select Idle, Acquire or Trigger modes). – Readout of the AFE II board over the LVDS link • Code currently only reads out one board (not a big deal to make it read out N). • Code currently cannot correctly load FPGA firmware correctly. There is some byte/word order problem which needs to be addressed. 11

AFE II readout • Hardware required: – – – Linux PC VME crate SBS Bit 3 Interface 1553 controller SASEQ VLSB 12

User Interface • Written in Qt, basic interface with a selection of buttons to perform operations and colour coded to report error (green = good, red = bad). • Able to take a single event, or multiple events, and write to an ASCII file in the same format as used earlier for AFEII testing/debugging. • Needs to be integrated with the Uni. Daq side before the next KEK test-beam, but has already been used to read pedestals. 13

Screen shots: 14

Pedestals 15

Plans • Work at D 0 is continuing, aim to have a complete system test including calibration and cosmic-ray data taking by the end of July. • DAQ code will be extended to read out several AFE boards and fix checksum problem. • Once hardware/software system has been validated, hardware will be shipped to KEK, software will then be ready to be integrated with Uni. Daq system. 16

Conclusions • Despite unavoidable delay in originally planned schedule, much progress has been made on the online code for the tracker. • G 4 MICE efforts have suffered due to the usual lack of mouse-power (<<insert regular plea for more effort here>>). • Still plan to use G 4 MICE for monitoring and analysis of test-beam activities at KEK. 17