Aggregator

Log Number: 4406946Logbook(s): 

• ELOG

Entry Makers: dchriBody: 

.

Log Number: 4406943Logbook(s): 

• ELOG

Body: IDDescriptionPeriodCause 15020Title:
2L04 lost PSS waveguide pressure

Summary:
Dropped HV. NL, SL, and INJ dropped to power permit as well.

Log Number: 4406939Logbook(s): 

• ELOG
• RFLOG

Entry Makers: mockBody: 

Dropped the NL and SL to power permit. Contacting RF on call and possibly SSG.

Log Number: 4406935Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 3.0.1 Target restore date was 2025-06-27 14:28:44 The output from the myRestore execution was as follows: iocin04rfhpa system@2025-06-27 14:28 2(2) restored Rf12Hpa0L04@2025-06-27 14:28 103(103) restored Execute: /usr/csite/certified/bin/ced2Epics -ced ced -A -i iocin04rfhpa (success) PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 Procedure return status: Success

Log Number: 4406933Logbook(s): 

• HBLOG
• ELOG

Body: 

The third line presents the FT calorimeter E>6000 MeV trigger rate.
The yellow annotation shows the time of the incident.
The FT calorimeter was slowly recovering after this incident during two days.
Electron and muon triggers behave normally.

Log Number: 4406929Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 3.0.1 Target restore date was 2025-06-27 14:28:44 The output from the myRestore execution was as follows: iocin04rfhpa system@2025-06-27 14:28 2(2) restored Rf12Hpa0L04@2025-06-27 14:28 103(103) restored Execute: /usr/csite/certified/bin/ced2Epics -ced ced -A -i iocin04rfhpa (success) PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 Procedure return status: Success

Log Number: 4406926Logbook(s): 

• ELOG

Body: IDDescriptionPeriodCause 15019Title:
(iocln04rfhpa) trips 0L04 out of FIL

Summary:
Attempting to Power cycle after multiple trips.

Log Number: 4406923Logbook(s): 

• ELOG

Entry Makers: mockBody: 

Software happened to be already in the control room. He reported that he can still ping the ioc however we are frequently losing EPICS controls. Going to try and reboot the ioc locally.

Log Number: 4406922Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 3.0.1 Target restore date was 2025-06-27 14:28:44 The output from the myRestore execution was as follows: iocin04rfhpa system@2025-06-27 14:28 2(2) restored Rf12Hpa0L04@2025-06-27 14:28 103(103) restored Execute: /usr/csite/certified/bin/ced2Epics -ced ced -A -i iocin04rfhpa (success) PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 Procedure return status: Success

Log Number: 4406920Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 3.0.1 Target restore date was 2025-06-27 14:28:44 The output from the myRestore execution was as follows: iocin04rfhpa system@2025-06-27 14:28 2(2) restored Rf12Hpa0L04@2025-06-27 14:28 103(103) restored Execute: /usr/csite/certified/bin/ced2Epics -ced ced -A -i iocin04rfhpa (success) PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 Procedure return status: Success

Log Number: 4406915Logbook(s): 

• ELOG

Entry Makers: mockBody: 

This ioc lost CA comms but zone was still running with no apparent issues. Once the ioc restored connection, the zone dropped out of filaments. We were able to bring back into HV and RF without any issues.

Log Number: 4406914Logbook(s): 

• ELOG
• RFLOG

Entry Makers: dchriBody: 

.

Log Number: 4406910Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 3.0.1 Target restore date was 2025-06-27 14:15:22 The output from the myRestore execution was as follows: iocin04rfhpa system@2025-06-27 14:15 2(2) restored Rf12Hpa0L04@2025-06-27 14:15 103(103) restored Execute: /usr/csite/certified/bin/ced2Epics -ced ced -A -i iocin04rfhpa (success) PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 PVs modified: 0 Procedure return status: Success

Log Number: 4406899Logbook(s): 

• HBLOG
• ELOG

Body: 

Wednesday evening at 19:43:23, there was a sudden increase in rates in multiple detectors when Hall B current was 0. The event lasted approximately 30 seconds.
It appears that it was a beam setup for Hall C,
The BOM rate went up from 0 to 8 kHz. Under normal production current of 325 nA, it is ~20 Hz
The midstream halo went up to 60 Hz
Downstream halo to 14 kHz
These rates were below FSD thresholds.
The FT rate increased to 180 MHz. For production conditions, it is 18 mHz
All our BPMs (2C21, 2C24, and 2H0) did not see any beam.

Log Number: 4406895Logbook(s): 

• ELOG

Entry Makers: samariBody: 

another one, cleared fine

Log Number: 4406892Logbook(s): 

• ELOG
• UITFLOG

Tags: 

• Readme

Body: [figure:1] Always check the Authorization web application for the latest status: JLab Authorization Manager

Log Number: 4406889Logbook(s): 

• ELOG

Body: HALLA=>MAGNETS=>TRIMS=>BS04B10=>MQA1C17=>MQA1C17RESALARM has been disabled in alarm handler

Voltage is past the software set limit, but is not an issue. OPS-PR 4370342

Log Number: 4406881Logbook(s): 

• ELOG
• INCLOG

Entry Makers: samariBody: 

~8 times in the past day, cleared just fine

Log Number: 4406819Logbook(s): 

• ELOG

Entry Makers: samariBody: 

Log Number: 4406817Logbook(s): 

• HALOG
• ELOG

Entry Makers: samariBody: