Difference between revisions of "Compton Database Scheme"
From PolWiki
Jump to navigationJump to searchLine 18: | Line 18: | ||
*end_time: DATETIME | *end_time: DATETIME | ||
*comment: TEXT | *comment: TEXT | ||
+ | |||
+ | === measurement_type === | ||
+ | *measurement_type_id: INT UNSIGNED AUTO_INCREMENT | ||
+ | *units: TEXT | ||
+ | *title: TEXT | ||
+ | |||
+ | === beam === | ||
+ | *beam_id: INT UNSIGNED AUTO_INCREMENT | ||
+ | *analysis_id: INT UNSIGEND | ||
+ | *monitor_id: INT UNSIGNED | ||
+ | *measurement_type_id: CHAR(4) | ||
+ | *subblock: TINYINT UNSIGNED | ||
+ | *n: INT UNSIGNED | ||
+ | *value: FLOAT | ||
+ | *error:FLOAT | ||
+ | |||
+ | === monitor === | ||
+ | *monitor_id: INT UNSIGNED AUTO_INCREMENT | ||
+ | *quantity: TEXT | ||
+ | *title: TEXT | ||
== Unorganized list of values we want to record == | == Unorganized list of values we want to record == |
Revision as of 14:27, 26 June 2012
This page contains the proposed database scheme to store laser cycle analysis information per run. This scheme is modeled in part with the QWeak database scheme presented in Damon Spayde's collaboration talk slide 6.
good_for
- good_for_id: INT UNSIGNED AUTO_INCREMENT
- type: TEXT
run_quality
- run_quality_id: INT UNSIGNED AUTO_INCREMENT
- type: TEXT
run
- run_id: INT_UNSIGNED AUTO_INCREMENT
- run_number: INT UNSIGNED
- run_type: TEXT
- good_for_id: SET(1-40)
- run_quality_id: SET(1-40)
- start_time: DATETIME
- end_time: DATETIME
- comment: TEXT
measurement_type
- measurement_type_id: INT UNSIGNED AUTO_INCREMENT
- units: TEXT
- title: TEXT
beam
- beam_id: INT UNSIGNED AUTO_INCREMENT
- analysis_id: INT UNSIGEND
- monitor_id: INT UNSIGNED
- measurement_type_id: CHAR(4)
- subblock: TINYINT UNSIGNED
- n: INT UNSIGNED
- value: FLOAT
- error:FLOAT
monitor
- monitor_id: INT UNSIGNED AUTO_INCREMENT
- quantity: TEXT
- title: TEXT
Unorganized list of values we want to record
- IHWP #1 and #2
- Beam energy
- Beam Position
- Beam Slope
- Laser power
- Charge
- Beamline asymmetries