Difference between revisions of "CCDB Example Session"

Revision as of 11:34, 8 January 2014

Date: Sat, 07 Dec 2013 21:11:49 -0500
From: Mark Ito <marki@jlab.org>
To: Sean Dobbs <s-dobbs@northwestern.edu>
CC: Dmitry Romanov <romanovda@gmail.com>
Subject: Re: CCDB tables

Sean,

Dmitry and I added two of the tables you sent me. Here are some of the 
commands that we used, with some comments:

# work on the timing offsets table
# first get documentation on the "mktbl" command

ccdb help mktbl

# next add the table, as per specs

ccdb mktbl CDC/timing_offsets -r 3522 t0 #timing offset, t0 \(ns\)

# now add some actual constants
# first look at the documentation for "add"

ccdb help add

# add the data taking the defaults: default variation and run range
# from 0 to infinity find data.txt as an attachment to this message

ccdb add CDC/timing_offsets data.txt

# dump the results of the add, use specific identifier returned from the
# addition, format is suitable for a hand editing and re-adding

ccdb dump /CDC/timing_offsets:0:default:2013-12-06_16-37-29

# another look at the constants added

ccdb cat /CDC/timing_offsets

# take a peek at all of the constants for this type

ccdb vers /CDC/timing_offsets

# go on the the wire alignment table
# this one has multiple columns

ccdb mktbl CDC/wire_alignment -r 3522 \
   dxu dyu dxd dyd #upstream and downstream wire end displacement

# add try to add constants for wire alignment, but make a mistake
# (d2.txt attached), command was rejected with an error message, no
# action was taken

ccdb add CDC/wire_alignment_offsets d2.txt

# try again, this time with success

ccdb add CDC/wire_alignment d2.txt

# look at the version

ccdb vers /CDC/wire_alignment

# look at the added constants

ccdb cat /CDC/wire_alignment

# end of session

In addition, note that you can browse the contents of the database at 
https://halldweb1.jlab.org/ccdb . The constants described above will be 
there, of course.

This is all done in the spirit of trying things out. All can be reversed 
if necessary. Feel free to fool around yourself. One important caveat: 
the read actions will succeed from anywhere, internet-wise. The write 
actions must be completed while logged into the JLab CUE. This is our 
current access control protocol.

I'm sure that this will generate questions, so please ask away. Note 
that Dmitry is the true expert in all matters CCDB.

   -- Mark