Search/Navigation:
Related:
SLAC/EPP/HPS Public
Jefferson Lab/Hall B/HPS Run Wiki
S30XL-LESA/LDMX
...
Java Object Class | Java Collection Class | Default Database Table | Description |
---|---|---|---|
BeamEnergy | BeamEnergyCollection | beam_energies | nominal beam energies |
EcalBadChannel | EcalBadChannelCollection | ecal_bad_channels | ECal bad channel list |
EcalCalibration | EcalCalibrationCollection | ecal_calibrations | per channel ECal pedestals and noise |
EcalChannel | EcalChannelCollection | ecal_channels | ECal channel information including map of DAQ to physical channels |
EcalGain | EcalGainCollection | ecal_gains | per channel ECal gains |
EcalLed | EcalLedCollection | ecal_leds | per crystal LED configuration |
EcalLedCalibration | EcalLedCalibrationCollection | ecal_led_calibrations | per crystal LED calibration information (from calibration run) |
EcalPulseWidth | EcalPulseWidthCollection | ecal_pulse_widths | ECal signal pulse width (currently unused in recon) |
EcalTimeShift | EcalTimeShiftCollection | ecal_time_shifts | ECal signal time shift (currently unused in recon) |
SvtAlignmentConstant | SvtAlignmentConstantCollection | svt_alignment_constants | SVT alignment constants in Millepede format may be disabled using -DdisableSvtAlignmentConstants |
SvtBadChannel | SvtBadChannelCollection | svt_bad_channels | SVT bad channel list |
SvtBiasConstant | SvtBiasConstantCollection | svt_bias_constants | SVT bias setting for a time range |
SvtCalibration | SvtCalibrationCollection | svt_calibrations | per channel SVT noise and pedestal measurements |
SvtChannel | SvtChannelCollection | svt_channels | SVT channel information |
SvtDaqMapping | SvtDaqMappingCollection | svt_daq_map | SVT mapping of DAQ to physical channels |
SvtGain | SvtGainCollection | svt_gains | per channel SVT gains |
SvtMotorPosition | SvtMotorPositionCollection | svt_motor_positions | SVT motor position in mm |
SvtShapeFitParameters | SvtShapeFitParametersCollection | svt_shape_fit_parameters | SVT parameters for the signal fit |
svt_t0_shifts | SVT T0 (first sample) shifts | ||
svt_timing_constants | SVT timing configuration constants including offset and phase | ||
test_run_svt_channels | test run SVT channel information | ||
test_run_svt_daq_map | test run SVT DAQ mapping | ||
test_run_svt_t0_shifts | test run SVT T0 shift |
...
Each type of condition has an associated database table which contains records with conditions information plus a few additional pieces of information.
For instance, this is the table schema for the BeamEnergy condition.
No Format |
---|
mysql> describe beam_energies;
+---------------+---------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+---------------+---------+------+-----+---------+----------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| collection_id | int(11) | NO | | NULL | |
| beam_energy | double | NO | | NULL | |
+---------------+---------+------+-----+---------+----------------+
3 rows in set (0.00 sec) |
The id is the row ID used to uniquely identify the record. The collection_id associates a set of records together into a collection. Every data table has these two fields plus additional columns with the conditions data.
The conditions table associates collections with a run number range.
No Format |
---|
mysql> describe conditions;
+---------------+--------------+------+-----+-------------------+-----------------------------+
| Field | Type | Null | Key | Default | Extra |
+---------------+--------------+------+-----+-------------------+-----------------------------+
| id | int(11) | NO | PRI | NULL | auto_increment |
| run_start | int(11) | NO | | NULL | |
| run_end | int(11) | NO | | NULL | |
| updated | timestamp | NO | | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP |
| created | datetime | NO | | NULL | |
| tag | varchar(256) | YES | | NULL | |
| created_by | varchar(255) | YES | | NULL | |
| notes | longtext | YES | | NULL | |
| name | varchar(40) | NO | | NULL | |
| table_name | varchar(50) | NO | | NULL | |
| collection_id | int(11) | NO | | NULL | |
+---------------+--------------+------+-----+-------------------+-----------------------------+
11 rows in set (0.01 sec) |
The run_start and run_end give a range of run numbers for which the conditions are valid. These can be the same number to specify a single run.
The table_name gives the name of the table containing the conditions data.
The collection_id gives the collection ID to load from the table.
This table is modeled by the ConditionsRecord class which is accessible via the DatabaseConditionsManager.
When multiple collections of the same type are valid for the current run, the most recently added one will be used by default.