Skip to Content.
Sympa Menu

sphenix-maps-l - Re: [Sphenix-maps-l] next MVTX Electronics meeting tomorrow 2/1 at 1pm Eastern

sphenix-maps-l AT lists.bnl.gov

Subject: sPHENIX MAPS tracker discussion

List archive

Chronological Thread  
  • From: Yasser Corrales Morales <ycorrale AT cern.ch>
  • To: sphenix-maps-l AT lists.bnl.gov
  • Subject: Re: [Sphenix-maps-l] next MVTX Electronics meeting tomorrow 2/1 at 1pm Eastern
  • Date: Thu, 1 Feb 2024 10:11:17 -0700

Hi,

BUSY and BUSY VIOLATION are known features of ALPIDE chips which are asserted due to long readout time, from high occupancy or short trigger frame rates, during normal readout operation of the ALPIDE chip depending of the chip readout configuration (continuous or trigger mode, please note this is internal chip configuration and different from the detector readout mode). BUSY VIOLATION will mask or skip a single trigger frame but will not crash the RU DATAPATH readout. 

This situation are different from beam background events when the time readout frame are longer then the set event timeout and the datapath is disable for the rest of the run.

Cheers,

Yasser.

On 2/1/24 09:23, Liu, Ming Xiong via sPHENIX-MAPS-l wrote:

Thank you Ed, good to see the detailed analysis there. The cause of the “busy violation” is indeed from the same origin, too many hits to readout in time.

 

Cheers,

Ming

 

-- 

Dr. Ming Xiong Liu

P-3 Group, MS H846

Nuclear and Particle Physics & Applications

Physics Division

 

Office: 505.667.7125

Mobile: 505.412.7396

Los Alamos National Laboratory

 

From: Ed O'Brien <eobrien AT bnl.gov>
Date: Thursday, February 1, 2024 at 9:08 AM
To: Jo Schambach <schambachjj AT ornl.gov>, SPHENIX MVTX <sphenix-maps-l AT lists.bnl.gov>, "Ming Liu (BNL)" <ming AT bnl.gov>
Cc: John Haggerty <haggerty AT bnl.gov>, Kin Yip <kinyip AT bnl.gov>, Martin Purschke <purschke AT bnl.gov>
Subject: Re: [Sphenix-maps-l] next MVTX Electronics meeting tomorrow 2/1 at 1pm Eastern

 

    Hi Jo and Ming,
     I am reviewing the ALICE FOCAL TDR and see that their EM section
    of the FOCAL uses MAPS ALPIDE pixels sensors for readout, interleaved
    with W plates. The TDR has a long description of how they will
    deal with what they call "BUSY violations" in the ALPIDE readout from
    high multiplicity events. As far as I can tell this is the identical
    data-hang situation that we are experiencing with the MVTX.
    I have posted the ALICE FOCAL TDR at the top of the Indico page for
    today's MVTX electronics meeting:
    https://indico.bnl.gov/event/22140/

    Perhaps the MVTX electronics experts already know all of this information
    or even contributed to this section of the TDR, but if one looks at
    p. 24-38 you can read a detailed description of how ALICE plans to
    deal with the BUSY-violations in their future FOCAL.
    I find it interesting reading. Thanks.

    Ed




On 1/31/24 8:59 AM, Schambach, Jo via sPHENIX-MAPS-l wrote:

What:    Weekly MVTX Electronics meeting

When:   1 February 2024, 13:-00 EST

Indico:   https://indico.bnl.gov/event/22140/

Zoom:   https://bnl.zoomgov.com/j/1603202671?pwd=Qng1QjhyWVV0YTA0VXV3dzNOWHQyUT09

 

I will be in a workshop tomorrow all day, so I won’t be able to host this myself, but provided the indico and zoom coordinates here for the meeting

 

Joachim Schambach

Oak Ridge National Laboratory

PO Box 2008

Bldg. 6000, MS 6368, Rm 205-C

Oak Ridge, TN 37831-6368

Phone: (865) 341-0694

Email: schambachjj AT ornl.gov

 




_______________________________________________
sPHENIX-MAPS-l mailing list
sPHENIX-MAPS-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-maps-l




_______________________________________________
sPHENIX-MAPS-l mailing list
sPHENIX-MAPS-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-maps-l



Archive powered by MHonArc 2.6.24.

Top of Page