INTT Weekly meeting

Thursday 2 Oct 2025, 20:00 → 22:00 US/Eastern

Meeting URL 

https://riken-jp.zoom.us/j/92149923535?pwd=sbLcakxQeRQrch8dnJfJ8g1NiEdvKa.1

20:00 → 20:20 INTT behavior in silicon seeds

INTT behavior in silicon seeds (maybe interesting for you?)

Speaker: Cheng-Wei Shih (National Central University)

INTT_2025_10_03_SiSeed_InttTimeMM.pdf

- Bumps in the INTT timing bucket are separated with 120 BCO space, which is consistent with the number of RHIC bunches.
- This analysis require +- 1 BCO timing.

-- It was lucky for dN/deta analysis because it was 56x56 bunches data and there is no collision from neighbor BCO.
- Current silicon seed requires only geometrical matching but not INTT timing matching.
- Takashi also saw 2nd peak separated by 120 BCOs before.
-- Separation is not necessary to be 120, 240 ... but 230 is also possible even if it is a small fraction.
- It is a problem of silicon seeding algorithm to integrate over long time frame.

-- You should start silicon seeding with INTT cluster only with right timing, then confirm MVTX track matching.

-- Out of INTT timing is mostly accidental matching.

-- Electrical noise from hot chips/channels contributes such accidental hits.

-- Nice to have a material to convince the tracking group to make INTT timing the anchor for the silicon seeds.

- Integration time of MVTX 100 BCOs
- Requiring 3 clusters at MVTX but less than 2 intt clusters may be very soft particles.
-- Exclude such soft particles and focus on high pT. 

-- You can limit delta-phi e.g 0.01 to exclude soft particles.

20:20 → 20:40 Offline QA update

Speaker: Joseph Bertaux (staff@purdue.edu;student@purdue.edu;member@purdue.edu;employee@purdue.edu)

bertaux_2025_10_2.pdf

- Intt2 felix ch4 is masked
- What kind of requirement we used as a good BCO timing for Run24? It is make sense to have a similar or same criteria as Run24.

-- Every felix server should have the same peak. There was no case like 1 or 2 felix channel has mismatched timing.

- Jaein developed some infrastructure to show time dependence of BCO timing using calibration module.

- It would be good to script to automatically input the INTT timing QA into run triage database.

-- Jaein has a useful python script to do it.

- For Run24, the BCO QA is done after masking hot chips.

-- Check the difference between with/without masking chips.
- Need to check more runs to check the stability of the timing this year.

- Yuko will present an summary slide for the offline QA to discuss more next week.

20:40 → 21:00 Chip saturation issue for half-entry chips

Speaker: Tomoki Harada

251003_ChipSaturationForHalfentry_Tomoki.pdf

- The half-entry chip returns the output values for every other channels, so the cluster size is suppressed so small.
- The new digital control parameters which mitigate the half-entry issue are being used for the current operation.