A Diagnostic Tool for the ZEUS Microvertex Detector Hardware

byAndreas Jantsch

TU Dresden

06/09/2004 Summer Student Session 2004 2

Contents

1. The ZEUS Microvertex Detector2. The ZEUS MVD Hardware3. The Diagnostic Tool

06/09/2004 Summer Student Session 2004 3

1. The ZEUS Microvertex Detector

06/09/2004 Summer Student Session 2004 4

The Microvertex Detector

• installed during the shutdown periode 2000/01• high precision track measurements of

electron – proton interactions• track resolution of ~10µm

06/09/2004 Summer Student Session 2004 5

Modules

• silicon strip sensors• surface: 36cm²

thickness: 300µm• 512 strips / halfmodule• 2 halfmodules / module• 8 analog readout chips

(Helix 3) / module

06/09/2004 Summer Student Session 2004 6

2. The MVD hardware

06/09/2004 Summer Student Session 2004 7

The Patchoxes

06/09/2004 Summer Student Session 2004 8

The MVD hardware

06/09/2004 Summer Student Session 2004 9

The MVD Platform

06/09/2004 Summer Student Session 2004 10

MVD Platform Boards

06/09/2004 Summer Student Session 2004 11

Why do we need a diagnostic tool?

06/09/2004 Summer Student Session 2004 12

3. The Diagnostic Tool

DATABASE:• contains boards, cards, cable labels, …

and relations betweenQUERY SCRIPT:• information from database

06/09/2004 Summer Student Session 2004 13

My Steps

• understand the detector• understand the MVD hardware• learn MySQL and PERL• create the database using an SQL script• write a PERL script to query the database• type in the data from paper documentation

by hand

06/09/2004 Summer Student Session 2004 14

The Database

• create database usingan SQL script

• create all tables• load data into tables

using ascii text files• 1 table / board type• 17 tables

HV_PATCHBOX CARD

D-2-82D411

D-2-72D410

D-2-62D409

::::

A-8-28A1

A-8-18A0

cableslotcrateid

06/09/2004 Summer Student Session 2004 15

The Query Script

• PERL / DBI• 3 options:1. all boards connected to one halfmodule2. all halfmodules connected to a specific

board3. all halfmodules connected to a helix

driver cable

06/09/2004 Summer Student Session 2004 16

ExampleWhich halfmodules are affected,

if you exchange one helix driver board?

• input: name: helix_drivercrate: R-2-1-4slot: 11

• output: ids: 80…89, 200…219

06/09/2004 Summer Student Session 2004 17

Results

• solve hardware problems more quickly• all information in one database for the first

time• easy to enlarge database and query script

(e.g. spares, fanouts, …)

06/09/2004 Summer Student Session 2004 18

Future Prospects

• link to MVDDAQ homepage by Alessandro Polini

06/09/2004 Summer Student Session 2004 19

Thanks!

• Tobias Haas• Chris Youngman• Alessandro Polini• Krzysztof Wrona• Radek Kaczorowski• Ingo Martens