1 / 29

Sci Fi Simulation Status

Sci Fi Simulation Status. Malcolm Ellis MICE Meeting Osaka, 2 nd August 2004. Outline. Status at last collaboration meeting Progress since April: dE/dx in track fit addition of fibres as measurements pattern recognition current performance momentum resolution efficiency/purity

calix
Download Presentation

Sci Fi Simulation Status

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. Sci Fi Simulation Status Malcolm Ellis MICE Meeting Osaka, 2nd August 2004

  2. Outline • Status at last collaboration meeting • Progress since April: • dE/dx in track fit • addition of fibres as measurements • pattern recognition • current performance • momentum resolution • efficiency/purity • To-do/priority setting

  3. Status at CERN Meeting • Prototype data had been analysed, light yield, efficiency, dead channels and resolution matched expectations. • Specifications for next station used in G4MICE, light yield, dead channels, etc matched in G4MICE to prototype. • Lack of time had meant some improvements predicted at Abingdon meeting had yet to be implemented...

  4. Beam/Backgrounds • All plots presented in this talk were produced with the following conditions: • Beam: Default G4MICE beam • RF Background: 0, 0.1, 1 and 10 times expected rate (100 impossible due to file size) • Detector description: current design, as reported at CERN • Only modification in datacards was to vary the RF background rate (see next slide) • Hope to start using beam from G4Beamline once I have time to work with Kenny on this (not before September).

  5. Sample datacards Due to file size limitation (max 2G) did not achieve 50k events for large background rates. 0.25% Dead channels as before Same RF background model as before Modify RF Background rate • numEvts 50000 • SciFiadcFactor 6.0 • SciFiFiberConvFactor 3284.0 • SciFivlpcEnergyRes 2.0 • SciFiMUXNum 7 • TPGMode Off • SciFiDeadChanFName nom.dcl • rfBGSource gamma • rfBGPhotonModel Uniform • rfBGNumberOfPhotons 10 • rfBGDirection 1 • rfBGPhotonEnergy 10 • rfBGTimeWindow 100 • rfBGTimeDelay -15 • rfBGZstart -5650 • rfBGRadius 150

  6. Progress since April • Improved model of dE/dx in the energy range of interest has been added to the Reconstruction for use by the Kalman package • Prototype code to add clusters as measurements in the track fit. Can not be used fully until after the design iteration • Pattern recognition improved to enhance purity of muon track selection • Code still does not “talk” to PID detectors, this will not happen until design-iteration is carried forward...

  7. dE/dx in Kalman • Kalman package can accept a table of mean dE/dx as a function of total momentum. • Currently, does not differentiate between particle types. • dE/dx versus P determined from GEANT4 and fed into Kalman for use in Reconstruction

  8. Clusters in Track Fit • A space point (triplet) consists of three clusters, each describing a line in a Sci-Fi plane. • These clusters can be added to the track and used in the fit as individual measurements, rather than as the 3D space point of the intersection. • This allows efficiency to be recovered by adding 2 or even only 1 cluster per station to the track fit (next version).

  9. Pattern Recognition • Proceeds as before, only changes are extra cuts to remove background and reduce CPU use. • Find clusters • Build space points (only triplets) • Find straight tracks and lock off points • Find best helix • Fit helix

  10. Space Points (Triplets) • A triplet should be three clusters (one in each view) which intersect in space and time • Pattern recognition checks the geometrical alignment of the three fibres, as well as the difference in time between them as recorded in the TDCs

  11. Triplet Finding

  12. Straight Tracks • PT distribution shows a lot of RF induced background are essentially straight tracks • Use this to select potential straight tracks and lock the points off so that they will not be considered when searching for a helix • This produces a massive saving in CPU use for high RF background • Potential for use of a better track model that does not need to differentiate between “straight” and “curved” tracks – see Ken’s talk.

  13. Straight Tracks

  14. Muon Track Recognition • Pretty much as before: • Pick three points • Determine the circle parameters • Check TDC information is consistent • Look for a 4th or 5th matching point • Fit track using Kalman filter • Pick track with best c2. • Use of the old MINUIT based code is gradually being phased out. • By the time we move to the design iteration version, it will not be used at all...

  15. Current Performance • All plots following are with the expected amount of RF background, 0.25% dead channels, conservative light yield, etc, etc... • Result purely Sci Fi, no matching to particle ID detectors for PR or Particle ID (require design-iteration code for that) • Position resolution effectively unchanged (slight variation due to new fibre spacing): ~400 mm • RMS values quoted versus RF level at end...

  16. PX Resolution – 6.0%

  17. PY Resolution – 6.7%

  18. PZ Resolution – 1.9%

  19. PT Resolution – 4.7%

  20. X’ Resolution – 7.4%

  21. Y’ Resolution – 7.8%

  22. T’ Resolution – 0.5%

  23. Track-Finding Efficiency

  24. Track Purity – 99.8%

  25. Variation with RF

  26. Magnetic Field versus P? • Test the hypothesis that as the tracker is m/s limited, there is no advantage to be had by lowering the solenoid field if the mean momentum is lowered. • Simulated 160 MeV/c muons at 4T and at 3.2T, compare momentum resolution...

  27. 160 MeV/c – 4T 10.6 % 13.7 %

  28. 160 MeV/c – 3.2T 6.5 % 8.0 %

  29. To-do / Priority Setting • Using a realistic description of tracker, background, etc, performance is better than 10% required. • Purity is very high. • Efficiency of PR requires more work. • Further major improvements will not be made without moving to the new design and taking it forward. • Question – is the performance of this code (in CVS already) sufficient for other work (e.g. emittance calculation) to carry on? • If so – as much effort as possible should be directed towards the new design.

More Related