Name: INTT Weekly meeting
Start: 2025-10-23T20:00:00-04:00
End: 2025-10-23T23:00:00-04:00
Location: No location set

Hide

[Aki: Run24 documentation]
- Now collecting information of Run24 data production, and good/bad
run list for MVTX, INTT and EMCal for Si-Calo tracking.
- Some of the Run24 data were already deleted from disk and exist only in HPSS.

There are minutes attached to this event. Show them.

- 1
  
  OfflineQA
  
  Speaker: Yuko Sekiguchi (RIKEN)
  
  20251023_OfflineQA.pdf
  
  [Yuko:Offline QA]
  - How the other two bad runs with ~90% good channel look like?
  --Tow bad runs looks different issue from the last one. Those have
  apparently the DAQ (probably clock sync) issue.
  -- The 3rd one is not clock issue. Questionable tag will be appropriate.
  -- Maybe <90% good channel is tagged as bad run, and 90%<good
  channel<92% is questionable tag?
  - Around 75000 after DAC0 change has a minor issue on the calibration.
  See the details in Jaein's presentation.
- 2
  
  Offline QA check(2)
  
  Speaker: Jaein Hwang (Korea University)
  
  INTTmeeting_track_10_24.pdf
  
  [Jaein: Offline QA check 2]
  - What is reason of high good channel ratio for runs before DAC0 update?
  -- Maybe the beam condition get better or some change other than the
  INTT cause the good channel fraction.
  - In the official production, bad channels are excluded in the
  clustering stage, but not in the rawhit DST production.
  -- They are excluding bad (cold/hot) channel based on the good/bad
  channel info in the CDB database.
  -- It would be nice to have some different categorization like hot,
  and very hot channels, then production can choose which tag is used in
  the clustering.
  -- Currently the production is using one CDB parameter (not
  run-by-run), so it would be nice to reproduce the data with different
  hot/cold category in the future re-production.
  - Keep DAC0=25 for the time being as long as it doesn't disturb DAQ.