• Created by Unknown User (phansson), last modified on Aug 28, 2009

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Introduction

There are three periods of test beams in which 3D sensors will be tested at CERN. This page contains a placeholder for notes/reminders for preparation.

MCC board

Description of the board and how to operate it here: MCC boards at SLAC.

Todo list

Hardware modifications on TPLL for use with the EUDET telescope Jens

Suggestions is to modify one board that can be used with the EUDET all the time plus one spare. Proposed to make a new board but apparently there are new boards with strange problems according to Jens and so we need to modify an existing one. The modification takes about 1 week.

  • Which TPLL boards are modified?
Modification of the Oslo reconstruction code Ole

According to Ole this is a very simple change to identify the chips.

Modify the BAT online monitoring Pelle hopefully with help of BAT expert

After discussion with Jens it seems like the best way to handle it is to modify the BAT online monitoring in order to keep TurboDaq software intact. We need to identify how the data stream from the module is read and identify how to separate up the chips. The online monitoring display should be re-usable.

Implement the ATLAS module/MCC in the EUDET framework Georg

Mail from Georg:



Hi,
Am 26.08.2009 um 17:27 schrieb Jens Weingarten:

Hi Georg,

yes you can start using a normal module, as for TurboDAQ the MCC board will lokk like a module with only N (N<16) chips.
Did you get to talk to Markus about that?

Yes I did, We came to the same conclusion. But, you can always say 'the system should behave like this'. But as you also agree, I will start with reading out from a module. Do you still think that its nesessary to test these extension with a read multichipboard as a final prove?

At what place in the code are you planning to separate the module data stream into single chip data streams? I would propose to do that before you write the data to the shared buffers, so that for the telescope software (regardless if you're using BAT or EUDET) it looks like you have N separate DUTs.

In fact there a no shared buffers anymore. The Eudet-Extension do come with a complete redesign on the read-out and logging-software.
There is a new function in TurboDAQ that is called every time a event is read-out from the FIFOs. At the moment this function 'just' sends this whole event to the DataCollector of the Eudet-Framework. But I guess it will be easy to decide if a event did happen in sensor A or B. In this case I need to send this event as an event of Sensor A or B. As the Eudet-Framework is already prepared to receive Data from one Producer that contains more than one sensor-plane this will be a piece of cake, to say it with your words, Jens. (wink)

With this its also easy, as I do believe, to integrate this is the online-monitoring software. And it should be easy as well to do correlations between the planes. But I haven't tested the online-software yet in detail.


That will prevent us from having to change online monitoring or even analysis code to account for use of the MCC board.
Let's talk about that also next week on the phone. Per will not be available, but I think I understand the board well enough to get you started.


Ok

See you,
Jens


Georg Troska schrieb:
Dear Per,

I would like to plan the next steps to find a possibility to make the MultiChipBoard running with the Eudet Extensions.

First of all: What is your current status? You said in your last email that you still need to test if all chips are working simultaniously..? Have you found out something? I would like to start with the integration of this multichipboard during the next days - it shouldn't take so long. Currently I have no idea how this works. Is it necessary to use the multichipboard itself or can I use a 'standard module' for the first tests. I'm not realy sure if they are really compatible. Are you?

Currently I'm working on the nominal single-chip-assembly extension. The software is already running, I'm just changing the GUI to make it nice (wink)

Georg


Hi Per,

as I do understand the telescope itself is not necessary for testing the readout-chain.
I have a complete-version of the eudet-framework with the whole readout-chain running here. I am also using the Eudet-Trigger-Logic-Unit. When the system is running here there should be no reason why it should not be running with the eudet-telescope

I will be at CERN from 7th Sep. Maybe you are there as well? Maybe we could find time discuss a few things. Once the readout with the module is running it could be interesting to test the readout with your multi-chip card. Would it be possible to send it here?

Georg

MCC tests at CERN Alessandro & Pelle
  • Run source scan with >1 chip, moving the source over the chips to see hits in all attached chips for same source scan Pelle & Alessandro
  • Run with BAT software after modification to check online monitoring
    • To see correlated plots we could either use cosmics with a stack of chips or a source. The latter option has the problem of penetration depth and the former has the problem of statistics?

DUT's & rough run plan

10-17 October
  • List of devices under test
    • STA-3D (2E,3E and 4E?)
      • Check if the 2E and 4E can be revived Pelle, Alessandro
    • CNM
    • SINTEF
    • FBK (irradiated?)

Run plan
Should focus on measurements that require the extra resolutions

  • Charge sharing
  • Electrode charge collection efficiency
24-04 November

This assumes that we have access to the Morpurgo magnet.

  • List of devices under test
    • STA-3D (2E,3E and 4E?)
    • CNM
    • SINTEF
    • FBK (irradiated?)
  • Mounting (using BAT either in H6 or H8) ?
    • Prefered choice: Use the cooling box prepared for EUDET TB period (above), needed if we test irradiated sensors
    • Backup choice is to use box from May if there is NO? required cooling

Run plan
Should focus on the measurements to validate the 3D performance and fill in the information we are lacking from the May TB.

  • Angle scan
  • Magnetic field strength scan
20-25 November

This period is in H6 without magnetic field.

DUT's
  • List of devices under test
    • STA-3D (2E,3E and 4E?)
    • CNM
    • SINTEF
    • FBK (irradiated?)
  • Mounting
    • Same comments as above.
    • Irradiated sensors should be available, see earlier comments on mounting

Run plan

  • No labels