Mon Jun 10 10:11:12 2024 INFO: Fill completed in 11min 7secs
Travis confirmed a good fill curbside
Naoki, Sheila
To investigate the origin of whistles and rms increase in FC IR signal as reported in 78263 and 78344, we turned off the FC green VCO lock after FC IR transition.
In TRANSITION_IR_LOCKING state of SQZ_FC guardian, the FC CMB servo is disabled after FC IR transition. Since we use the green QPD at FC trans for beam spot control, we also turned off the beam spot control. The SDF is accepted as shown in the attachment.
After this guardian change, FC lost lock after IR transition. I reverted the guardian change and FC lock is fine. The FC CMB input is ON now and it was OFF from 2024/06/10 16:44:06 UTC to 2024/06/11 15:07:58 UTC. The beam spot control is still OFF.
After getting the OK for operations ABOVE 10W for H1 yesterday, I forgot to post anything looking at pressure sensors during higher power locklosses/operations yesterday/today. So here is a look from the last 24hrs.
Jennie W, Sheila, TJ
This is done to reduce the coupling we get to length from having off-centre spot positions on the mirrors.
The script can be found in userapps/isc/common/scripts/decoup/a2l_min_generic_LHO.py .
See the steps the script runs in the bottom two plots and the reponse of the ADS demodulated signals in the top plots.
I ran ETMX P and Y first by calling the script with
python a2l_min_generic_LHO ETMX BOTH
changed P and Y
H1:SUS-ETMX_L2_DRIVEALIGN_P2L_SPOT_GAIN => 3.22
H1:SUS-ETMX_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 4.99
ETMY
both P and Y changed
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.3
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 0.92
ITMX
both P and Y changed
H1:SUS-ITMX_L2_DRIVEALIGN_P2L_SPOT_GAIN => -0.99
H1:SUS-ITMX_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 2.88
ITMY
H1:SUS-ITMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => -0.36
H1:SUS-ITMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => -2.5
16:35:52 UTC all A2L gains set and script finished.
CHARD_Y coupling was still bad so we reran Y degree of freedom for all test masses.
ETMX
Want to change gain from 4.99 to 4.98, rounded to 2 decimal places. St.Div is 0.925. Change of 0.01
H1:SUS-ETMX_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 4.98
ETMY
Want to change gain from 0.92 to 0.93, rounded to 2 decimal places. St.Div is 0.145. Change of -0.007
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 0.93
ITMY
Want to change gain from -2.5 to -2.5, rounded to 2 decimal places. St.Div is 1.0. Change of -0.001
Gain did not change.
3 A2Ls changed by 17:33:32 UTC.
ITMX
Want to change gain from 2.88 to 2.87, rounded to 2 decimal places. St.Div is 0.496. Change of 0.01
H1:SUS-ITMX_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 2.87
3 A2Ls changed by 17:33:32 UTC.
I don't think these values made it into lscparams' dictionary a2l_gains['FINAL'] (starting around line 451 in lscparams.py), so they were reverted for the next lock, and they were accepted as the previous values in alog 78383.
FAMIS 20701
No major events for this week, but I am noticing that the PMC TRANS/REFL drifting we've been seeing for a couple months now has somewhat settled down. Thinking this might relate to how we've had an unlocked IFO for longer periods of time in recent days, I trended this against IFO range, but I don't notice a strong correlation.
GV20 AIP went red yesterday, about 22:43 utc time. We will take a look at the controller for this unit as soon as posible, failure is unusual, as of right now it appears as if the controller failed, per trend of adjecent gauges the internal pressure does not appear to be affected. No further action is required at this moment.
TITLE: 06/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 128Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 5mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY:
H1's OBSERVING! (after no Observing for several days)
H1 has been locked at high sensitivity for 5.5hrs and observing just under that time. Nuc30's DARM spectra is froze, so I'm trying to open it up again, or see if the nuc needs a reboot. From what I can see, the violins are slowly ringing down from being rung up from the recovery time of the last few days.
Environmentally, all looks good with low winds, and microseism droping. The higher frequency (3-30Hz) seismic seen around the corner station yesterday afternoon/eve was probably from the trucks & Genie for the film crew.
The Control Room is in a filming configuration as lighting and flim equipment is staged.
TITLE: 06/10 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 130Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
ASC DIFFS
LSC-MISCH2
and
SUS-ITMY_R0_OPTICALALIGN TRAMPS & OFFSETS
Please see Screenshot!
Also had to Init LOCKLOSS_SHUTTER GUARDIAN.... before OBSERVING.
Current H1 STATUS is NLN for 16 minutes and OBSERVING.
Oh wow. What a shift! Great job, Tony! And all the remote help from Sheila, Keita, & Jenne!!
TITLE: 06/10 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 15mph Gusts, 11mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.16 μm/s
QUICK SUMMARY:
Reverted to 1402011129 which is just after initial alignment.
lost lock again a number of times trying to get back to LOWNOISE_LENGTH_CONTROL
Started at line 5008 entering lines of code into guardian -i ISC_LOCK shell terminal
Lost lock @ Transition_From_ETMX after entering line 5092 from ISC_LOCK
ezca.get_LIGOFilter('SUS-ETMX_L3_LOCK_L').ramp_gain(0, ramp_time=5, wait=False) #
Many attempts to lock DRMI later and a few Alignment touchups, we arrived at CARM to Analog where there were a number of saturatrions.
I have since reached higher lock states where I waited in LOWNOISE_COIL_DRIVERS, TRANSITION_FROM_ETMX, and LOWNOISE_LENGTH_CONTROL for a few minutes EACH after they finished.
Nuc30, the main DARM Screen is acting a fowl and is not runnign correctly agian. I tried rebooting but it refused to load the XFCE4 panel & windows manager correctly.
I have made it to OMC_WHITENING but I'm greated with the following ISC_LOCK messages:
The Violins are going down the Main culprits are EYM1, EXM8, and as per usual IYM5&6 !O.o!
2024-06-10_08:00:40.526574Z ISC_LOCK [OMC_WHITENING.run] USERMSG 0: EEEEEPP! ADC Counts for the DCPDs are too high. With whitening they would be 536240, larger than the 524288 available counts! Cannot turn on OMC whitening! Stay here and damp violins
After we make it to NLN there will be a large number of SDF changes to accept.
TITLE: 06/09 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 14mph Gusts, 10mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.20 μm/s
QUICK SUMMARY:
Initial_Alignment was run, Locking process started and set to stop at LOWNOISE_FROM_ETMX so the next state can be troubleshot.
TITLE: 06/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Tony
SHIFT SUMMARY:
Tried to be better at noting main items in the alog today, but overall, we have received the OK for high power work from Jenne/Mike. With this, spent most of the day with Keita remotely, Sheila via chat, and then Jenne joined remotely. Have made it past 60W a few times, but have an issue at LOWNOISE LENGTH CONTROL. The last hour or so H1 has had locklosses in early steps around DRMI and earlier, so Tony started an alignment.
The COSMIC film crew has been busy with set-up in the MPR, Roof, and Control Room. (Richard and Mike have been working with them.)
LOG:
Corey, (Jenne, Keita
For last few days, to lock the OMC, one needed to manual adjust SRM pointing to minimize POP90 before Locking the OMC---this was done from the ENGAGE SOFT LOOPS state (steps noted by Sheila and in alog 78331).
To make this step easier in the future, went through the same process, but at the end, we wanted the ASC to take care of this in the future. So,
And we are currently attempting the MAX POWER step on ISC LOCK.....but there is also some ground motion going on by the film crew's trucks and Richard is also going to be using the Genie Lift to help them put some equipment on the roof.
I just put these vals into the guardian (using the usual offset, not the smooth offset) in ISC_LOCK near the end of EngageASCforFullIFO. Tramp and values set around line 3496-3500, offset turned on in 3525-3527. We're going to try them this lock.
Mike & Jenne gave the OK for operations above 10W.
Made it to 25W (after a manual tweak of SRM at ENGAGE SOFT LOOPS to be able to lock the OMC), but had a lockloss at MOVE SPOTS.
Film crew is here and mainly doing set-up in the Multi-Purpose Room of OSB (Richard & Mike are with them).
Keita has been helping me online, Sheila has posted comments in chat, and Jenne said she'd be available remotely now-ish.
Manual SRM Moves at ENGAGE SOFT LOOPS
Attached is the tiny moves made on SRM to lower POP90.
To do this, after ENGAGE SOFT LOOPS was completed, Sheila said to turn off the Inputs to SRC1 pit & yaw and then make SRM adjustments. I had then kept the SRC1 input OFF and moved on (to that lockloss at MOVE SPOTS. (Jenne is saying we might want to turn those SRC1 offsets back ON with an offset).
Corey, Keita (w/ Jenne on cell)
Last night, Jenne had Tony make a few changesto allow us to run 10W lockloss tests WITHOUT the OMC/DC Readout. Here are the changes made to Guardian files, which were SAVEd & LOADed for ISC_LOCK.
Reversion for ISC_LOCK.py:
Reversion For lscprams.py:
This will allow us to lock the OMC (unless I missed other changes from last night).
Sun Jun 09 10:10:28 2024 INFO: Fill completed in 10min 24secs
Running an alignment this morning and noticed that ALS X-ARM was stuck.
TITLE: 06/09 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY:
Ten 10Watt locks tonight with no obvious spikes in pressure .
2024-06-08_22:58:05 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-08_23:53:25 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-09_00:40:40 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-09_01:22:46 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-09_02:42:00 ISC_LOCK POWER_10W -> LOCKLOSS
The above locklosses at 10Watts can be seen at alog 78320
Had to do an initial alignment inbetween the the first and last 5, that struggled to get past SRC, but I lowered the threshholds again.
2024-06-09_05:23:19 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-09_05:58:34 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-09_06:26:14 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-09_06:53:46 ISC_LOCK POWER_10W -> LOCKLOSS
2024-06-09_07:21:12 ISC_LOCK POWER_10W -> LOCKLOSS
On the last one I forgot to return H1:IMC-REFL_SERVO_IN1POL back to positive, and spent some time wondering why the IMC wasn't locking any longer lol.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
21:03 | SAF | HAZARD | LVEA | YES | LVEA is Laser HAZARD | 23:31 |
00:23 | Tour | Mike & IMAX | LVEA Xarm | YES | Giving Film Crew an IMAX tour & drone flying | 4:38 |
01:32 | Fire Watch | Dripta | LVEA Roof & EY | No | Looking for fire or smoke near Rt.240 round about | 02:02 |
We had 10 locklosses from 10W lock yesterday, and we see zero pressure spike. At this point I'd say this HAM6 alignment is safe. We can try locking OMC and going to high power.
The 1st attachment is the summary trends from yesterday, the same thing as Tony posted but just in a single plot. Y-axis scale is the same as the 2nd attachment, which is from Thursday when we got pressure spikes. Note that the first spike was from a 10-W lock loss on Thursday and that was clearly visible in all pirani gauges on the plot.