1 / 14

Readout options. Some ideas R. Turchetta, STFC-RAL, UK F.Anghinolfi , CERN

ATLAS CMOS WG1 f2f meeting 20 th February 2014 - CERN. Readout options. Some ideas R. Turchetta, STFC-RAL, UK F.Anghinolfi , CERN. Tony’s slides on 27/1/14. Tony’s slides on 27/1/14. 4. Z-encoding.

didier
Télécharger la présentation

Readout options. Some ideas R. Turchetta, STFC-RAL, UK F.Anghinolfi , CERN

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ATLAS CMOS WG1 f2f meeting 20th February 2014 - CERN Readout options. Some ideas R. Turchetta, STFC-RAL, UK F.Anghinolfi, CERN

  2. Tony’s slides on 27/1/14

  3. Tony’s slides on 27/1/14

  4. 4 Z-encoding Only what I would call the basic unit is considered below. It is close to reticle size, so good for both stitched and non-stitched sensors. All coordinates below list first X dimension then Z. Pixel: 74.5umx50um Segment: 74.5umx800um Number of pixel/segments: 16 Number of segments: 32 Number of contiguous segments in X: 256 Size of sensing area: 19.1mmx25.6mm Number of bits per segment M (X pos.) = 8 N (Z pos.) = 5 Total = 13 Z X

  5. 5 Z-encoding • The next slides will try to answer the following main questions: • How do we get the digital information out of the pixels? • What should go in the periphery of the sensor? • How do we interface with the ABCxxxand what are the implications for the ASIC?

  6. 6 How do we get the digital information out of the pixels? Option 1. Distributed priority encoder Use asynchronous “toggle” per segment: No clock propagation  less power consumption and substrate noise; Asynchronous hit encoding Use priority encoding, for example 4:2 building blocks to build the 32:5 encoding. (see Alice-ITS) 16 input OR

  7. 7 How do we get the digital information out of the pixels? Option 2. Straight wiring 32-bit wide bus from pixels, then priority encoder in the periphery. The bus could be driven by a digital buffer or a current method could be adopted. The trade-off is between power and noise. Need some accurate design to be studied. It would then need an encoder in the periphery 16 input OR

  8. 8 Options review

  9. 9 What should go in the periphery of the sensor? Option 1. Each strip generates 5-bit per hit. It needs an additional 256:8 encoder to generate the X position. After this, one hit would be coded over 5+8=13 bits. Option 2. Each strip needs a 32:5 encoder. Then, as for option 1, it needs an additional 256:8 encoder to generate the X position. After this, one hit would be coded over 5+8=13 bits.

  10. 10 How do we interface with the ABCxxxand what are the implications for the ASIC? Both options are going to generate 13 bits per hit. The information is already encoded, so no need for decoding within the ABCxx DCL not needed. Pipeline size: at the moment 256 bits per BCO. They would become 13*max. number of hits per BCO Data transmission. Q: Would the ABCxxx need to process clusters?

  11. Tony’s slides on 27/1/14

  12. 12 Standard stereo As in Z-encoding, pixel outputs are ORed to generate a single output. Then they connect straight into ABCxxx = ABC130 – front-end

  13. Tony’s slides on 27/1/14

  14. 14 Binary stereo As in Z-encoding, pixel outputs are ORed to generate a single output. 256:8 encoder is integrated in the periphery The ABCxxx receives 8 bits per hit Pipeline size: at the moment 256 bits per BCO. They would become 8*max. number of hits per BCO Data transmission. Q: Would the ABCxxx need to process clusters?

More Related