8. February 2012 Thomas Bergauer (HEPHY Vienna) SVD Construction Database SVD-PXD meeting.

8. February 2012

Thomas Bergauer (HEPHY Vienna)

SVD Construction Database

SVD-PXD meeting

Sensors and Beam Test

2

SVD Layout

• SVD consists of – ~2000 readout chips– ~200 sensors– ~50 ladders

• We want to – trace all components– Store measurement

results

• Too large to handle with Excel-sheets

• Database proposed to handle this

Thomas Bergauer (HEPHY Vienna)30. Nov 2011

Rect (122.8 x 38.4 mm , 160 / 50 um pitch)2

Rect (122.8 x 57.6 mm , 240 / 75 um pitch)2

W e dge (122.8 x 57 .6-3 8.4 m m , 240 / 75..50 um p itch)2

0

0

10

3

45

6[cm] layers

[cm]

20

-10-20-30 10 20 30 40

6

z APVs

z APVs

z APVs

64

4

4 4

46

6

6

rphi APVs

rphi APVs

rphi APVs

6

64

4

4 4

4

4

46

666 6

6 6 6

6

Layer # Ladder

s

Rect. Sensors[50μm]

Rect. Sensors[75μm]

Wedge Sensor

s

6 17 0 68 17

5 14 0 42 14

4 10 0 20 10

3 8 16 0 0

Sum: 49 16 130 41


3

CMS Tracker Construction Database

Contains:

• Registration: scan barcode and enter

basic sensor information

• Inventory handling: which objects are

where?

• Transfers: shipments from one

institute to another

• Measurement results– Own and vendor measurements

• Good/bad/broken handling

• Assembly: which sensor is on which

module

• Cabling scheme: which module is on

which DAQ channel via which cable


CMS used local Java program interfacing to central Oracle DB

Belle-II: Web interface with mySQL


4

CMS Data Insertion/Extraction

Data insertion:• Measurement results had to be

stored as XML files– Uploaded via BigBrowser (Java

Program)

• Assembly via Java GUI (or similar

XML files)

Data Extraction:• via BigBrowser (limited

functionality)

• User-provided query tools



5

CMS Tracker Scheme

• System tables– object list (object_description)

– History

– Assembly

– Transfer

– Institute list (center_description)

– Problem list (known_problem)

• Action tables (to store measurement

results)– Sensortest (IV, CV, stripscan)

– Mechanical assembly precision

(measured with CMM)

– Bonding (which channels have been

bonded/not bonded)

– ……



6

PROPOSAL FOR BELLE-II



7

Proposal for Belle II

• mySQL Database running at HEPHY• Web-Interface using PHP for most of the db

interaction– Data extraction– Inventory, logistics

• Upload of measurement data directly from measurement software (when available)– LabView Database connectivity tested and working– Root ?



8

Web Interface

• Login: Username/password to identify user (=institute)

• Inventory: shows list of all objects (now only sensors)– Click on sensor shows all information for it (i.e. all

measurements and history)

• Shipments: transfer to inventory of other institute

• Assembly: build modules, ladders, layers (later)



9

OBJECT NUMBERINGAnother topic which goes in parallel to Database



10

Object numbering

• When using a database, each

object needs to have an unique ID

number

• CMS has used barcodes to read

unique ID numbers, called

OBJECT ID

• Barcode can be put onto object

(envelope or box) by vendor or

locally (e.g. Dymo barcode printer)– Very small 2D barcodes have been

used by CMS to remain on modules



11

HPK Sensor Numbering Scheme

• E.g. Sensor 2 02 01 2 0404 52 (12 digits)– Meaning of digits:

• 2…….....Belle-II• 02…..….SVD (01…PXD,…)• 01………Sensor (02…Hybrid,

03…Ladder,…)• 2…….....HPK (1…Micron)• 0404.…..HPK Batch No.• 52………Sensor within batch

– Written without blanks: 202012040438

• Proposed to HPK already (using code-128)Thomas Bergauer (HEPHY Vienna)30. Nov 2011


12

THAT’S IT. ;-)


8. February 2012 Thomas Bergauer (HEPHY Vienna) SVD Construction Database SVD-PXD meeting.

Documents

beam test object numbering

beam test proposal

beam test svd layout

hephy webinterface

beam test web interface

institute assembly

mysql database

object id barcode