Aggregator

Log Number: 4491553Logbook(s): 

• HBLOG
• ELOG

Body: 

Comments

Log Number: 4491552Logbook(s): 

• HBLOG
• ELOG

Body: 

Comments

Log Number: 4491551Logbook(s): 

• ELOG
• HBLOG

Entry Makers: pasyukBody: 

X position on 2C21A is very stable, while on 2C24A it oscilates. Could be noisy corrector between them?
Vertical positions track each other but excursions sometimes is above 0.1 mm

Log Number: 4491550Logbook(s): 

• HBLOG
• ELOG

Body: 

Comments

Log Number: 4491548Logbook(s): 

• HBLOG
• ELOG

Body: 

Comments

Log Number: 4491538Logbook(s): 

• HBLOG
• ELOG

Entry Makers: bschaumlBody: 

I'll get their target positions dialed in and if halo counts are high I'll see if I can tidy up orbit.

Log Number: 4491537Logbook(s): 

• ELOG

Entry Makers: eformanBody: 

Cryo has been contacted by post 2.

Log Number: 4491536Logbook(s): 

• DCLOG
• ELOG

Entry Makers: yoonBody: 

took setpoint and cycled

no TC swap

Log Number: 4491534Logbook(s): 

• ELOG

Tags: 

• Autolog
• MCC8am

Body:  */ ATLis Comments Posted 18:00 Friday April 24 through 18:00 Saturday April 25 AES I&C Systems Ion Pak Maintenance Beam Operations 2026

2026-04-24 22:04 - Mathew Almodovar-Mercado

Log Number: 4491533Logbook(s): 

• HCLOG
• ELOG

Entry Makers: bschaumlBody: 

Engaged without any trouble. We are leaving feed forward off for now because we have no reason to expect it will cause any less trouble than before.

Log Number: 4491530Logbook(s): 

• ELOG

Body: IDDescriptionPeriodCause 16796Title:
Hall B tuning

Summary:
Beam acceptable to Hall C, tuning still required for Hall B.

Log Number: 4491528Logbook(s): 

• ELOG

Entry Makers: roblinBody: 

We have CW into Hall C. Clean CW, no IDX activity to speak of. We also have beam to the Hall B tagger dump and it looks relatively close to what we expect.

This means, we can potentially continue tuning Hall B in CW while we deliver to Hall C in an non invasive way.

Log Number: 4491526Logbook(s): 

• ELOG

Body: IDDescriptionPeriodCause 16795Title:
Recovery spill over

Summary:
Continuing recovery back to Halls B and C.Duration:
18 hours 35 minutes

Time Down:
24-Apr-2026 23:00

Time Up:
25-Apr-2

Log Number: 4491525Logbook(s): 

• HCLOG
• ELOG

Entry Makers: yoonBody: 

Log Number: 4491524Logbook(s): 

• HBLOG
• ELOG

Entry Makers: bschaumlBody: 

Beam flew right through the line and lit up all the BPMs to 2C22 though it was a little ugly so I steered up the line. Beam looks good on all viewers and is showing up on tagger dump viewer.

Log Number: 4491523Logbook(s): 

• HCLOG
• ELOG

Entry Makers: yoonBody: 

Log Number: 4491522Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: System UN-Masking for: BeamLossMonitor
User: eforman
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
ILM

Log Number: 4491520Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: System Masking for: BeamLossMonitor
User: eforman
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
ILM8T0

Log Number: 4491519Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: Destination Masking to: HallB,HallC
User: yoon

Log Number: 4491518Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: Destination Masking to: BSY
User: yoon