1 / 12

ARCs cut definition for TEC modules

ARCs cut definition for TEC modules. Javier Fernandez Menendez Institut für Experimentelle Kernphysik Karlsruhe University TEC meeting 14 th July 2004. ARCs TEC Data on the web. R1 : 31N + 19S from Hamburg R2 : 21S + 26N from Wien (problem in 2 APVs)

preston
Télécharger la présentation

ARCs cut definition for TEC modules

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. ARCs cut definition for TEC modules Javier Fernandez Menendez Institut für Experimentelle Kernphysik Karlsruhe University TEC meeting 14th July 2004

  2. ARCs TEC Data on the web • R1: 31N + 19S from Hamburg • R2: 21S + 26N from Wien (problem in 2 APVs) • R3: 31 from Ka + 23 from Ham (x-check) • R4: 26 modules from Zurich • R5: not enough statistics yet in community… • R6: 23 from Aachen • R7: 24 from Strasbourg Total: ~230 modules = ~2.5Gb of data in files Javier Fernandez (IEKP/UniKa)

  3. What cuts can be defined? Healthy Statistical and graphical criteria Not use APV border channels for cuts definition Noisy Pinhole Open Javier Fernandez (IEKP/UniKa) No statistical criteria here: tagged as bad channels anyway in DB

  4. Methodology Noise for all modules from one geometry in one single APV mode Javier Fernandez (IEKP/UniKa)

  5. Methodology: an example Border Channels: 1,2, 128, 129, 255, 256, 384, 385, 511, 512 1.3 (~4s) 0.9 (~4s) Next to border channels: 127, 130, 254, 258, 383, 386 Symmetric 4s cut from mean for healthy region definition Javier Fernandez (IEKP/UniKa)

  6. Final result of cuts Noisy channels perfectly tagged!!! Healthy region 1.3 (~4s) 0.9 (~4s) Still room for fluctuations (4s = 99.95% probability) Javier Fernandez (IEKP/UniKa)

  7. Summary of noise 4s cuts Stereo and Normal R1 show ~equal noise values Noise and cuts increase with R# Javier Fernandez (IEKP/UniKa)

  8. R2 modules problem Lower average noise in central APVs Effect not seen in other geometries with 6 APVs (R1 and R5) Javier Fernandez (IEKP/UniKa)

  9. It makes distribution not gaussian Not-central APVs contribution Central APVs Javier Fernandez (IEKP/UniKa)

  10. Not an apparent Wien test problem PIO PIOn R2 Module 26690 DIO DIOn Wien Karlsruhe Javier Fernandez (IEKP/UniKa)

  11. Not an apparent Wien test problem PIO PIOn R2 Module 26697 DIO DIOn Wien Aachen Javier Fernandez (IEKP/UniKa)

  12. Conclusions • There is a clear behavior difference between: channels at the borders of the APV and channels next to channel border • Noise cutsdefined/confirmed for TEC mods. • Program mainAnalyzer (in DefAna package) allows to redefine them in an easy way if needed and do extensive module analysis/comparisons • Noise ~equal in stereo and normal modules • Statistical gaussian method: first iteration • 4s symmetric criterium maybe too tight ? • But 5scould be too loose in some cases… Javier Fernandez (IEKP/UniKa)

More Related