database update g. pirozzi (università della basilicata and infn – rome i)

Database update

G. Pirozzi(Università della Basilicata

and INFN – Rome I)

G.Pirozzi - Muon meeting Oct 2002 2

Contents

• Database entries• Data size “guesstimate”• Technical solutions• Barcodes


“Simple” Database objects

• S-curve• R-curve• Crosstalk• Noise• WTM• Pitch• Currents

• Uniformity• Planarity• Efficiency• Gas leakage• Any kind of

general info• … many many

more


Composite DB object• Panel (planarity + qual. tests – if any)

– Links to 1 or 2 Gaps, 1 Chamber

• Gap (WTM, Pitch, I,…)– Links to 2 panels, 1 Chamber

• FEE board (R&S-curve, Noise, Crosstalk,single channel info, …)– Links to 1 Chamber

• Chamber (efficiency, plateaux, uniformity, leakage, …)– Links to 5 panels, 4 gaps, n FEE boards


DB requirements• The user MUST have the possibility to access

data at ANY level: – Pierluigi says: “I want to check data from a specific

(well known) chamber, or gap”– Burkhard says: “I want to histogram the WTMs of ALL

the gaps wired with CERN machine”– Bepo says: “For trigger studies I need to get all the

initial efficiency and time resolution data concerning M1 chambers”

– Werner wants to check if they really placed the noisemost FEE boards in the outermost regions

• Data must be stored both in raw and in graphic format


Size guesstimate

• FEE boards– R&S curves: ~1kb data, ~50kb pict– Crosstalk & other: ~1kb data

• Panels (maybe just for samples)– Planarity + quality: ~1kb/100kb

• Gaps– WTM: ~10kb/50kb– Pitch: ~10kb/50kb– Currents + other: 1kb/50kb


Size guesstimate 2• Chamber: all above and also…

– Small “general”: ~1kb data– Plateau: ~100kb/50kb– Uniformity 10Mb/100kb– TDC spectra 10Mb/5Mb

• 1 Chamber ~25Mb/7-10Mb• Although it is always possible to decide to keep

the full data only for some sample chambers, it is reasonable to expect an overall data size of ~50Gb

• Access and data processing time must still be correctly evaluated


Technical solutions

• EDMS provides (nominally) many tools for data storing, definitions of hierarchies and for backtracing the history of the various objects. It uses Oracle servers. It could also be useful to integrate the DB with the CAD drawings

• Custom Oracle-based DBs are also possible (see Atlas LAr)

• CERN Oracle group (IT-DB) offered us full support


A label on each physical object…

LHCb Muon PNPI 07/04

12876….9870


Barcodes

• See Atlas SCT Silicon Detectors• The size of the label depends both

on the “eye-readable” information and on the coded one

• FEE boards impose rather strictly that labels size is of the order of 30x20 mm^2, unless custom solutions are studied (we do NOT like this idea at all)


Code 128

• Advantages:– Alphanumeric code with special

symbols– Self checking– Atlas STC uses the same

• Disadvantages:– Needs overflow side zones


Label size

• L = (5.5D + 11C + 35)X + 2Q– L = minimum label length– D = number of numerical digits– C = number of additional characters– X = with of a single module (1 digit is made of

11 modules … with some constraints)– Q = overflow zone

• The module width (X) can vary from 0.19mm to 0.4mm while the minimum overflows are given by max[2.54mm,10X]


Label size 2• I Imagine, in our case:

• Using “high density” modules (X ~ 0.19mm), we have: L ~ 25 mm

• “Extra” digits may be partly avoidable => leaves the possibility to map also the experiment and the subsystem

CxxyyyyyyC

InitType Serial no.

Check


Conclusions

• The first ideas on how to organize the MuHard DB have been made

• The first contacts with CERN IT-DB have been taken

• Barcode 128 seems a valid solution for labeling detector objects

• The work has started and needs a huge effort. Everyone is invited to give comments, remarks and suggestions

database update g. pirozzi (università della basilicata and infn – rome i)

Documents