star-qaboard-l@lists.bnl.gov
Subject: STAR QA Board
List archive
- From: weidenkaff@physi.uni-heidelberg.de
- To: star-qaboard-l@lists.bnl.gov
- Subject: [STAR-QAboard] eTOF issues shown yesterday
- Date: Sat, 13 Feb 2021 07:52:08 +0000
Hello Everyone,
I checked on some of the eTOF issues shown in yesterday:
1. Missing hits in module 23-3:
This one is a calibration issue. Module 23-3 was exchanged for this years run and thus the calibration from last year is not valid any more. All hits are shifted along the y-axis due to different time offsets between the sides. This can also be seen in the HLT plots. The plot with the missing hits shown in the meeting however contains a cut on the y-position of hits to reject wrongly reconstructed hits. Since all hits are shifted, this rejects almost everything. No problem for the raw data/final production.
Module 19-2 is intentionally turned off due to read-out instability
2. empty plots for runs 22038004 22038005 and 2204017:
I can confirm that there are indeed no eTOF data in these runs. One can "reproduce" this issue also in the online plots if the "with eTOF" trigger is active, but "eTOF busy" flag is not yet cleared by the shift crew (as i needs to be done during the ramping). I assume that this was missed for these runs.
Best Regards
Philipp Weidenkaff
I checked on some of the eTOF issues shown in yesterday:
1. Missing hits in module 23-3:
This one is a calibration issue. Module 23-3 was exchanged for this years run and thus the calibration from last year is not valid any more. All hits are shifted along the y-axis due to different time offsets between the sides. This can also be seen in the HLT plots. The plot with the missing hits shown in the meeting however contains a cut on the y-position of hits to reject wrongly reconstructed hits. Since all hits are shifted, this rejects almost everything. No problem for the raw data/final production.
Module 19-2 is intentionally turned off due to read-out instability
2. empty plots for runs 22038004 22038005 and 2204017:
I can confirm that there are indeed no eTOF data in these runs. One can "reproduce" this issue also in the online plots if the "with eTOF" trigger is active, but "eTOF busy" flag is not yet cleared by the shift crew (as i needs to be done during the ramping). I assume that this was missed for these runs.
Best Regards
Philipp Weidenkaff
- [STAR-QAboard] eTOF issues shown yesterday, weidenkaff, 02/13/2021
Archive powered by MHonArc 2.6.24.