Recent Log Entries

Fopt default Max Amplitude set too low

Log Number: 3893197Logbook(s): Entry Makers: mockBody: 

The default max amplitude when opening the application is 1. Based on information from optics expert this is too low. The Max amplitude should be something like 3 in order to get nominal kicks on the BPMs.

Fopt failure

Log Number: 3893188Logbook(s): Tags: Body: Fopt 7.6.2 failed with the following diagnostic:
Machine unstable during run, please repeat! [1.25394]GUI's Log PageFopt Progress Log
13:33:57 Starting Fopt
13:33:57 Fetching current and energies
13:33:57 Extracting BPM information from CED
13:33:58 Number of BPMs detected: 285
13:33:58 Determining status of Halls
13:33:58 Suspending Energy Locks
13:33:58 Failed to suspend Energy Locks
13:33:58 Suspending Orbit Locks
13:33:58 Programming the function generator

Fopt

Log Number: 3893167Logbook(s): Tags: Body: Fopt 7.6.2 completed successfully. The runtime settings include a sample count of 15, a minimum current of 4, and an operating regime of Standard with Excitation in 1S Region. The corrector and RF kicks applied were 3.86334 and 3.86334 volts respectively. The max. amplitude setting was 3 millimeters. The files for this run were saved in the directory /cs/opshome/hlapps/optics/diforb/21aug161255. The X and Y stability of the machine during the run was 0.0621127 and 0.0466224 (mm) respectively.

Fopt failure

Log Number: 3893166Logbook(s): Tags: Body: Fopt 7.6.2 failed with the following diagnostic:
Machine unstable during run, please repeat! [0.467694]GUI's Log PageFopt Progress Log
12:52:16 Starting Fopt
12:52:16 Fetching current and energies
12:52:16 Extracting BPM information from CED
12:52:17 Number of BPMs detected: 361
12:52:17 Determining status of Halls
12:52:17 Suspending Energy Locks
12:52:17 Failed to suspend Energy Locks
12:52:17 Suspending Orbit Locks
12:52:17 Programming the function generator

rayTrace Data Collection: MBC3S01V to IDA4R02 - 3S to 4R y plane

Log Number: 3893162Logbook(s): Body: username = dturner, hostname = opsl03, CSUE version = dvl

Data collection parameters:
points_per_turn = 32
lattice_name = /cs/dvlhome/apps/r/rayTrace_12GeV/dvl/fileio/data/2021-08-16_12:27:25/MBC3S01V_IDA4R02
sddsmonitor_interval = 1.0
start_element = MBC3S01V
emit = 1.56389770932549E-10
filter_min = 0
num_turns = 3
condition_dwell = 2
fsd_pv = ISD0I011G
name = ARC3_to ARC4_y
end_pass = 1
launch_momentum = 2832.5352068669
corr2_momentum = 2832.53520686275
corr2_initial_bdl = 6.58133067190647e-05
max_orbit = 1.5

iocsoftRadNDXIN03 restored

Log Number: 3893160Logbook(s): Tags: Body: restorelib 2.2.1 Target restore date was 2021-08-16 12:28:17 The output from the myRestore execution was as follows: iocsoftRadNDXIN03 A360_det@2021-08-16 12:28 10(10) restored A360_ndx@2021-08-16 12:28 5(5) restored Pause: 3 second(s) Execute: /cs/op/iocs/iocsoftRadNDXIN03/initCalibrationConstants.csh IN (success) Old : NDX0L04_HV_BIAS.DRVH 1000 New : NDX0L04_HV_BIAS.DRVH 1000 Old : INX0L04_gCc 1.164e+12 New : INX0L04_gCc 1.164e+12 Old : INX0L04_nCc 9.4431e+09

1L25:6 processed?

Log Number: 3893159Logbook(s): Entry Makers: mmerzBody: 

I was (pleasantly) surprised as well.

"No Response" is not entirely accurate. "Very small" would be better. And when :1 tripped, you can see that the NDX do respond to 25s gradient.

rayTrace Data Collection: MBC3S01H to IDA4R02 - 3S to 4R x plane

Log Number: 3893158Logbook(s): Body: username = dturner, hostname = opsl03, CSUE version = dvl

Data collection parameters:
points_per_turn = 32
lattice_name = /cs/dvlhome/apps/r/rayTrace_12GeV/dvl/fileio/data/2021-08-16_12:13:10/MBC3S01H_IDA4R02
sddsmonitor_interval = 1.0
start_element = MBC3S01H
emit = 1.432687291721364E-10
filter_min = 0
num_turns = 3
condition_dwell = 2
fsd_pv = ISD0I011G
name = ARC3_to ARC4_x
end_pass = 1
launch_momentum = 2832.54403321941
corr2_momentum = 2832.54403321941
corr2_initial_bdl = -688.385925292969
max_orbit = 1.5

Phased 0L04-8

Log Number: 3893157Logbook(s): Entry Makers: mockBody: 

After recovering cavity 8, tried to restore beam. Would not make it past the injector chicane. Began phasing cavity 8. Almost 180 degrees out of phase upon FCC reboot.

COMMENT ON Hall A CAMAC Power Supply Swap

Log Number: 3893155Logbook(s): Body: 

Before we left the hall we noticed that the CAMAC again
turned off and came back on. We decided to just replace the
power supply as well.
After rebooting the ioc we watched the crate for 20 minutes
with no further issues.

Pages