Project

General

Profile

Feature #994

detector cabling

Added by Wilson, Antony almost 11 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Martyniak, Janusz
Category:
Python API
Start date:
23 May 2012
Due date:
% Done:

100%

Estimated time:

Description

please provide the meta data you want to be associated with cabling data

Files

cabling_detector.py (957 Bytes) cabling_detector.py Wilson, Antony, 17 July 2012 09:41
cabling_detector_from_file.py (481 Bytes) cabling_detector_from_file.py Wilson, Antony, 17 July 2012 09:41
#1

Updated by Karadzhov, Yordan almost 11 years ago

I suggest to use for cabling almost the the same scheme as for the calibration.
The only difference is that we do not need "cabling type"

Metadata when storing a cabling:

device name
valid from date

retrieval of a cabling to be via one of these methods:

get_cabling_for_run(device_name, run_number)
get_cabling_for_date(device_name, date_number)
get_current_cabling(device_name)
get_cabling_for_id(id)
get_ids(start_time, stop_time)

#2

Updated by Wilson, Antony almost 11 years ago

  • Assignee changed from Karadzhov, Yordan to Rajaram, Durga

Hi Durga
Please can you confirm that this will meet your requirements

#3

Updated by Rajaram, Durga almost 11 years ago

This sounds fine.

#4

Updated by Wilson, Antony over 10 years ago

My test CDB server has been updated and a new Python API is available at
http://bazaar.launchpad.net/~antony-wilson/mcdb/mice.cdb.client.api-python/download/head:/cdb0.0.3.2.tar.gz-20120717083724-92kawpbx85vmojyx-1/cdb-0.0.3.2.tar.gz

Documentation can be found at
http://rgma19.pp.rl.ac.uk:8080/cdb/doc/python/classcdb_1_1__cabling_1_1Cabling.html
and
http://rgma19.pp.rl.ac.uk:8080/cdb/doc/python/classcdb_1_1__cabling__supermouse_1_1CablingSuperMouse.html

The attached examples show how to add data and retrieve data to my test server. You should be able to use my test server for limited testing.

Regards
Antony

#5

Updated by Rajaram, Durga over 10 years ago

  • TOF cabling now in the production DB
  • Code to access cabling added, modified, merged
  • ConfigurationDefaults has new parameter to specifiy cabling date (default = "current")
  • TOF_cabling_date_from
  • Note: the schema has devices TOF0,TOF1,TOF2 -- the cabling data however is common to all tof stations.
    Since there is no generic "TOF" device, I have triplicated the same data under the 3 devices. The code by default looks in the device specified by "TOF_trigger_station" in ConfigurationDefaults
#6

Updated by Rajaram, Durga almost 9 years ago

  • Assignee changed from Rajaram, Durga to Martyniak, Janusz

Looks like the DAQ was not added as a detector/device in the cabling table.
Can we please add it?

MICE Production Server - Public read only interface
API Version: 1.0.0.0
Server name: MICE Production Server - Public read only interface
Cabling
    set_url(string url)
    get_name()
    get_server_host_name()
    get_status()
    get_version()
    get_cabling_for_date(string device, datetime timestamp)
    get_cabling_for_id(int id)
    get_cabling_for_run(string device, int run_number)
    get_current_cabling(string device)
    get_ids(datetime start_time, datetime stop_time)
    list_devices()
Devices:['CONTROL', 'CKOV A', 'CKOV B', 'EMR', 'KL', 'SCALERS', 'TOF0', 'TOF1', 'TOF2', 'TRIGGER', 'TRIGGER REQUEST', 'TRACKER 1', 'TRACKER 2']

#7

Updated by Rogers, Chris almost 9 years ago

I did a little digging - it looks like the Devices list is implemented on the client side in _cabling.py line 47

self._detectors = ["Ckov A", "Ckov B", "EMR", "KL", "Scalers", "TOF0", "TOF1", "TOF2", "Trigger", "Trigger request"]

and on the server side in ServerConstants.java line 58
    /** Names of detector devices **/
    public static final String[] DETECTORS = { "Ckov A", "Ckov B", "EMR", "KL", "Scalers", "TOF0", "TOF1", "TOF2",
            "Trigger", "Trigger request" };

On the server side the same list is used for Calibration and for Cabling. The quickest way would be to add DAQ to these two lists, though strictly speaking DAQ should not (I believe) have a calibration. It is probably okay...

#8

Updated by Martyniak, Janusz almost 8 years ago

Implemented and deployed on the preprod DB. Open for testing. Please note that you need to update your client API as well to be able to benefit for the change.

Thanks, JM

#9

Updated by Martyniak, Janusz almost 8 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Successfully tested on the preprod DB.

Also available in: Atom PDF