PXL detector geometry correction DB

1. different layers of translation + rotation

These translation + rotation tables are similar to the ones for SSD and so on. They can be either ideal geometry or including corrections. They are to be stored in geometry db domain. We don’t know how frequent will they need to be changed yet, maybe on 100 days level. The table type will be

$STAR/StDb/idl/Survey.idl    size: 184

“Id” is always the index, and always starts from 1. 

We need several layers of tables for PXL detector with different names:

idsOnTpc, 1 row;
pstOnIds, 1 row;
pxlOnPst, 1 row;
pxlHalfOnPxl, 2 row;
pxlSectorOnHalf, 10 row;
pxlLadderOnSector, 40 row;
pxlSensorOnLadder, 400 row;

2. sensor TPS correction parameters

These tables are to be stored in geometry db domain, expected to change per year. Id is index. The array length of X, Y, W should be nMeasurements, right now it is 121.  I don’t see a need to change this 121 right now but can’t tell whether it will need to be changed in the future. I don’t know whether there is a better way to deal with this kind of situation.  Size: 1472, total size for 400 entries is 588.8 k.

/* pxlSensorTps.idl

 *

 * Table: pxlSensorTps

 *

 * description: // pxl sensor correction by Thin Plate Spline

 *

 */

struct pxlSensorTps {

  long Id; /* 1-400 */

  unsigned short nMeasurements; /* n measurements for TPS fit */

  float A[3]; /* */

  float X[121]; /* */

  float Y[121]; /* */

  float W[121]; /* */

};

The idl files can be found at RCF

/star/u/qiuh/hft/offlineChain/DB/StDb/idl

Currently I will be the person who need to insert the data, login: qiuh