Aggregator

Log Number: 4506243Logbook(s): 

• ELOG

Entry Makers: samariBody: 

I got passed down that we couldn't push hall C passed 50 uA because of integrated loss trips. I first adjusted bunching as I suspected given the loss signals that we weren't optimized for higher current. Bringing the prebuncher from 3.95 to 4.05 minimized the MS interception, and subsequent Buncher adjustment from 4 to 4.4 removed most loss on IDXs and in the main machine )fig 1). We still couldn't ramp them up so I checked when integrated loss looked good, and it seems that at 19:50 when the A1 locks were briefly turned on, they were turned off in an inopportune spot (fig 2).

Log Number: 4506240Logbook(s): 

• HBLOG
• PRADLOG
• ELOG

Body: Submitted Items ItemNote [ ] Shift [Owl][Day][Swing]Owl [ ] Date05/29/2026 [ ] Time [ ] ExpertCarlos Ayerbe Gayoso [ ] WorkerBuddhiman Tamang [ ] Beam Current Requested/Delivered (nA)700 nA

Log Number: 4506229Logbook(s): 

• HDLOG
• ELOG

Entry Makers: shrinerBody: 

Log Number: 4506228Logbook(s): 

• HDLOG
• ELOG

Entry Makers: shrinerBody: 

Log Number: 4506223Logbook(s): 

• ELOG
• LERFLOG

Body:  ACCELERATOR OPERATOR SIGN IN FORM OPERATOR:    Shriner
DATE:             05/30/2026
SHIFT:               Owl

The operator has read the following:

• ELOG
• PD Shift Plan
• Radiation Surveys for PSS Segments in Controlled Access
• PSS Log

Log Number: 4506222Logbook(s): 

• ELOG
• LERFLOG

Body:  ACCELERATOR OPERATOR SIGN IN FORM OPERATOR:    Samari
DATE:             05/30/2026
SHIFT:               Owl

The operator has read the following:

• ELOG
• PD Shift Plan
• Radiation Surveys for PSS Segments in Controlled Access
• PSS Log

Log Number: 4506214Logbook(s): 

• ELOG
• RFLOG

Entry Makers: dturnerBody: smartRAT V3-4 on opsrfdaqnl1

To view waveforms from a timestamp:

ssh opsrfdaqnl1 "smartRAT -m DAQ -d /data/fast_daq/<timestamp>"


To view waveforms of the top 25 from this report:

ssh opsrfdaqnl1 "smartRAT_view_daily_top25 2026-05-22-2026-05-29"


Data directory: /cs/prohome/apps/s/smartRAT2/3-4/fileio/pca_data/output_cavityOutDet/calibrated_cavitylevel_centralize_tsfresh_minimal_gmespmes/whole/rcntnp/2026-05-22-2026-05-29/PCA/

Log Number: 4506205Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: saver ran from opsl05

Saved: deir 05-29-26 23:35:15 {A:i B:5 C:3 E:345 A=BS B=CW C=CW D=CW 0R08=50.22 No dumps in.

Log Number: 4506204Logbook(s): 

• ELOG
• LERFLOG

Body: 
THOMAS JEFFERSON NATIONAL ACCELERATOR FACILITY
ACCELERATOR OPERATIONS CREW CHIEF SIGN IN FORM

Date : 05-29-26
Time : 23:26:58
Day : Friday
Shift : Owl

Crew Chief : Deir
Program Deputy: Saitiniyazi
Team : A
Arm : Shriner
Designated SSO: Samari
LERF Operator:
Operators : Samari, Shriner

This stamp certifies that the above Crew Chief has read/reviewed/received the following:

Log Number: 4506200Logbook(s): 

• ELOG

Tags: 

• ShiftSummary

Body:  CEBAF SHIFT LOG Shift Summary

Start of shift: CW to xBCD.

Log Number: 4506199Logbook(s): 

• ELOG

Tags: 

• BeamAccounting

Body:  Accelerator PHYSICS STUDIES RESTORE ACC DOWN OFF (SAM) Planned 8 0 0

Log Number: 4506196Logbook(s): 

• POLOG
• ELOG

Entry Makers: bschaumlBody: 

We are already not in a great spot with BLA, so the lock making it any noisier was intolerable. We have left them off for most of the shift once we observed this.

Log Number: 4506187Logbook(s): 

• DCLOG
• ELOG

Entry Makers: yoonBody: 

took setpoint

No TC swap

Log Number: 4506184Logbook(s): 

• ELOG

Entry Makers: dchriBody: 

Checked AE02 positions with xB & xD. xB was at a good -11.5 & xD was at ~4.2. Changed the ArcA target lock position at AE02 from 4.25 to 4.7. After applying Path Length adjustments and running some locks, everything seems to be in a better place overall. xB & xD at -11.5 & 4.7 respectfully
before after
Fig. 1
Path Length before path adjustments
xC tune beam

Fig.2,3
Path Length before path adjustments
Orbit
xB tune beam

Fig.4,5
Path Length before path adjustments
Orbits
xD tune beam

Fig.6
DogCalc changes
xD tune beam

Fig.7
Path Length.
xB tune beam

Fig.8
Path Length.

Log Number: 4506178Logbook(s): 

• ELOG

Body: IDDescriptionPeriodCause 17064Title:
checking orbits after multiple trips

Summary:
checking orbitsDuration:
23 minutes

Time Down:
29-May-2026 21:04

Time Up:
29-May-2026 21:27

Log Number: 4506177Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: System UN-Masking for: BeamLossMonitor
User: lrichard
Areas: All

BeamLossMonitor Devices:
ILM0I07
ILM0L01A
ILM0L01B
ILM0L02
ILM2D00A
ILM2D00B
ILM0L04A
ILM0L04B
ILM0L05
ILM0L06A
ILM0L08
ILM0R01
ILM4D00
ILM0R03
ILM0R04
ILM0R06
ILM0R08
ILM0R09
ILM1L01
ILM1L02
ILM6R08
ILM3S00
ILM7S00
ILM9S00
ILM5S10
ILM5E03
ILM7S01
ILM9A01
ILM3E02
ILM5A01
ILM1A04
ILM1A06
ILM1A09
ILM5A10
ILM1A16
ILM1A19
ILM3R10
ILM9R07
ILM1R09
ILM2L03
ILM5R10
ILM5R05
ILM2L01
ILM2T09
IL

Log Number: 4506176Logbook(s): 

• ELOG
• BTLOG

Tags: 

• Autolog

Body: dogCalc V0-14 download

hostname: opsl02
CED workspace: OPS
CED login_key: pro

Log Number: 4506173Logbook(s): 

• ELOG

Body: IDDescriptionPeriodCause 17064Title:
checking orbits after multiple trips

Summary:
checking orbitsDuration:
1 minute

Time Down:
29-May-2026 21:04

Time Up:

Log Number: 4506172Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: System Masking for: BeamLossMonitor
User: lrichard
Areas: All

BeamLossMonitor Devices:
ILM0I07
ILM0L01A
ILM0L01B
ILM0L02
ILM2D00A
ILM2D00B
ILM0L04A
ILM0L04B
ILM0L05
ILM0L06A
ILM0L08
ILM0R01
ILM4D00
ILM0R03
ILM0R04
ILM0R06
ILM0R08
ILM0R09
ILM1L01
ILM1L02
ILM6R08
ILM3S00
ILM7S00
ILM9S00
ILM5S10
ILM5E03
ILM7S01
ILM9A01
ILM3E02
ILM5A01
ILM1A04
ILM1A06
ILM1A09
ILM5A10
ILM1A16
ILM1A19
ILM3R10
ILM9R07
ILM1R09
ILM2L03
ILM5R10
ILM5R05
ILM2L01
ILM2T09
ILM8T

Log Number: 4506167Logbook(s): 

• HDLOG
• ELOG

Entry Makers: dchriBody: 

Overall, xD stability has 'improved'

Fig.1
xD current start of shift,
Sigma: 13.94
Mean: 30

Fig.2
xD current mid-shift,
Sigma: 13.08
Mean: 31

Fig.3
Ops PID lock in the injector has it's pros and cons...
PROs: various INX(gamma rates) seem to drop down and Hall B Halo trips become less frequent
CONs: more interception on Injector aperture(s) and Hall D current is a bit more unstable

... however, other tweaks being performed around this time make it tricky to 100% deduce what's causing what