Top Banner
3

Checkout with pulser runs · Checkout with pulser runs: So far just scanned events 'manually'; only few chan. checked Bunch # seems always OK Rotation # sometimes 'skips'; counter

Jul 24, 2020

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Checkout with pulser runs · Checkout with pulser runs: So far just scanned events 'manually'; only few chan. checked Bunch # seems always OK Rotation # sometimes 'skips'; counter
Page 2: Checkout with pulser runs · Checkout with pulser runs: So far just scanned events 'manually'; only few chan. checked Bunch # seems always OK Rotation # sometimes 'skips'; counter
Page 3: Checkout with pulser runs · Checkout with pulser runs: So far just scanned events 'manually'; only few chan. checked Bunch # seems always OK Rotation # sometimes 'skips'; counter

3

Checkout with pulser runs: So far just scanned events 'manually'; only few chan. checked Bunch # seems always OK Rotation # sometimes 'skips'; counter in WFD? Problem so far seems only rotation # for 'primary pulse' chan.; 2ndary pulse, few Si chan. checked all agree (rotation #, bunch #) Maybe change WFD module w/ suspect rotation #?

But also: Need systematic way to verify (rotation #, bunch #) correct all chan. Only if all ~OK can use to separate pulser/physics events Also need (rotation #, bunch #) for coincidences in t

0 scint.

If (rotation #, bunch #) cannot be verified to ~work: Proposal: turn off pulser for sweep measurements? (easy in config. file)

Pulser event identificationPulser event identificationPulser event identificationPulser event identification