sphenix-run-l AT lists.bnl.gov
Subject: Commissioning and running of sPHENIX
List archive
[Sphenix-run-l] sPHENIX Shift Change Notes (Sunday, June 25, 2023)
- From: Jamie Nagle <jamie.nagle AT colorado.edu>
- To: sphenix-run-l AT lists.bnl.gov
- Subject: [Sphenix-run-l] sPHENIX Shift Change Notes (Sunday, June 25, 2023)
- Date: Sun, 25 Jun 2023 16:22:11 -0400
----
General (Stefan/Kin)
Current Priority Items (PC)
Work Control Coordinators (Chris/Joel)
Plan of the Day (Stefan/PC/all–to be revisited at end of meeting)
Current plan - shift crew & experts running for the weekend
111x111, 2 mrad, 8 hour stores, field on, global mode, MBD,ZDC,LL1,HCal,EMCal(5/8)
→ continue updating instruction manual, recovery directions
→ experts requested to check online monitoring and update (MBD, HCal, EMCal)
Per Stefan’s email — |
“We’ll have a meeting in the 1008 conference room at 10:00am tomorrow (Monday) to discuss the plan of the day regarding tomorrow's access vs DAQ work. DAQ experts and people who would like to take advantage of the access should attend (we’ll also dial into the SSM zoom).”
Expect 4 hour access sometime on Monday (not yet determined)
→ 2 hours to remove TPC one-laser (Azmoun + Frank)
→ MBD to check one cable , test cable/channel swap (check ?)
→ check out HCal ADC crate (potential voltage/backplane issue)
4 hours if we need to swap that crate (or may need to plan later)
→ check out HCal pre-amp issue (maybe 2 hours)
Monday-Tuesday this coming week
Acquire input from TPC group about next 2 weeks of potential zero field running
Also, input from Kin on magnet, how long to leave on for nowAssess information from analysis of MVTX with single beam tests etc., and then follow up with meeting with machine people
MBD performance update → coordinate with Commissioning Task Force
Priority items for next week: GL1/GTM firmware update, GL1 readout, RevTick implementation, DAQ monitor, further checks on ADC/XMIT issues
→ Chi is in 1008 on Monday 9-5:30 pm, and so this is a likely focus
=================================================================
Evening (Derek Anderson, Sijan Regmi, Justin Bryan)
Inherited fill 33902 from day shift
Lasted up until owl shift began
Jaebom and us tested latest instructions running GTM in global mode
Ran more-or-less continuously from 7:50 pm onwards
Was able to take 9 runs with about 4.8M events in total
Observations:
More often than not, run would end when seb02 (EMCal) froze
When MBD presecale was set to 0, seb15 (LL1) choked
Night (John Lajoie and Justin Frantz)
(0:20 AM) Beam dumped as scheduled
(1:04AM) New store #33903, 111x111 @ 2mrad, initial sPHENIX ZDC ~9kHz
(08:00AM) ~9.2M events in 13 good runs!
Day (Charles Hughes, Alex Holt, and Pedo Nieto)
(8:00 AM) inherited store #33903
(8:00 AM - 9:00 AM) Taking DATA !
EMCAL + HCAL + MBD + LL1 + ZDC
2 good runs - thanks to owl shift for detailed instructions!
(9:05 AM) MCR called, said beam dump would come a little later
Issue with AGS injection field not stable
MCR fixing
(9:15 AM) Planned beam dump
(9:25-9:40 AM) DO (Pedro) recovered EMCAL tripped bias channel
(10:00 AM) New store # 33904, 111x111, 2 mrad x-ing angle, 10 kHz ZDC initial
(10:10 AM) Began new round of data taking (same detector config as before)
(10:10-10:50 AM) some troubleshooting - problems with sebs not starting events
(11:00 AM) good runs returned
(11:00 AM) Different EMCAL bias channel tripped
Asked EMCAL if 3 trips/24 hours was expected - they said yes
(12:30 PM) Chris Pinkenburg Called - Data Transfer from BBOX hanging
“Please under no circumstances run an ls of any subdir under /sdcc on the buffer boxes”
(1:20 PM) HCAL OnlMon plots looked odd
Bimodal Avg ADC in Towers vs Sample #
Called Virginia
(2:00 PM) GTM Server Failed
Reason Unclear, occurred after dcminit but not sure that was the cause - Martin rebooted, seems to be working
(3:30 PM) Data taking ongoing
Runs 15035 - 15049
SUM OF EVENTS IN GOOD RUNS: 8.3M (and counting)
Seb02 is most common failure mode (stopped incrementing 1048577 events)
PLEASE REMEMBER TO HAVE D.O. RECOVER TRIPPED EMCAL CHANNEL BETWEEN FILLS - MAY NEED EXPERT CALL, SHOULD FOLLOW E-LOG POST
=======================================================================
Magnet (Kin)
Nothing new to report.
MBD (Mickey, Lameck, Alex, Abdull)
Today the MBD rate (500-600Hz) 2 mRad xing angle is lower than yesterday's (500-1000 Hz) 2 mRad xing angle.
The ZDC rate had changed from yesterday's 3kHz to today’s rates (8kHz & 4kHz) because there was no leveling with this new beam that we are getting.
Today’s plots are better than yesterday’s plots, with almost a single peak at the center.
Trigger (Dan)
GTM/GL1 (Martin/Dan/John K)
DAQ (Martin/John H)
MVTX (Yasser/Hao-Ren)
Continuing analyzing data from single beam and not collisions runs.
Problematic events most probable coming from beam background rather than halo muons, dE/dx > 100 KeV, compare with dE/dx from muon ~ MIP
TPC (Jin, Takao, Evgeny, Charles )
Update on CF4 situation from Rob - when will we run out?:
“At the current rate, about 3-4 weeks. Fast flow, 1-2 weeks. Vendor is waiting for customs to give her an estimate of release. I will follow up with buyer on monday to get a plan b if the vendor doesn’t give us a delivery by then.”
Update on Bob Azmoun’s status if Monday access starts later:
“If the access starts later in the day, that will be fine. I can stay very late tomorrow if needed. Besides, I think I'll only need one hour for the job.”
Analysis continuing on HV + Collisions + Magnet Data
Still conferring amongst ourselves about what’s next wrt to collisions
Still conferring amongst ourselves about what‘s next wrt “no magnet” running
HCal (Virginia)
Continued data taking + analysis of data
Day shift pointed out strange behavior in online monitoring plot of average ADC vs time sample- checked timing and that looks okay. Need to check what caused this in offline analysis (maybe just some noisy hot channel?)
Plan to test LED running more next week
Virginia + Jaebeom will do first few tests to make sure we can get out of normal running and back into normal running without issue
Need shift crew to be running on operator1 to be able to run LEDs
Question on HCal timing:
Currently we aren’t adjusting the timing as long as the waveforms are within our sample window to avoid having to rerun setups that sometimes fail
Plan is to time in to time sample 6 when the timing is expected to be stable between stores
Eventually we need to have data which is centered at time sample 6 to get optimal performance of template waveform fitting to understand its performance
Do we know when we expect to have stable timing?
EMCal ()
Nothing to report
Shift crew reset tripped SiPM bias voltage per Tim’s instructions
TPOT (Hugo)
Nothing to report
INTT ()
sEPD()
Gas/Cooling ()
ZDC (Ejiro/JohnH/Peter)
Analyzing data as they become available for the ZDC
Currently working on a potentially good run with the MBD + ZDC (run 14266). According to John H, the first 50k events appear to have good alignment for the MBD
Working on the ZDC calibration using the ZDC single neutron peak (got some resources from Peter on this)
- Would it make sense to schedule a 0 crossing short data taking with the ZDC and then steer into the 2mrad?
Background Counters ()
Online Monitoring (Chris)
Are the online monitoring plots being saved? If so, how can experts access them?
|| James L. Nagle
|| Professor of Physics, University of Colorado Boulder
|| SKYPE: jamie-nagle
|| WEB: http://spot.colorado.edu/~naglej
||------------------------------------------------------------------------------------------
- [Sphenix-run-l] sPHENIX Shift Change Notes (Sunday, June 25, 2023), Jamie Nagle, 06/25/2023
Archive powered by MHonArc 2.6.24.