G2p AnaInfo
Contents
Additions to the AnaInfo Tables
The AnaInfo tables will be updated with new fields as they are ready. Potential fields are listed below:
- Run Start/Stop times from raw data - Added
- Beam polarization from Moller measurements: Added my Melissa 3/12/13
- Ammonia target material cup number
- Cerenkov and Pre-shower/Shower PID cuts : Added by Melissa 2/15/13
- Scaler normalization analysis
- BCM Charge/Current
- Deadtime : Added 11/26/12 (Not helicity dependent)
- Detector Efficiency : Added 11/26/12
- Sieve Slit Status
- Target Field Strength
- Target Orientation
AnaInfo Tables
Below is a snapshot of the AnaInfo tables on 8/13/12. More fields will be added as time goes on.
mysql> show Tables; +---------------+ | Tables_in_g2p | +---------------+ | AnaInfoL | | AnaInfoR | | RunInfoL | | RunInfoR | | RunInfoT | +---------------+ 5 rows in set (0.00 sec)
mysql> describe AnaInfoL; +---------------+-----------+------+-----+-------------------+-----------------------------+ | Field | Type | Null | Key | Default | Extra | +---------------+-----------+------+-----+-------------------+-----------------------------+ | RunNumber | int(11) | NO | PRI | 0 | | | RunStartTime | datetime | YES | | NULL | | Determined from Raw data files | EntryTime | timestamp | NO | | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP | | ps3 | float | YES | | NULL | | Copied directly from RunInfo | ps4 | float | YES | | NULL | | Copied directly from RunInfo | ps7 | float | YES | | NULL | | Copied directly from RunInfo | ps8 | float | YES | | NULL | | Copied directly from RunInfo | TargetEncoder | float | YES | | NULL | | Avg value from EPICS/raw data | SeptaStatus | int(11) | YES | | NULL | | Expert Determined | RunStatus | int(11) | YES | | NULL | | Expert Determined | RunQuality | int(11) | YES | | NULL | | Expert Determined | Q1p | float | YES | | NULL | | Avg value from EPICS/raw data | Q1pSTD | float | YES | | NULL | | Avg value from EPICS/raw data | Q2p | float | YES | | NULL | | Avg value from EPICS/raw data | Q2pSTD | float | YES | | NULL | | Avg value from EPICS/raw data | D1p | float | YES | | NULL | | Avg value from EPICS/raw data | D1pSTD | float | YES | | NULL | | Avg value from EPICS/raw data | Q3p | float | YES | | NULL | | Avg value from EPICS/raw data | Q3pSTD | float | YES | | NULL | | Avg value from EPICS/raw data | SeptaI | float | YES | | NULL | | Avg value from EPICS/raw data | SeptaSTD | float | YES | | NULL | | Avg value from EPICS/raw data | TargetSTD | float | YES | | NULL | | Avg value from EPICS/raw data | Ihwp | int(11) | YES | | NULL | | Avg value from EPICS/raw data | IhwpSTD | float | YES | | NULL | | Avg value from EPICS/raw data | Energy | float | YES | | NULL | | Avg value from EPICS/raw data (HALLA:p) | EnergySTD | float | YES | | NULL | | Avg value from EPICS/raw data (HALLA:p) | ExpertC | longtext | YES | | NULL | | Expert Determined | RunStopTime | datetime | YES | | NULL | | Determined from Raw data files +---------------+-----------+------+-----+-------------------+-----------------------------+ 27 rows in set (0.00 sec)
mysql> describe AnaInfoR; +---------------+-----------+------+-----+-------------------+-----------------------------+ | Field | Type | Null | Key | Default | Extra | +---------------+-----------+------+-----+-------------------+-----------------------------+ | RunNumber | int(11) | NO | PRI | 0 | | | RunStartTime | datetime | YES | | NULL | | | EntryTime | timestamp | NO | | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP | | ps1 | float | YES | | NULL | | | ps2 | float | YES | | NULL | | | ps7 | float | YES | | NULL | | | ps8 | float | YES | | NULL | | | TargetEncoder | float | YES | | NULL | | | SeptaStatus | int(11) | YES | | NULL | | | RunStatus | int(11) | YES | | NULL | | | RunQuality | int(11) | YES | | NULL | | | Q1p | float | YES | | NULL | | | Q1pSTD | float | YES | | NULL | | | Q2p | float | YES | | NULL | | | Q2pSTD | float | YES | | NULL | | | D1p | float | YES | | NULL | | | D1pSTD | float | YES | | NULL | | | Q3p | float | YES | | NULL | | | Q3pSTD | float | YES | | NULL | | | SeptaI | float | YES | | NULL | | | SeptaSTD | float | YES | | NULL | | | TargetSTD | float | YES | | NULL | | | Ihwp | int(11) | YES | | NULL | | | IhwpSTD | float | YES | | NULL | | | Energy | float | YES | | NULL | | | EnergySTD | float | YES | | NULL | | | ExpertC | longtext | YES | | NULL | | | RunStopTime | datetime | YES | | NULL | | +---------------+-----------+------+-----+-------------------+-----------------------------+ 27 rows in set (0.00 sec)
Organization of AnaInfo
Currently (8/13/12) four fields in the AnaInfo tables are expert determined and by expert determined I mean they do not directly tie back to an EPICS variable. These are, SeptaStatus,RunStatus,RunQuality and ExpertC (or Expert Comment). I will briefly describe the function of each one and how it is determined.
SeptaStatus
During the running of the experiment the RHRS Septa magnet experienced two separate issues which damaged the coil packages. This field exists for both LHRS and RHRS. The SeptaStatus field takes the following values:
- 0 - RHRS septa operating with all coil packages (48-48-16)
- 1 - RHRS septa after 1st issue but before 2nd (40-32-16)
- 2 - RHRS septa after the 2nd problem (40-00-16)
The field values were determined by reading the HALOG to determine when the problems occurred. During transition periods from one status to another it is possible that SeptaStatus value maybe incorrect but this does not affect Production or Optics running, only calibration runs taking with no beam in the Hall.
RunStatus
This is similar to the RunType field in RunInfo except here it is Expert determined instead of Shift Worker controlled. RunStatus takes the following values:
- 1 - g2p Production
- 2 - gep Production
- 3 - Dilution
- 4 - g2p Optics
- 5 - gep Optics
- 6 - Packing Fraction
- 7 - Cosmic
- 8 - BCM Calibration
- 9 - BPM Calibration
- 10 - Pedestal
- 11 - DAQ Test
- 12 - Large Charge Asymmetry
- 13 - Other
These were determined from a combination of the Student Run Sheets, Shift Worker Run Sheets and HALOG.
RunQuality
The RunQuality field distinguishes runs based upon 5 categories. This categories are listed below:
- -1 - Production Run with wrong Septa or Q1
- 0 - Junk/Garbage Run
- 1 - Calibration Run
- 2 - Production/Dilution Run with some minor problems (eg. One BCM not working)
- 3 - Production/Dilution Run with no obvious problems
RunQuality was determined from a combination of Student Run Sheets (SRS), Shift Worker Run Sheets (SWRS) and the HaLog. For the determination of production run quality, it was assumed that any run on the SRS was either a 2 or 3. Runs during a production run period which were not on the SRS were then checked on the SWRS, if they appeared on this list and were flagged as a good run they were a 2 or 3. If a run during a production period was not on either the SRS or SWRS it was considered on a case by case basis.
ExpertC
The ExpertC or Expert Comment field is where the student experts can make comments. These comments serve to explain decisions made in regards to RunQuality and RunStatus made by the student experts. For example, they should give reason for a production run's RunQuality flag if it is something other than 3. The expert comment is also used to provide further information on the RunStatus, such as what kind of optics run or BPM run, for example.
ChangeLog
Listed below are changes made to the database values and the reasoning for this. This is all after the initial population of the DB.
UnStable Septum Field
- 1/30/13 Email from Melissa on 9/11/12:
Hey Ryan, As promised, here is a list of runs that seem to be affected by the "mystery" problem: 22477 - 22480 (2.2 GeV, p0 = 2.228) 22481 - 22487 (2.2 GeV, p0 = 2.228, dilution runs) 22491 - 22501 (2.2 GeV, p0 = 2.072) By run 22502, the problem seems to be gone (at least, I can't see anything suspicious in the vdc wire distribution). I may have add to this list once I actually figure out what was going on. As far as a flag to put on it - since I don't know exactly what the problem was, I don't know what to put. I guess you can just label it "unstable septum field" for now. Let me know if you need anything else - thanks!! Melissa
- Going to change RunQuality to runs in question to a 2, if it wasn't already. And update ExpertComment to reflect this change.
Plots from Runs in Question There should be only 2 peaks, one for e-nitrogen elastic and the other for eP elastic events. This issue happened to the data set when the right septum is under 40-32-16 configuration. Melissa found some strange behavior of the RHRS VDC distributions. There are 4 peaks on NH3 elastic data set.
