Aggregator

Log Number: 4364461Logbook(s): 

• ELOG

Body: 

Proper protocol is being followed. Approved by Crew Chief. Good to start immediately.

Log Number: 4364460Logbook(s): 

• ELOG

Entry Makers: nserenoBody: 

Took open/closed loop data using bpms in the FFB loop for hall A. The two plots are for bpms "N1" and "N6" or more formally named 1C07 and 1C16. One thing we are unsure of is the sampling rate of the time domain data. We think it is around 4 kHz since this puts a line that gets nicely suppressed by the feedback system at about 65 Hz. See attached plots for the PSD and rms motion up to 100 Hz open/closed loop.

Log Number: 4364459Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: System UN-Masking for: BeamLossMonitor
User: alexs
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: 4364458Logbook(s): 

• CLOG
• ELOG

Entry Makers: creelBody: 

Just to add clarification for everyone.

Starting and stopping equipment, such as warm compressors, is a completely normal process that occurs behind the scenes as part of our ongoing responsibility to maintain and operate the cryogenic systems.
There is nothing special about this particular iteration and we do this type of operation routinely in the background.
In this case, starting the compressor was necessary to support the LCLS2 fast cooldown tomorrow morning.

I have asked FM to pull the logs from the power monitor for inspection to verify.

Log Number: 4364456Logbook(s): 

• ELOG

Tags: 

• Autolog

Body: System Masking for: BeamLossMonitor
User: alexs
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
ILM8T09<

Log Number: 4364453Logbook(s): 

• ELOG

Tags: 

• ShiftSummary

Body:  CEBAF SHIFT LOG Shift Summary

Start of shift: Beam to A/B, Investigating D Tagger trip

Log Number: 4364452Logbook(s): 

• ELOG

Tags: 

• BeamAccounting

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

Log Number: 4364449Logbook(s): 

• ELOG

Body: 

Task approved by work supervisor.

Log Number: 4364446Logbook(s): 

• BTLOG
• ELOG

Entry Makers: ryanmbBody: 

It appears the data from the FFB system may have some issues.

First, checking the FFT data (caget FB_A:BPM:N1:FFT_X for example), some of the BPMs appear to not update, and others (1C16V for example) sometimes do not have data.

This was confirmed by Nick Sereno in some of the time-domain data as well.

This was originally discovered when running the attached python script to grab FFT data and format it for plotting. An example output file is included as well.

Log Number: 4364443Logbook(s): 

• HBLOG
• ELOG

Entry Makers: bbarkerBody: 

Log Number: 4364440Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.6 Target restore date was The output from the myRestore execution was as follows: Auto timestamp unavailable [iocitfrffcc1]

Log Number: 4364438Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.6 Target restore date was The output from the myRestore execution was as follows: Auto timestamp unavailable [iocitfrffcc2]

Log Number: 4364436Logbook(s): 

• ELOG

Body: LERF=>MAGNETS=>TRIMS=>FL05B09 has been disabled in alarm handler

Not running

Log Number: 4364435Logbook(s): 

• ELOG

Body: LERF=>MAGNETS=>TRIMS=>FL05B14 has been enabled in alarm handler

GTS Running

Log Number: 4364434Logbook(s): 

• ELOG

Body: LERF=>MAGNETS=>TRIMS=>FL05B10 has been enabled in alarm handler

GTS Running

Log Number: 4364433Logbook(s): 

• ELOG

Body: LERF has been enabled in alarm handler

GTS Running

Log Number: 4364431Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.6 Target restore date was The output from the myRestore execution was as follows: Auto timestamp unavailable [iocitfrffcc1]

Log Number: 4364430Logbook(s): 

• LERFLOG
• ELOG

Entry Makers: diggsBody: 

GTS Trim Racks are running in the LERF, so I ask Ops turn on the Alarm Handler for those 2 Trim Racks in the LERF.

Log Number: 4364428Logbook(s): 

• LERFLOG
• CLOG
• ELOG

Entry Makers: johnwBody: 

SC1R flow is set to increase to 200g/s to support the FEL/LCLSII FCD tomorrow (Friday, 4/25) and will remain at 200g/s until the completion of the single module pumpdown scheduled for Monday, 4/28. We expect to complete this flow ramp around 4:45pm today (4/24).

Log Number: 4364426Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.6 Target restore date was The output from the myRestore execution was as follows: Auto timestamp unavailable [iocitfrffcc2]