Project

General

Profile

Bug #1817

Alignment corrections in CDB

Added by Rajaram, Durga almost 6 years ago. Updated over 5 years ago.

Status:
Open
Priority:
Normal
Category:
Database
Start date:
01 February 2016
Due date:
% Done:

0%

Estimated time:

Description

We want to store in a CDB table, alignment and analysis-based corrections to the surveyed geometry.

This makes it easier to keep track of the alignment stuff and allows one to, if needed, apply the corrections for chosen run ranges without having to release a new geometry when the alignment gets updated.

But this would mean that the geometry_download script will have to
  • pull down the corrections from the CDB (if corrections exist for a run)
  • update the positions/rotations in the GDML and ParentGeometry.dat files

As far as the end-user goes, there should be no difference in how the geometry is used.

Propose the following schema:


ID (int)
Module_Name (string)
dx(float)
dx_err (float)
dy (float)
dy_err (float)
dz (float)
dz_err (float)
dx_rot (float)
dx_rot_err (float)
dy_rot (float)
dy_rot_err (float)
dz_rot (float)
dz_rot_err (float)
valid_from (timestamp)//

I am imagining the Module_Name would be e.g. TOF1/Tracker0/Tracker1/EMR/ etc

For the API,

get_corrections_for_run(run, module_name) 
get_corrections_for_date(date, module_name)

set_corrections(module, list_of_corrections)

Also available in: Atom PDF