Skip to Content.
Sympa Menu

sphenix-run-l - [Sphenix-run-l] Dedicated Work Session on MVTX/INTT/TPOT BCO alignment / data integrity checks

sphenix-run-l AT lists.bnl.gov

Subject: Commissioning and running of sPHENIX

List archive

Chronological Thread  
  • From: Jamie Nagle <jamie.nagle AT colorado.edu>
  • To: sphenix-run-l AT lists.bnl.gov
  • Subject: [Sphenix-run-l] Dedicated Work Session on MVTX/INTT/TPOT BCO alignment / data integrity checks
  • Date: Tue, 11 Jun 2024 13:25:40 -0400

Hello All (cc sphenix-run-l for the announcement),

The meeting / working session focused on MVTX/TPC/TPOT BCO alignment / data integrity checks issue(s) will be tomorrow:

Wednesday, June 12, 2024 from 1:30 pm - 3 pm, and below are the Zoom coordinates.     

Zoom coordinates

https://bnl.zoomgov.com/j/1614645041?pwd=bmE4STBRZk5tVVVUUC8zRnQxSlFyQT09


I would like this to be a working session,  i.e., after some  discussion, really writing, sharing code...
The basic idea (as discussed previously) is to check in offline code for what fraction of GL1 triggers (GL1 data and its BCO), do we have data from the MVTX, INTT, TPOT covering that BCO.      It is important to check individual packets and then what fraction of events have the entire detector.     It would be good in each  case to pick  a few runs, at least one where you  know part of the detector dropped out (i.e., a test case that should definitely  show missing data).     
 
There has also been discussion about whether with the MVTX, INTT, TPOT one can tell if data is simply missing, or if that segment of the detector had no hits.    My understanding (glad to be corrected) is that all systems send a header with the BCO, even if all pixels, strips, whatever, had no hits.

Sincerely,

Jamie

||------------------------------------------------------------------------------------------
|| James L. Nagle   
|| Professor of Physics, University of Colorado Boulder
|| EMAIL:   jamie.nagle AT colorado.edu
|| SKYPE:  jamie-nagle        
|| WEB:      http://spot.colorado.edu/~naglej 
||------------------------------------------------------------------------------------------



Archive powered by MHonArc 2.6.24.

Top of Page