Commissioning and running of sPHENIX

[Itaru Nakagawa <itaru AT riken.jp>]

Dear Jaebeom,

 Thank you very much for organizing the meeting today. There were a lot of symptoms reported in the meeting:

o Data process stops at 78 kEvents (Slide 10 of Takashi's presentation)

o BCO stuck in ddump (Slide 9 of Takashi's presentation)

o Dozen of nonsense BCO found in a run (Reported by Joseph)

 Although we don't know if all these issues are correlated or not yet, I can tell that they are all coming from the same origin, i.e. Incorrect BCO stamp in the data. So definitely we need Raul and possible rcdaq experts to look into the cause why these irrelevant BCO stamps are injected into data. I believe it will read to the intrinsic solutions.

 I wonder if nonsense BCO stamp can cause different symptoms as above depending on the applications like ddump, event combiner, etc depending on how different codes handle and recover from it once these codes picked up the nonsense BCO in the data. This has been my question since we discussed this issue in the INTT weekly meeting last week.

Regards,

-itaru

On 2024/08/04 23:44, Park, JaeBeom wrote:

Dear all, 

As announced by Jamie on Friday, we will have a special meeting to discuss the BCO alignment & potential data drop for the tracking subsystems (INTT, TPC/TPOT, MVTX). 

Date : Monday, Aug 5th at 1:30 PM ET

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

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

Best,

Jaebeom 

===============================
|| JaeBeom Park
|| Postdoctoral Associate 
|| University of Colorado Boulder
|| E-mail : jpark4 AT bnl.gov
|| Phone : (934) 386-1466
===============================