# Presentation: 898464

## 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 special
- studies and the data loggers.

- Version 10-15-02-1

**Notes:**
 Here is an outline of what I will be covering in this talk.
First I want to put SDA in context as one of several tools for understanding the accelerator complex performance.  Then I will describe SDA, give some examples, and conclude with our plans for next year.

## Schematic View of SDA

- Instruments
- Other Devices

- System of
- DA engines

- Database

- Files

- EXCEL,
- etc.

- Scalar, Plot
- Viewers

- User Programs
- (Java classes)

- Servlets

- Standard
- Plots, Tables,
- Store Checker

- SDAEdit

**Notes:**
Here is a box diagram of the SDA system
Here on the top left, we have the devices whose data we want to record.
SDAEdit, the blue box in the top right, is a GUI for entering into the database, a list of devices and the times at which to acquire the information.  When a store begins, as controlled by the sequencer, the System of DA engines makes the appropriate requests to the front-ends that control the devices.  At the appropriate time, the front ends read the data and send it back to the DAQ which then stores the information in the database. 
    Accessing the data is shown on the lower part of the diagram.  The servlet infrastructure acts as the interface to the database.  There are a number of standard plots, tables and the store checker which are built or run automatically each store as shown in the light blue box.  The pink boxes show the  viewers for browsing the data and extracting it to files for analysis in other familiar tools like EXCEL,  MathLab.  Next, as indicated in the yellow box, there is a suite of Java classes for special purpose user written programs for more complicated analyses. Finally, for completeness,  I show the tradition data loggers which acquire data based at fixed frequencies, independent of stores.

## 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

**Notes:**
This next slide lists the types of data saved in SDA.  There are the 
 emittance devices, such a flying wires, sync light and bunch length.  Then there are the intensity measuring devices, like the torioids and fast bunch integrators.
There are a variety of beam position devices.  A number of settings are recorded, plus computed devices which are combined of other devices.  Finally, information comes from the experiments, the bottom line, luminosity, plus losses and information on the beam position at size at the interaction points.

## Cases and Sets

- Proton Inject’n
- porch

- Proton Injection
- tune up

- Inject
-  Protons

- Eject
-  Protons

- Inject Pbars

- Pbar
- Injection
-  porch

- Before
- Ramp

- Flattop

- Acceleration

- Squeeze

- Initiate
- Collisions

- Remove
- Halo

- HEP

- Pause HEP

- Proton
- Removal

- Unsqueeze

- Deceleration

- Extraction
- porch

- Extract Pbars

- Cogging

- Recovery

- Ramping

- Flattop2

- Reset

- 36 sets p injection
- 9 sets for pbar injection
- set every 10 min - HEP

- Not shown are MI, Pbar Source, Recycler States

**Notes:**
I said earlier that the SDA data acquisition is triggered relative to specific events in the  Here is a state diagram of the Tevatron during a store. If we ignore  proton injection tune up,  box which is inject protons, the process starts with proton injection porch, the heavy black box.  There are then 36 proton injections, the blue box.  Next there are 9 Pbar injections of 4 bunches each( green box).  Then follow the line of pink boxes – before ramp, accelerate, flattop squeeze, initiate collisions, remove halo, to HEP, the red box.  Each of these boxes, including the ones, I didn’t mention, corresponds to a case, cases can have repeated data  collections, called sets – as indicated in the box on the right:
36 in proton injection, 8 for pbar injection and a set every 10 minutes for HEP
I won’t show them, but they are in your copy of the transparencies, but there are more cases covering, for example, protons into the MI, with 36 sets,  and  cases for recycler operation. 

## SDA Viewer WindowCase Unstack Pbars- Store 1843

**Notes:**
The simplest way to get the data is to use the browser.  Here is an example of a browser window – I don’t expect you to read this.  It shows the case unstack Pbars in the accumulator. You see the list of devices on the left, a shot description and then t7 of the 9 sets – there is a set for each of the 9 pbar transfers.

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

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

- set number (transfer)

- bunch intensity - 109

**Notes:**
You can plot the rows, Here for example we have for the case inject Pbars, the 

## 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 **

- 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 

- Store Checker
- Results

- When MiniBoone started running,
- errors were detected. B:CHGB
- had to be sampled and held at a
- a 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

**Notes:**
Prior to recalibration of pbar fbi
. Color is pbar bunch intensity 

## Measured Pbar Lifetime Versus Lifetime Due to Collisions - March

- P.  Lebrun

- _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

**Notes:**
On the previous slide, you saw that there are two archiving systems.  Lumberjack and SDA.   They are compared here. The lumberjack data logger is always running and is distributed among many different loggers..  Data is acquired according to a designated frequency,  independent of accelerator states.  It’s the only archiver active during study time.  It has a major deficiency that most of the data o the data disappears after 1-30 days depending on the  logger.  

    In contrast, SDA is completely store based and data acquisition is triggered on specific events, such as inject protons.  It is a permanent archive and the content is controlled, while the lumberjack configurations can and are modified at will.