Presentation is loading. Please wait.

Presentation is loading. Please wait.

MuTrg/Mutr Optimization Yoshi-mitsu Imazu. ● Mutr Lv1 timing scan Adjustment of Lv1 timing Online/Offline shape cut values ● Mutrg threshold scan → Better.

Similar presentations


Presentation on theme: "MuTrg/Mutr Optimization Yoshi-mitsu Imazu. ● Mutr Lv1 timing scan Adjustment of Lv1 timing Online/Offline shape cut values ● Mutrg threshold scan → Better."— Presentation transcript:

1 MuTrg/Mutr Optimization Yoshi-mitsu Imazu

2 ● Mutr Lv1 timing scan Adjustment of Lv1 timing Online/Offline shape cut values ● Mutrg threshold scan → Better noise suppression (noise vs charge efficinecy) DCM (Online) lower bound release going to applied? → Better Hit distribution (charge eff. & reconstructed position) Tools: Private Tree, or QA hist → READY Tools: Noise Data & Private Tree (charge efficiency) → READY ● Rough GTM scan → Better trigger efficiency (more hit in 3 window) Order Acceptable noise rate (SG1) Plane Noise Rate Trigger Rate consistency check Tools: Mutrg Hit Histo (MutrgCalibAna) & Analysis → READY Sample: ~500k MuID per Lv1 Sample: ~500k MuID per thresh., Mutrg: LOGIC=OR and AND2 in st0 Width=1? Sample: 200k MuID per point., Mutrg: LOGIC=OR and AND2 in st0 Width=3(1) Note relative ratchet timings (backup)

3 Lv1 = 4, 5, 6, 7, 8 Sample: ~500k MuID per Lv1 Lv1=5Lv1=7 Plane1 (Non-stereo) Plane0 (Stereo) Plane1 (Non-stereo) Plane0 (Stereo) [BCLK] ● ~2 BCLK difference between stereo and non-stereo planes Pkstrip in TrkAss Clstr, South [oct summed, no cut on trk] (Run11 Commissioning) Timing Distribution: NOT IN QA plots NOT IN QA plots ● Mutr Lv1 timing scan (run12: elog 952)

4 (ADC2 – ADC0)/ADC2 for Pkstrp in TrkAss Clstr, South [oct summed] Plane1 (Non-stereo) Plane0 (Stereo) (Run11 Commissioning) Lv1 = 5 Lv1 = 6 Lv1 = 7 Lv1 = 8 Lv1 = 9 Note: Non-stereo plane 1-2 BCLK DELAYED against stereo plane by Mutrg FEE installation Upper cut Lower cut Upper cut Lower cut Tuned for non-stereo (Red) (Run11-12 setup) Sampling timing: Pushing Backward Sampling timing: Pushing Forward → Shape recovery by pushing lv1 backward → Recovery from lower edge IN QA plots

5 “Pkw” of TrkAss Clstr, South [clsz>1, oct summed, no cut on trk] (Run11 Commissioning) Lv1 = 5 Lv1 = 6 Lv1 = 7 Lv1 = 8 Lv1 = 9 pl0 pl1 pl0 pl1 pl0 pl1 pl0 pl1 pl0 pl1 Looks like ~2BCLK diff btw pl0 & pl1 (# pl0 / # pl1 = 0.95) (# pl0 / # pl1 = 0.85) (# pl0 / # pl1 = 0.65) (# pl0 / # pl1 = 0.40) (# pl0 / # pl1 = 0.30) ● Non-stereo stereo diff. explained by Timing diff (or impact of shape cut1) ● Lv1 should be optimized on stereo plane (earlier signal) as far as non-stereo kept away enough from upper bound (impact on Q ~ few % only) IN QA plots

6 “Clsz” of TrkAss Clstr, South [oct summed, no cut on trk] (Run11 Commissioning) Lv1 = 5Lv1 = 8 pl0 pl1 pl0 pl1 (# pl0 / # pl1 = 1.00) (# pl0 / # pl1 = 0.70) Lv1 = 6 Lv1 = 7 Lv1 = 9 pl0 pl1 pl0 pl1 pl0 pl1 Looks like ~2BCLK diff btw pl0 & pl1 (# pl0 / # pl1 = 1.00) (# pl0 / # pl1 = 0.95) (# pl0 / # pl1 = 0.50) ● Non-stereo stereo diff. explained by Timing diff (or impact of shape cut1) ● Lv1 should be optimized on stereo plane (earlier signal) as far as non-stereo kept away enough from upper bound (impact on Q ~ few % only) IN QA plots

7 ● Zero Suppression off data for parameter adjustment? ● Zero Suppression off noise data for recap effect? Few minutes with clock trigger At various BBC rate circumstances Sample: ~500k MuID at a (optimized) Lv1 Ex. run328750

8 ● Mutrg threshold scan (run12: elog 971) Sample: ~500k MuID per thresh., Mutrg: LOGIC=OR and AND2 in st0 Width=1 All OR: 10mv 20mv 30mv 40mv 50mv 60mv 80mv AND2 in St0 + Others OR: 10mv 20mv 30mv 40mv 50mv 70mv 90mv Main Targets Avoid This! Hit Timing Dist. (MuID cosmic sample) Large Baseline Contrigution: Threshold too low → provide non zero hit rate even at BBC=0

9 ● Rate suppression has priority ● Chrg. Eff./Hit Rate → Constant as threshold goes infinite? ● Better plots will be from Minjung

10 ● Rough GTM scan (run12: elog 939) Scan over 0, 20, 40, 60, 80, (100) [ns] Mutrg at optimized logic/thresholds Width=3 or Width=1 -> 3 offline Latency=32, trigdelay=10, (MRG reset) delay = 1(North), 2(South) No fiber! rdel_s cdel_s rdel_n cdel_n Delay[nsec] 0 0 0 0 0 0 125 0 125 21.1 0 255 0 255 42.9 1 109 1 109 58.1 1 229 1 229 78.4 2 161 2 161 106.7 Check stability of LL1/GL1 efficiency After final timing adjustment with fiber (remember south behavior last year)

11 backup

12 Black: Lv1 Delay 7 Red: Lv1 Delay 6 Green: Lv1 Delay 8 ADC height ∝ ΔE 0 5 6 7 Lv1 Delay (BCLK) MuTr/MuTrg GTM GL1 MuTr Latency (fixed) 0 5 6 7

13

14

15

16 Picked up #emu fire @timing4 per 5k MuID (~100s) sample Survey its time development over run by segmenting data into 5k MuID samples

17 South Oct2 (0 origin) ● ~0.03Hz ave. → more less accidental rate of SG1_S & MuID (~0.05-6Hz) ● South Oct2 one of dominant source of SG1_S fire? ~0.03Hz ● Looks no obvious spikes


Download ppt "MuTrg/Mutr Optimization Yoshi-mitsu Imazu. ● Mutr Lv1 timing scan Adjustment of Lv1 timing Online/Offline shape cut values ● Mutrg threshold scan → Better."

Similar presentations


Ads by Google