gtpc decoding n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
GTPC decoding PowerPoint Presentation
Download Presentation
GTPC decoding

Loading in 2 Seconds...

play fullscreen
1 / 7

GTPC decoding - PowerPoint PPT Presentation


  • 149 Views
  • Uploaded on

GTPC decoding. Zolt án Fodor KFKI – Research Institute for Particle and Nuclear Physics. The problem was: No hit in the simulated GTPC hits in the 3. 4. 7. padrows After some error ignorance I could see only the first pad hits with om.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'GTPC decoding' - flower


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
gtpc decoding

GTPC decoding

Zoltán Fodor

KFKI – Research Institutefor Particle and Nuclear Physics

slide2
The problem was:

No hit in the simulated GTPC hits in the 3. 4. 7. padrows

After some error ignorance I could see only the first pad hits with om

slide3
In the GTPC we have 7x96 pad, but we are using the VTPC or HR configuration on MB readout.

 padrow #1 contains information of 1. and 3. padrow

padrow #2 contains information of 2. and 4. padrow

padrow #3 contains information of 5. and 7. padrow

padrow #4 contains information of 6. padrow

slide4
d) PADR

The TPCs are numbered from 1 to 4 in order VTPC1, VTPC2, MTPCL and MTPCR.

The sectors in each TPC are numbered from 1 to 6 (VTPC) and 1 to 25 (MTPC) with the

convention that sector 1 in each TPC is upstream and towards the Jura. Numbering always

increases in the direction of increasing z (i.e. in the beam direction.)

Pads are numbered from 1 to 192 (VTPC and HR sectors in MTPC, i.e. 20-25 for MTPCL

and 1-5 for MTPCR) and 1 to 128 elsewhere. Pad numbers increase from Saleve to Jura.

In the case of VTPC1, not all pads are instrumented.

The BOS bank numbers are constructed from the TPC number, the sector number and the pad

row number as follows:

The PADR BOS bank number is then:

TPC# * 216 + Sector# * 28 + padrow#

The definition of the PADR bank is thus:

word 1 bank name PADR

2 bank number (See definition above)

3 reserved 0

4 number of data words following n

data The data are organised in bytes, padded with zeroes to fill n

integers as necessary.

byte 1 pad number (high byte: will be zero)

2 pad number (low byte: in range 1 to 192)

3 status: bit 0: data are compressed (status=1)

bit 1: data are not compressed (status=2)

bit 2: gain calibrated data (status=5 or 6)

Bit 3: t256 timeslices mode

slide5
a) for uncompressed data, (status=2) 512 bytes of time information follow and then the

structure is repeated with the next pad number.

b) for compressed data, (status =1) the data are as follows1

byte 4 0

5 0£repeat count £ 255: the number of additional zeroes

6 hit: 8 bits of ADC time bucket information

7 to n further hits. this sequence ends when the next zero is

encountered

n+1 0 end of sequence of hits

n+2 0:£ repeat count: £ 255: the number of additional zeroes

n+3 further hits. this sequence ends when the next zero is

encountered

This sequence continues until all 512 time buckets have been accounted

for from the current pad. At this point a new pad number will follow:

byte m pad number (high byte: will be zero)

m+1 pad number (low byte: in range 1 to 192)

m+3 status

slide6
a) for uncompressed data, (status=2) 512 bytes of time information follow and then the

structure is repeated with the next pad number.

b) for compressed data, (status =1) the data are as follows1

byte 4 0

5 0£repeat count £ 255: the number of additional zeroes

6 hit: 8 bits of ADC time bucket information

7 to n further hits. this sequence ends when the next zero is

encountered

n+1 0 end of sequence of hits

n+2 0:£ repeat count: £ 255: the number of additional zeroes

n+3 further hits. this sequence ends when the next zero is

encountered

This sequence continues until all 512 time buckets have been accounted

for from the current pad. At this point a new pad number will follow:

byte m pad number (high byte: will be zero)

m+1 pad number (low byte: in range 1 to 192)

m+3 status

slide7
In the om, the format taken from data, no parameter at startup

The dipt has a parameter to force the t256 mode

After adding this “t256” bit to the MC data I can see with om the simulated tracks correctly

Modification in the MTSIM/src/bos.c and GTEMBED_GTPC/src/gtembed.c

Reordering the GTPC data in: MTSIM/src/sim.c