# Presentation: 210375

## Mapping for Silicon Run IIb

- L. Bagby, A. Nomerotski, _E. von Toerne_
- December 2002
- _[http://d0server1.fnal.gov/projects/run2b/Silicon/www/smt2b/readout/mapping.htm](http://d0server1.fnal.gov/projects/run2b/Silicon/www/smt2b/readout/mapping.htm)_

## Mapping/Cabling Requirements

- Do not move the 80 conductor cables
- Do not move the 50 conductor cables
- Avoid cable knots
- Each HV channel has channel from only one VRB
- Each stave goes into one VRB (soft constr.)
- 80-cond. cable requirements (from STT / see B.Reay’s note)
- Do not combine different stave types I,II,III,IV
- Do not combine hybrids from different 30deg. sectors
- Do not combine L0 with other layers
- Do not combine L4 with other layers
- Do not combine a layer with any other layer (soft constr.)

## Cathedral

**~19’-30’ High **
**Mass Cable     **
**(3M/80 conductor)**

**Serial Command Link**

**Cathedral**

**Interface**
** ****Board**
**Crates**
**(8x18)**

**8’ Low Mass Cables**

**3/6/8/9 Chip HDI**

**Sensor**

**CLKs**

**Horse Shoe**

**3/6/8/9 Chip HDI**

**Sensor**

**Adaptor **
**card**

**25’ High Mass Cable (3M/50 conductor)**

**CLKs**

- I
- B

**MCH2**

**V****R****B****C**

**S**
**B**
**C**

**V****R****B**

**Monitoring**
**SDAQ**

**PDAQ  (L3)**

**VRB**
**Crates**
**(12x10)**

**Platform**

**SEQ**

**SEQ**
**Controller**

**Optical Link**
**1Gb/s **

**Sequencer **
**Crates**
** ****(6x20)**

**VTM**

**Around Iteraction Region**

**CLKs**

**MCH3**

**PowerPCs and Single Board Computers are accessed thru Ethernet**

**MCH2**

**HV **
**Crates**
** ****(8x6+2x4)**

**Cathedral**

**Fuse**
**Panel**

**Bulk LV**
**Power Supplies**

**HV**
**fanout**
**1=>4**

**HV**
**breakout**
**box**

**VME**
**Crates**
**(4x3)**

**25 twisted **
**pair cables**

**17 twisted **
**pair cables**

**HV**

**LV**

**I,V,T Monitoring**

## How many hybrids does it take to ...

## Lyn’s Mapping Suggestion

## Readout Electronics

- Interface Boards
- 8 crates (144 boards) located inside the detector volume
- Regenerates signals
- SVX monitoring and power management
- Bias voltage distribution

**SEQuencers**
**6 crates (120 boards) located on the detector platform**
**Use SVX control lines to actuate acquisition, digitization and readout**
**Convert SVX data to optical signals**

**VRBs (Readout Buffers)**
**12 crates (120 boards) located in counting house**
**Data buffer pending L2 trigger decision**
**Input @ 5-10 kHz L1 accept rate ~ ****50 Mb/s/channel**
**Output @ 1 kHz L2 accept rate ~ ****50 Mb/s**

## Installation

- Interface Boards

## HV distribution

- HV Modules
- (MCH2)

- Fanout Boxes
- (MCH2)

- Breakout Boxes
- (Platform)

## Naming of Installed Parts

- A few technical terms
- Module: 	A sensor/hybrid combo in Layers L2-5 		Types: 10/10A  20/20A  10/10S  20/20S
- Stave:	10/10A+20/20A+10/10S+20/20S+support
- Ladder:	Sensors ganged together in readout
- 		(1 Module = 2 Ladders)

## General Remarks

- Labeling of production parts and installed parts differs
**Worst case naming scenario:** Each subgroup uses different  names for the same installed object: HV naming different from DAQ naming different from reconstruction different from MC simulation ...
- It might be convenient to have a scheme similar to RunIIa
- Because it is convenient not to have to learn new names
- It might be better **NOT** to have a scheme similar to RunIIa
- Because the detector geometry is very different and the naming should reflect the geometry.
- The proposed scheme is a good compromise of these two principles

## Module Position on Stave

**20/20**

- South End

- North End

**10/10**

- Naming of ladders:
- Lisa will use “barrel” label

## Stave Location in R-phi

- No inner/outer radius
- stave structure

- Uli Heintz’s STT labeling
- (from Bill Reay’s mapping note)

## Stave Location in R-phi

**508**

**408**

**306**

**204**

**509**

**409**

**307**

**205**

**510**

**511**

**410**

**411**

**308**

**512**

**513**

**412**

**309**

**206**

**413**

**310**

**514**

**515**

**207**

**311**

**414**

**516**

**415**

**517**

**208**

**312**

**416**

**518**

**519**

**417**

**313**

**209**

**314**

**419**

**418**

**521**

**520**

**210**

**523**

**315**

**420**

**522**

**211**

**316**

**421**

**524**

**317**

**422**

**525**

**423**

**526**

**527**

**212**

**L2-01**

**L3-01**

**318**

**424**

**528**

**529**

**L4-01**

**530**

**402**

**302**

**L5-01**

**403**

**502**

**503**

**404**

**303**

**202**

**504**

**505**

**405**

**304**

**203**

**305**

**406**

**506**

**407**

**507**

-  Compromise between STT note and reconstruction needs
- Label with 3 digits
-  highest significant digit indicates layer
-  Start at x-axis, similar to U.Heinz’s STT note)
-  Go counterclockwise
-  Odd numbers have always smaller radius than even numbers in the same layer, consis-tent with Table 9, TDR

**End-on view**

- North/South,Axial/Stereo    labels: **AN, AS, SS, SN**

**Seen from **
**South(?)**

## Naming of Layer 0 and 1

**End-on view**

**3**

**4**

**2**

**1**

**12**

**11**

**10**

**9**

**8**

**7**

**6**

**5**

## Naming of Layer 0 and 1 Sensors

- North End

- South End

**6**

**5**

**4**

**3**

**2**

**1**

**2**

**3**

**4**

**5**

**6**

**1**

## Naming of Module/Staves – Part2

- How to address a sensor located inside the run IIb detector?
- Use stave number and local sensor number
- It is in layer **3**, **N**orth side, **A**xial alignment
- in an outer radius stave (because of even stave number)
- the **6****th** sensor from the middle of the detector => outermost sensor on the north side
- Advantage: Everybody is able to find it using the map
- Hybrid locations are labeled by module

**L3-08NA****-6**

## Naming of Production Parts

## Naming of Production Parts, Hybrids

- Name of Production parts conveys part properties.
- Hybrid properties to appear in naming:
- Layer 0 / L1 / L2-5 Axial / L2-5 Stereo
- I suggest to label production hybrids with a 4-digit number, following a suggestion by Jim Fast
- Highest significant number could indicate the hybrid type

- Example:	Hybrid-0001 Layer0
-  		Hybrid-1001 Layer1
- 		Hybrid-2001A Layer2-5 Axial
- 		Hybrid-3001S Layer2-5 Stereo

**How does the database handle preceding 0’s ?**
**Does the database accept hyphens?**
**How do we handle pre-production parts?**

- Highest Significant Digit

## Naming of Production Parts, Sensors

- Layer 0 / L1 / L2-5
- production sensors with a 4-digit number
- The highest significant number indicates the sensor type

- Highest Significant Digit

## Naming of Production Parts, Modules

- Naming of junction cards/adapter cards

- No differentiation by layer
- Assign consecutive production numbers

- L2-5 Modules named after hybrid they contain
- + appendix to indicate 10/10 and 20/20 Modules
- Hyb-2001A (L2-5, axial hybrid) becomes either
- M-2001-10/10A or
- M-2001-20/20A

## Naming of jumper cables

- Differentiation by length

-  Naming of L0 flex cables

- Assign production numbers based on          layer and length -> will talk to Noel

- Naming of twisted pair cables

- Consecutive production numbers

## Naming of Production Parts, Staves

- Are all staves alike? Yes!
- We can label staves with consecutive production numbers:  Stave-1, Stave-2, Stave-3, ... Stave-199 ...
- Once the staves are installed, they receive numbers that indicate their location. Location numbers and production numbers will be different and can be mapped onto each other using the database.
- The map can be put into excel and posted on the web.
-  That way everybody will know where his/her favorite stave/hybrid/sensor ended up. This knowledge is important for the operation of the detector.