- Indico style
- Indico style - inline minutes
- Indico style - numbered
- Indico style - numbered + minutes
- Indico Weeks View
Timing, Fill Pattern and Bunch Currents
Frontend Performance, RHU, Electronics for calibration & efficiency studies
Frontend Performance, RHU, Electronics for calibration & efficiency studies
HF, Pixel, Calibration, Corrections, Systematics, pre and post LS1
For all BRM/Lumi systems
Italian Restaurant
Il Gattopardo, Trattoria Wildau
Simulation, Medipix, Passives,...
BPTX minutes:
Andrey: Scope Based Algorithms
Talk will be mostly algo sw
BPTX, 175m from IP, connected to scopes, goes to DAQ computer, python scripts, publish to DIP/HTML/ASCII
Two identical scopes, Timing and Bunches, (different orbit sources), SW runs and measures: ΔT, phases, bunch pattern, wrongBucketFlag, pulse integrals, pulse length
DIP goes global and local, ASCII local, HTML access from .cms network
Who uses info? Timing: LHC (cogging), L1 Trigger (bunch pattern, cogging), TTC (phases) Bunching: Nobody cares
Cogging: time difference between B1 and B2, done per BX, σ~10ps, 0.1ns ~ 1.5cm in z
p-Pb cogging: beams are not locked, cogging cannot be calculated with Timing, but can be with Bunches (now someone cares about it?)
Bunch Pattern: abandon BPTX gating signals at L1 and use LHC bunch config instead. BPTX will be relegated to cross-checker, a sad fate indeed.
Monitoring: Tell Trigger Shifter about the html page, it’s nice, maybe make a simplified ‘Shifter Version’ because shifters are simple
Time performance: Timing takes 14 seconds, Bunches takes 35, (atlas takes 3 seconds....). Andrey thinks python is too slow, switch to C/C++ (will take more work)? But who even cares? This isn’t a race! (update: it is almost always a race)
Instabilities: scopes crash, update firmware, jiggle the cable, turn it on and off? Make the code better? cron-job to restart crappy code
What should we do differently? Use Bunches as main scope. Remove fluff/cruft from analysis code, publish minimum info to DIP. Change code language?
Questions: Arkady: firmware? fans busted, overheating? new scope has best firmware!
Andrezj: possible to calculate bunch intensities? yes within 5%, but needs more studies to do better.
Someone: Why did you screw up the code in the first place? Old C++ code was 12 lines and did not respond well to changing starting parameters. Python prevented crawling around on the ground to tweak parameters. But maybe Andrey needs to crawl more?
Anne: Ever use external trigger? yes. Can you make an orbit the external trigger? Can we get around and just use one scope? yes, if you believe phase does not change. but that’s a lot of faith
Vlad: Atlas is not gunna update their BTPX
Me: why dont we just get a better scope with more inputs? it’s super expensive (100k+)
Anne: BPTX Hardware
Hardware has been stable. Scope+software not so much. Caused horrible strife among shifters.
Timing: Keep HW same. Update scope firmware/fans. Move cogging to Bunches. Write down priorities. Include bptx in DQM. We need to debug the code, obviously.
BPTX going forward: PCIe-2ch Acqui card, lots of stats