Project

General

Profile

Feature #993

detector calibration

Added by Wilson, Antony about 12 years ago. Updated over 11 years ago.

Status:
Open
Priority:
Normal
Assignee:
Wilson, Antony
Category:
Python API
Start date:
23 May 2012
Due date:
% Done:

0%

Estimated time:

Description

the detectors wish to store their calibration data as flat files

it is proposed that they provide the following metadata when storing a calibration:
device name
calibration type
valid from date

retrieval of a calibration will be via one of these methods
get_calibration _for _run(device_name, calibration_type, run_number)
get_calibration _for _date(device_name, calibration_type, date_number)
get_current_calibration(device_name, calibration_type)
get_calibration _for _id(id)

get_ids(start_time, stop_time)
Return a list of ids of the calibration data sets that were valid during the given time period.
N.B. if the stop_time is None then only the ids that were valid at the start_time will be returned.
Returns:
a dictionary containing the calibration ids data set:
key - id
value - dictionary with id specific data
id specific data dictionary:
key - validFrom
a datetime from when the id was valid
key - created
a datetime of when the id was created

Please can Yordan and Durga confirm that this will meet their requirements


Files

calibration.py (972 Bytes) calibration.py Wilson, Antony, 12 July 2012 13:50
calibration_detector_from_file.py (500 Bytes) calibration_detector_from_file.py Wilson, Antony, 12 July 2012 13:50

Related issues

Related to Configuration Database - Bug #1519: Method to get calibrations by run is brokenClosedMartyniak, Janusz11 July 2014

Actions

Also available in: Atom PDF