sda – shot data analysis

October 2002Jean Slaughter

SDA – Shot Data Analysis

Outline

•Description of SDA

•Examples

•Plans for 2003

SDA is a system for acquiring and analyzing data from stores. It is complementary to specialstudies and the data loggers.

Version 10-15-02-1


Schematic View of SDA

InstrumentsOther Devices

System of DA engines

Database

FilesEXCEL,

etc.Scalar, Plot

Viewers

User Programs(Java classes)

Servlets

Standard Plots, Tables,Store Checker

SDAEdit


Inputs to SDA• Longitudinal, transverse emittances• Intensities, DC and bunched• Beam positions • Settings

– Magnets, collimators, etc.– Tunes, chromaticities

• Computed devices• Data from CDF, D0

– Luminosity– Losses– Beam position, size


Tevatron HEP Collider State Diagram

Proton Inject’nporch

Proton Injectiontune up

Inject Protons

Eject Protons

Inject Pbars

PbarInjection

porch

BeforeRamp

Flattop

Acceleration

Squeeze InitiateCollisions

Remove Halo

HEP

Pause HEP

ProtonRemoval

Unsqueeze

Deceleration

Extractionporch

Extract Pbars

Cogging

Recovery

Ramping

Flattop2

Reset

Cases and Sets

36 sets p injection9 sets for pbar injectionset every 10 min - HEP

Not shown are MI, Pbar Source, Recycler States


SDA Viewer WindowCase Unstack Pbars- Store 1843


Pbar Bunch Intensities in MI before Transfer Case Inject Pbars - Store 1787

set number (transfer)

bunch intensity - 109


MI Bunch Intensities After RF Compensation - Store 1836

Intensity 109

store:set (transfer)


Snapshots and Fast Time Plots Capture High Frequency Data- (PlotViewer)

RF cavity phase, RF4 Cavity Volts

RF4 MI phase error, 53 MHZ

246 12 180 seconds

Accumulator RF During Unstacking


Standard Plot for Pbar Intensities


Store Checker• Purpose

– Monitor instrumentation and DAQ

– Monitor accelerator performance

• Checks SDA data for specified cases/sets

– Min < device value < max

– Min < ( difference in time of 2 devices ) < max

– Min < ( difference in value of 2 devices) < max

• Jobs run automatically every store

• “Standard” and “private” lists

• Results on WWW for “standard” list

• Lists on WWW


Store Checker Results

When MiniBoone started running, errors were detected. B:CHGB had to be sampled and held at aa different time.


Examples of User Analyses

• Emittances for stores 1300-1700• Calculated versus measured luminosity at CDF• Measured HEP pbar lifetime compared to lifetime

expected from interactions


User Analysis Combining Many Stores

P. Derwent


Measured Versus Computed Luminosity

P. Lebrun


Measured Pbar Lifetime Versus Lifetime Due to Collisions - March

-5 0 5 10 15 20 25 30 35 40

20

30

40

50

60

70

80

90

100

110

120

130

140

150

160

assuming 70 mb X-section

Old Stores (Febr. , March 02)

Comparison between Measured Pbar lifetime and "burn rate" due to collision

Pb

ar

Lie

time

, HE

P (

ho

urs

)

Bunch Number

Life-1036 BurnRate-1036 Life-1043 BurnRate-1043

P. Lebrun


-5 0 5 10 15 20 25 30 35 400

20

40

60

80

100

120

140

160

Pb

ar

Lie

time

, HE

P (

ho

urs

)

assuming 70 mb X-section

Recent Stores (Oct 02)

Comparison between Measured Pbar lifetime and "burn rate" due to collision

Bunch Number

Life-1832 BurnRate-1832 Life-1836 BurnRate-1836

Measured Pbar Lifetime Versus Lifetime Due to Collisions - October

P. Lebrun


Jobs for 2003• Finish and then maintain SDA infrastructure

– Still some DAQ errors – More flexible user access to data– Physics classes in Java tool kit

• Finish reviewing inputs • Study instrumentation• Standard plots and tables

• Emittances• Automated shots log• Automated summary spreadsheets

• User requests and education• Long term archiving of (non-SDA) data logger data


Ongoing Operations in 2003

• Dedicated analyses• Monitoring of SDA inputs

– Instrumentation problems– DAQ problems

• Monitoring of stores– Assimilating all the information– Group of physicists to review data and

follow up on what’s found


SDA Team

• Controls Department– K. Cahill, B. Hendricks, M. McCusker, T.

Bolshakov• Computing Division

– P. Lebrun, S. Panacek, A. Kulyavtsev, N. Kouropatkine, R. Rechenmacher

• Systems Departments– E. Harms, J. Annala, D. Capista

• Headquarters– M. Church, J. Slaughter


Summary

• SDA infrastructure should be complete in 6 months

• Shot analysis is a continuing part of operations


Two Types of Data

• Lumberjack data– Fixed frequencies,

i.e. non-triggered– Used for studies– Circular buffers –

data is overwritten after 1-30 days

– Any user can modify any archive configuration

• SDA data– Triggered at

specific events– Only during stores– Permanent archive– Standard content

Backup Slide

sda – shot data analysis

Documents