1 / 14

Analysis code for KEK Test-Beam

Analysis code for KEK Test-Beam. M. Ellis Daresbury Tracker Meeting 30 th August 2005. Requirements. Online: Monitoring – higher level than that provided by UniDAQ (i.e. using reconstruction) Event display Offline: Calibration Alignment Reconstruction (hits, points, tracks)

fraley
Télécharger la présentation

Analysis code for KEK Test-Beam

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Analysis code for KEK Test-Beam M. Ellis Daresbury Tracker Meeting 30th August 2005

  2. Requirements • Online: • Monitoring – higher level than that provided by UniDAQ (i.e. using reconstruction) • Event display • Offline: • Calibration • Alignment • Reconstruction (hits, points, tracks) • Event display • For the moment, only discussing the tracker.

  3. G4MICE • Software package for MICE. • Not just Simulation!!!! • Greatly extended in recent months to include: • Ability to create user applications that can use any components from the G4MICE libraries. • Ability to read in August cosmic ray data. Similar converter will be written for KEK data format. • Ability to produce and use calibration information for VLPCs (pedestals and gains). • Ability to decode electronic space to physical space for VLPC hits (incomplete at the moment).

  4. Online Plans • G4MICE application runs on a machine that can see the current or previous runs. • Application produces PAW histograms. • Histograms are accessed through a PAW session in the same style as for the MuScat online monitoring.

  5. Parameters to Monitor • Multiplicities (hits, clusters, points, tracks) • For everything except tracks, both integrated and per plane values will be monitored. • Fibre number distributions (for each plane) • Light yield distributions (for each plane) • Light yield with tracking (for each plane) • Distributions of space point positions per station (2D histograms) • When there is magnetic field: • Momentum (PX, PY, PZ, P) • Anything else? Ask now...

  6. Event Display • Another G4MICE application. • Currently displays hardware and low level SciFi hits (doublet clusters). • Will be extended to show space points and tracks.

  7. Offline - Calibration • Application to produce histograms for each channel (one with no LED pulser, the other with) works. • Kumacs have been written to perform a fit to the pedestal and first PE peak. • Preliminary results look reasonable, however there are some channels for which the fit fails, this needs to be improved.

  8. Offline - Alignment • Requires CMM information for first version and as a minimum space point reconstruction. • In principle will not be too difficult for the no-field case.

  9. Offline - Reconstruction • Low level classes are separated (raw hit on a VLPC channel versus simulated Monte Carlo hit). • Both classes can be used to make a “SciFiDigit”. • Reconstruction from Digits to Clusters, Space Points and Tracks is independent of data type. • Once raw data reading, decoding of cable information and calibration is validated, then the rest of the code will work without modification.

  10. Work done and Needed - 1 • Read raw data (cosmic ray format) • Read raw data (KEK format) • Produce calibration information • Use calibration information • Produce decoding information for old stations • Produce decoding information for new stations • Use decoding information on old stations • Use decoding information on new stations √ X √ √ √ X √ X

  11. Work done and Needed - 2 • Create user applications • Write PAW HBOOK files • Reconstruct higher level objects from raw data classes • Visualise experimental setup • Visualise clusters • Visualise points, tracks, etc... • PR and Track Fit (Straight Line) • PR and Track Fit (Helix) √ √ √ √ √ X √ √

  12. Work done and Needed - 3 • Correct representation of KEK setup in all phases of G4MICE • Correct use of Magnetic Field Map • Obtain field map for BESS solenoid • Extrapolation to other detectors • Monitoring application • Kumacs for monitoring application • Produce alignment information • Use alignment information X X X √ X X X X

  13. TOF and CKOV • G4MICE code for TOF and CKOV far less developed than that for the tracker. • Aron Fish has taken over G4MICE responsibilities for the TOF. • Need to develop all levels of reconstruction in G4MICE for TOF and CKOV data. • Unless deemed urgent, I’ve assumed that it can be done at a “relaxed” pace once the tracker code is ready. UniDAQ monitoring should be sufficient to ensure correct operation of TOF and CKOV detectors.

  14. Conclusions • Much progress in the past few months. • Still a LOT to be done in the remaining weeks...

More Related