star-qaboard-l@lists.bnl.gov
Subject: STAR QA Board
List archive
Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeV
- From: Takahito Todoroki <todoroki@bnl.gov>
- To: "Tsang, Chun Yuen" <ctsang@bnl.gov>
- Cc: Muhammad Abdulhamid via STAR-QAboard-l <star-qaboard-l@lists.bnl.gov>
- Subject: Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeV
- Date: Tue, 27 Jun 2023 08:42:53 +0900
Hello Emmy, Tommy, and all,
I have reviewed the bad runs and found the following issues in the shift log. For quite some runs, there was no particular reason to be bad though.
I also spotted possible additional bad runs shown below for your consideration. Other than those, the current bad run list looks good to me.
Thanks a lot for your hard work.
Best regards,
Takahito
new list
Chenliang marked bad
Emmy marked bad
Shift Log
22035002
runidvsavgdedx
#N/A
22038009
runidvsavgdedx
#N/A
22039013
runidvsavgphi
run_vs_avg_phi
TPX[8] was taken out of the run
22039028
runidvsrefmultgt20
run_vs_refmult
22043046
runidvsavgsdcaxyrms
#N/A
Poor good event rate by
bad beam steering
22043047
runidvsavgsdcaxyrms
#N/A
22044003
runidvsavgsdcaxyrms
#N/A
spikes in the TPC Charge_Phi
22044004
runidvsrefmultgt20
run_vs_refmult
22044005
runidvsrefmultgt20
run_vs_refmult
22046006
runidvsavgeta
run_vs_sdca_xy
Vertex_z now spiking toward negative 200 cm
22046012
runidvsavgdedx
run_vs_avg_dedx
22047008
runidvsavgdedx
run_vs_avg_dedx
Beam lost at the end of this run. All the TPC anode tripped,
TPC cathode tripped
22048040
runidvsavgsdcaxyrms
run_vs_avg_eta
Electron cooling off in first 10 min. much higher backgrounds
22048042
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
iTPC tripped
22049026
runidvsavgsdcaxyrms
#N/A
Difficulty with beam squeeze; trigger rate dropped from ~14 to
~4
22049027
runidvsavgsdcaxy
run_vs_sdca_xy
drop in trigger rate mid run (jump from ~14 to ~6)
22049029
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22050003
runidvsrefmultgt20
run_vs_refmult
22050040
runidvsrefmultgt20
run_vs_refmult
22050044
runidvsrefmultgt20
run_vs_refmult
22050045
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22051014
runidvsavgsdcaxyrms
#N/A
iTPC and TPX high dead rate 96%
22052032
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22052033
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
lots of dead time from TPX, iTPC,
22052035
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22052036
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
beam abort during squeeze
22052048
runidvsavgsdcaxy
run_vs_sdca_xy
Trigger hit 100% dead
22053022
runidvsavgphi
#N/A
22054007
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22054022
runidvsavgeta
#N/A
22054028
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
high backgrounds for most of this ru
22054030
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22054042
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22055023
runidvsavgdedx runidvsavgsdcaxy
#N/A
22058037
runidvsavgdedx
run_vs_avg_dedx
22059005
runidvsavgdedx
run_vs_avg_dedx
Unexpected beam abort caused massive annode trips
22061012
runidvsavgsdcaxyrms
#N/A
22061015
runidvsavgsdcaxyrms
#N/A
22062034
runidvsavgeta runidvsavgsdcaxyrms
run_vs_avg_eta run_vs_sdca_xy_rms
shifted z vertex positions, high backgrounds, and low rates of
useable events
22062035
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
High background, few centered collisions.
22062036
runidvsavgsdcaxyrms
run_vs_avg_eta run_vs_sdca_xy_rms
High background, few centered collisions.
22063014
runidvsavgdedx
#N/A
22064025
runidvsavgeta
run_vs_avg_eta
TPC and iTPC 100% busy
22064038
runidvsavgdedx
run_vs_avg_dedx
22065014
runidvsavgsdcaxy runidvsavgsdcaxyrms
run_vs_sdca_xy run_vs_sdca_xy_rms
high beam backgrounds
22065015
runidvsavgsdcaxy runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
high Blue backgrounds
22067039
runidvsavgdedx
run_vs_avg_dedx
22068012
runidvsavgeta
run_vs_avg_eta
22068041
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22069032
runidvsavgsdcaxy
run_vs_sdca_xy
22069034
runidvsrefmultgt20
run_vs_refmult
22069040
runidvsrefmultgt20
run_vs_refmult
22070040
runidvsavgsdcaxy runidvsavgsdcaxyrms
#N/A
high beam background
22071036
runidvsavgdedx
run_vs_avg_dedx
22074042
runidvsavgdedx
run_vs_avg_dedx
22076033
runidvsavgdedx
run_vs_avg_dedx
TPC Anode sector 6 channel 7
22076034
runidvsavgdedx
run_vs_avg_dedx
22077050
runidvsavgdedx
run_vs_avg_dedx
22078016
runidvsavgdedx
run_vs_avg_dedx
22078032
runidvsavgdedx
run_vs_avg_dedx
22079027
runidvsavgdedx
run_vs_avg_dedx
22084029
runidvsavgdedx
run_vs_avg_dedx
22084035
runidvsavgdedx
run_vs_avg_dedx
22085009
runidvsavgphi runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22085021
runidvsavgdedx
run_vs_avg_dedx
22086027
runidvsavgdedx
#N/A
22087027
runidvsavgeta runidvsavgdedx
#N/A
22088034
runidvsavgdedx
run_vs_avg_dedx
22091018
runidvsavgdedx
run_vs_avg_dedx
ShiftLeader Marked as Junk
22093029
runidvsavgdedx
run_vs_avg_dedx
noise in TPC Inner sector 1
22095027
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22096003
runidvsavgsdcaxyrms
run_vs_sdca_xy_rms
22096037
runidvsavgdedx
run_vs_avg_dedx
22097016
runidvsavgeta
run_vs_avg_eta run_vs_avg_dedx
iTPC sector 8, RDO 2 masked
22097030
runidvsavgdedx
#N/A
22098054
runidvsavgdedx
#N/A
22099024
runidvsavgdedx
run_vs_avg_dedx
22099042
runidvsavgeta
run_vs_avg_eta
Short run: unexpected
beam abort
22100045
runidvsavgdedx
run_vs_avg_dedx
22102034
runidvsavgdedx
run_vs_avg_dedx
22103027
runidvsavgdedx
run_vs_avg_dedx
22103032
runidvsavgsdcaxyrms
#N/A
22104027
runidvsavgdedx
run_vs_avg_dedx
22105030
runidvsavgdedx
run_vs_avg_dedx
22106032
runidvsavgdedx
run_vs_avg_dedx
a low number of events because mcr was unable to achieve a
full store in both beam
22108050
runidvsavgdedx
run_vs_avg_dedx
TPC Sector 1, the ADC spike
22109032
runidvsrefmultgt20 runidvsavgphi
run_vs_avg_phi run_vs_refmult
high TPC dead rates
22111047
runidvsavgdedx
run_vs_avg_dedx
22112021
runidvsavgdedx
run_vs_avg_dedx
22113001
runidvsavgdedx
run_vs_avg_dedx
TOF sector 3 down
22113029
runidvsavgdedx
run_vs_avg_dedx run_vs_sdca_xy
22115008
runidvsavgeta
run_vs_avg_eta
Short run: unexpected
beam abort
22115019
runidvsavgsdcaxy
run_vs_sdca_xy
Short run: beam abort
22115032
runidvsavgdedx
run_vs_avg_dedx
22116007
runidvsavgdedx
#N/A
22116008
runidvsrefmultgt20
run_vs_refmult
22116025
runidvsavgdedx runidvsavgphi
run_vs_avg_dedx
iTPC RDO S20:3 keeps on restarting
22116026
runidvsavgdedx
run_vs_avg_dedx
Short run after masking out iTPC RDO S20:3
22116030
runidvsavgdedx
run_vs_avg_dedx
22117023
runidvsavgphi
run_vs_sdca_xy_rms
22118058
runidvsrefmultgt20 runidvsavgsdcaxyrms
run_vs_refmult
22039010
#N/A
run_vs_refmult
Short run: TPX[8]
[0xBA08] died/rebooted
22069030
#N/A
run_vs_sdca_xy
22069033
#N/A
run_vs_sdca_xy
22070007
#N/A
run_vs_refmult
22074009
#N/A
run_vs_refmult
Short run: iTPC Sector 3 RDO 2 issue
22110025
#N/A
run_vs_sdca_xy_rms
22115004
#N/A
run_vs_sdca_xy_rms
22050038
added because of tommy's comment
22070001
added because part of refmult cluster
22070002
added because part of refmult cluster
22070003
added because part of refmult cluster
22070004
added because part of refmult cluster
22070005
added because part of refmult cluster
22070006
added because part of refmult cluster
22070007
added because part of refmult cluster
22070008
added because part of refmult cluster
22070009
added because part of refmult cluster
22070010
added because part of refmult cluster
22070011
added because part of refmult cluster
22070012
added because part of refmult cluster
22070014
added because part of refmult cluster
22070040
added because part of refmult cluster
high beam background
22070041
added because part of refmult cluster
Possible additional bad runs
22031054
Short run: RDO 03: 1 issue
22033001
Short run: TOF HV issue
22042004
Short run: THUB SW
issue
22046007
Short run: no shift log
entry
22048002
Short run: Run stopped
by miss click
22048007
Short run: no shift log
entry
22050006
Short run: Got beam
dump massage in 1 minute
22050016
Short run: TPC anode
sector 11 channel 5 tripped
22057010
Short run: no shift log
entry
22074009
Short run: iTPC Sector 3 RDO 2 issue
22091022
Unexpected beam abort.
A dead spot in TPC Sec.11
22091025
Short run: unexpected
beam abort
22094046
Laser run, no beam
22101015
Unexpected beam abort
22101016
high TPC dead rates due
to an error in RDO 35
22101017
high TPC dead rates due
to an error in RDO 35
22101018
high TPC dead rates due
to an error in RDO 35
22101022
high TPC dead rates due
to an error in RDO 35
22114030
Short run: beam abort
On Jun 27, 2023, at 6:21, Tsang, Chun Yuen via STAR-QAboard-l <star-qaboard-l@lists.bnl.gov> wrote:_______________________________________________Hi Emmy,These are the things I found on shift log. Runs that do not appear here correspond to runs where I found nothing on the shift log.22035002 ETOF sector 18 low hits.22038009 L4 running despite run stopped.22039013 TPX[8] rebooted. ETOF 19-2 empty.22039028 No BEMC22043046 RHIC hit beam pipe22043047 eTOR removed22044003 BEMC LV trip, unusual TPC Charge_Phi spikes22044004 No BTOW22044005 Not BTOW, ETOF EVB ERR22046006 Vertex_z spiking at -200 cm22047008 Beam lost, All TPC anode cathode and eTOF HV tripped22048042 Spike in event rate, eTOF iTPC tripped.22049026 ETOF EVB ERR22049027 Trigger rate drop mid run22049029 ETOF EVB ERR. DAQ ERR mid run22050003 No BTOW, 3 missing columns in eTOF digi density plot.22050040 BEMC box 11 has many time outs.22050044 BTOW LV box 11 has tons of timeouts.22050045 BTOW box 11 is out22051014 ETOF all sector HV trip, iTPC TPX 96% dead22052033 Coherence event, lost half of one beam. Dead time from TPX, iTPC and ETOF.22052036 11 min short run. Beam abort during squeeze.22052048 Trigger 100% dead.22054028 Shift leader observed very high backgrounds.22054030 FCS 100% dead.22058037 ETOF EVB ERR22059005 Unexpected beam abort. TPC HV tripped22061012 BTOW issues22062034 z vertex shifted.22062035 Shift leader observed high background.22062036 Shift leader observed high background.22063014 New dead area in BEMC.22064025 TPC and iTPC 100% busy22065014 Tune drifted, backgrounds way up22065015 Blue backgrounds high22068041 eTOF busy, didn't stop for beam dump.22070040 Beam hitting top of beam pipe.22076033 TPC anode sector 6 ch 7 tripped22076034 holes appear in BTOW22078032 GMT HV alarm. u3 became black.22084029 Two cold tiles in EPD22091018 MarkedJunk Shift leader marked as junk22093029 Noise in iTPC sector 122097016 short after mask iTPC sector 7, RDO 222097030 EPD had cold tile, ETOF had a column out.22099042 Beam lost with only 500 hlt good events.22106032 MCR unable to achieve full store.22109032 Extra hot sectors in TPC due to crate vme 55 being on.22111047 Lots of ETOF modules are blank in digi density plot.22112021 Empty boxes in BEMC, hot tower.22113001 TOF was in standby22113029 4 modules out for eTOF.22115008 Unexpected beam abort22115019 Beam abort22115032 No cooling for this store. Missing eTOF strips22116007 BTOW HP trip22116025 iTPC RDO S20:3 keeps on restarting.22116026 Short run22116030 eTOF 20-2, 20-3 missing22118058 TPC gas alarm, missing EPD tiles, VME crate is off.22039010 TPX[8] died/rebotted22069033 ETOF 19-1-2 is out22074009 Short run, iTPC S3 RDO 2 failed.22050038 BTOW tripes. Run ended early.22070001 BTOW removed22070004 eTOF 19.1 disappeared.Best wishes,TommyFrom: STAR-QAboard-l <star-qaboard-l-bounces@lists.bnl.gov> On Behalf Of Duckworth, Emilie via STAR-QAboard-l
Sent: Monday, June 26, 2023 3:19 PM
To: Ma, Rongrong <marr@bnl.gov>
Cc: Muhammad Abdulhamid via STAR-QAboard-l <star-qaboard-l@lists.bnl.gov>
Subject: Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeVok, sounds good!here is the final list then for Takahito to review:
Sent: Monday, June 26, 2023 12:02 PM
To: Duckworth, Emilie <educkwor@kent.edu>
Cc: Muhammad Abdulhamid via STAR-QAboard-l <star-qaboard-l@lists.bnl.gov>
Subject: EXT: Re: [STAR-QAboard] badrun cluster from refmult QA plot @7.7 GeVHello EmmyThanks for looking into this in detail. I would still like to suggest to add these two groups to bad run list. The reason the second group was marked as good is that they are fine within their own region. However, the centrality calibration is not typically done for different regions, which means the calibration parameters based on the majority of data are not suitable for this particular group of runs. The effect is small, but I do not think it is correct in principle. This is also why I suggested to perform only global rejection for refMult with a tighter criterion.Thanks.BestRongrongOn Jun 26, 2023, at 2:07 PM, Duckworth, Emilie via STAR-QAboard-l <star-qaboard-l@lists.bnl.gov> wrote:Hello all,At Friday's meeting, we arrived at the conclusion that we should move forward with the badrun list presented, with the addition of a cluster of events seen in the refmult QA plot that looked like they were arbitrarily included as "good" when they shouldn't have been.Zooming into that section, it is clear why some were marked as good and some were marked as bad. There were 2 run number clusters close together, one that averaged around 100, with a few dropping down to 90, and one that averaged around 90 for the whole cluster. it was the few dropping down to 90 that were marked as bad, and the neighboring cluster, which were all consistent with each other were all marked as good. A detail that was not clear from such a zoomed out plot.With this in mind, I propose we do NOT add this cluster to the bad runs list, and continue one with the list presented at Friday's meeting, no edits. except for ones suggested by Takahito as a third party review.Emmy<refmultgt20_2023-06-26.png>_______________________________________________
STAR-QAboard-l mailing list
STAR-QAboard-l@lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-qaboard-lCAUTION: EXTERNAL SENDER Do not click any links, open any attachments, or REPLY to the message unless you trust the sender and know the content is safe.
STAR-QAboard-l mailing list
STAR-QAboard-l@lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/star-qaboard-l
-
[STAR-QAboard] badrun cluster from refmult QA plot @7.7 GeV,
Duckworth, Emilie, 06/26/2023
-
Re: [STAR-QAboard] badrun cluster from refmult QA plot @7.7 GeV,
Ma, Rongrong, 06/26/2023
-
Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeV,
Duckworth, Emilie, 06/26/2023
-
Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeV,
Tsang, Chun Yuen, 06/26/2023
- Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeV, Takahito Todoroki, 06/26/2023
-
Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeV,
Tsang, Chun Yuen, 06/26/2023
-
Re: [STAR-QAboard] EXT: Re: badrun cluster from refmult QA plot @7.7 GeV,
Duckworth, Emilie, 06/26/2023
-
Re: [STAR-QAboard] badrun cluster from refmult QA plot @7.7 GeV,
Ma, Rongrong, 06/26/2023
Archive powered by MHonArc 2.6.24.