Jennie W, Sheila
Now we have our camera servo offsets that we found on the 17th tuned in we ran the A2L script again. The code is
userapps/isc/h1/scripts/run_all_a2l.sh
I saved these values in lscparams.py in userapps/isc/h1/guardian/ and accepted the sdfs in OBSERVE.snap.
Sheila, Jennie W
While Sheila runs a Bruco I checked the coherence from LSC - SRCL, PRCL, MICH, and ASC-MICH, DHARD and CHARD to DARM.
The first image is from our lock last night, the second is the same set of measurements from Monday night when we had a range of 156 MPc (left cursor).
Comparing the two it looks like PRCL coherence is slightly worse since Monday, CHARD looks about the same, DHARD is slightly worse in pitch but better in yaw, ASC-MICH is about the same, PRCL is a bit worse, SRCL is about the same and LSC-MICH is a bit worse.
Thu Apr 25 10:10:20 2024 INFO: Fill completed in 10min 16secs
Jordan confirmed a good fill curbside.
We've gone out of Observing at 1600UTC to start the 3 hour planned commissioning time in coordination with LLO and Virgo.
TITLE: 04/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 132Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY: Locked and Observing for 2 hours. Looks like Ryan C had some SQZ issues overnight. I imagine that we will be doing more investigations into the alignment shift today.
H1 called for assistance as the SQZer lost lock and has been struggling to relock, its been stuck waiting for the TTFSS to lock, it says "Check crystal frequency, can try 45MHz" which is a notification I haven't seen before and I can't find any reference in the WIKI. I'm calling out for SQZ help
I got ahold of Jenne, who suggested following alog 70050 which I did not notice that DIAG_MAIN was also complaining about. Doing this which is reseting the ISS did not help this TTFSS issue. Also at Jennes suggestion I'm going to try and get us into observing without SQZing
Back into observing with NO_SQUEEZING at 11:09 UTC, I followed the WIKI. I forgot that I also had to edit the IFO node to add to the exclude list to get us back into observing ( we should add this to said WIKI page). I reverted the attached SDF diffs
The usual trick of manually moving the crystal frequency to find the beatnote (suggested by the error message Ryan reports above) doesn't work in this case. The attached screenshot shows that at about 3 am the power on the FSS PD nearly doubled, but the fiber power, polarization, and power out of the squeezer laser didn't change. We lost the beatnote at that time (BEATnote strength drops to -40dBm. Moving the laser frequency around doesn't change this.
Note that I thought I could move the laser frequency while we were in observing without squeezing, because the crystal frequency is not monitored in SDF. However changing this changes other things which are monitored, and did temporarily knock us out observing. Some automation brought us back to observing quickly enought that I didn't notice the first time and so did this twice.
Vicky, Sheila, Camilla. Went SQZ_MANAGER to DOWN which cleared any wrong sdfs that had been reverted. The H1:SQZ-FIBR_SERVO_DEMOD_RFMON should not be this low (-40dB), even in old TTFSS issues (75337). We tried touching everything on the TFFSS screen to no avail. We tried changing polarization into "to beatnote" fiber. Turning down this power dropped the H1:SQZ-FIBR_PD_DC_POWER form 0.4 to 0.3. Rather than halving it. Going out to check powers on SQZT0.
On SQZT0 Sheila and I found that even with the PSL fiber unplugged and SQZ beam blocked, H1:SQZ-FIBR_PD_DC_POWER reported power.
Fil replaced the D2300329 Fiber Beat Note Box with our spare. This solved our TTFSS issues. It appears something in the power supply for the box had failed. Details in 77418.
TITLE: 04/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 134Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
LOG:
Rode out a 5.5 Mag Earthquake from New Zealand.
Violins look great!
H1 Is still locked and Observing.
I put in the Lock Aqusition survey in here https://docs.google.com/forms/d/e/1FAIpQLSf_RhE5fjtL9cNhyY6dXtBunM4tonBBwgikZwr1Hg0CBkGn2A/viewform because I could not find the link to the new Lock Aqusition Survey.
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:53 | SQZ | Terry, Kar Meng | OptLab | local | SHG lab work | 19:31 |
| 19:31 | PEM | Robert | CER | n | In and out to hunt for noise sources | 23:16 |
| 20:31 | SQZ | Terry, Kar Meng | Opt Lab | local | SHG lab work 2 | 23:36 |
| 23:56 | PEM | Robert | LVEA | N | Turning off the Lights in the LVEA | 00:56 |
| 01:05 | PEM | Robert | CER | N | Checking PEM system | 01:30 |
| 01:07 | SUN | Pat | Mid Y | No | Walking to mid Y | 01:56 |
| 07:06 | PCAL | Tony | PCAL Lab | Yes | Putting USB drive back. | 07:16 |
The link in Tony's log is the old link. Please use the link found on the operator wiki.
TITLE: 04/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 12mph Gusts, 10mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
After manual Initial_Alignment
We tried to get locked but there were issuses getting DRMI 1F and then PRMI.
I then touched the Beam Splitter and SRM a little bit to try and get PRMI locked with no luck.
I then took IFO to Check mitch fringes. Where it struggled some more to get past PRMI.
I then Took the IFO to Initial Alignment.
After Initial_Alignment H1 was able to get past DRMI locking and got to Nominal_Low_Noise.
Nominal_Low_Noise @ 1:31 UTC
SQZrs were touching up SQZ alignment and to get the SQZ system locked. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=77400
OBserving at 2:32 UTC
Tony, Nutsinee, Vicky
We re-aligned SQZ to the current IFO AS port alignment, got from basically no sqz at all, to ~4.5dB at the end.
Screenshot. First I aligned ZM4 P/Y by ~hundreds counts to see a sqz signal again in transmission of OMC, then manually walked a bit with ZM6. Then I engaged AS42 ASC (zm5/6), which helped a bit to bring the alignment closer, but leaving ASC on for too long caused alignment to run away (so I cleared history on it and started over). I ran AS42 briefly a couple times until improvement to RF3 signal stopped, then offloaded, then some manual walks, then again. Could not use SCAN_ALIGNMENT (zm4/6) - it's range is way too big right now that LO loses lock, so we need to back off the scan range. Manually adjusted SQZ angle to maximize yellow 350 Hz / blue 1.7 kHz blrms.
Overall biggest slider moves were in YAW: ZM4_Y +600, ZM6_Y +270, secondarily ZM4_P +70.
OMC_RF3_RFMON went from around -22 (noise floor around -25), to -10 at squeezing (ofc more with antisqz). SQZ went from basically totally misaligned to almost -4.5dB, with this series of manual walks and ASC attempts. On net, probably still broadly reducing noise with sqz vs. adding noise, so we decided to call it and accept SDFs on the ZMs, so Tony could go to observe.
Edit to add: Alignment and sqz angle are probably not that optimized still. Something interesting - when I first aligned and got something, squeezing needed an RF6 demod phase below 100 deg. When aligning more and with ASC help, the sqz angle moved back up to ~177 deg (where it is left now). Before, we had been operating at around 190-200 deg. Can add those trends here tomorrow. I'm a bit surprised how big much the sqz angle changed with alignment. Unsure if it's maybe a clue in tracking down why the sqz angle is drifting so much recently (for example if alignments, either sqz or ifo, are drifting and those drifts can be compensated in part by changing the sqz angle).
I have accepted the following SDF Diffs to get into observing.
I am waiting for the SQZs to make some quick changes to get the SQZ alignment optimal for Observing.
PCAL EX OSC sum SDF Change. I Thought this switch has to be on.
I took some transfer functions of OFI this afternoon, the references from the template were fairly old (2021), I trended the OSEM basis, and output filters gain as well at the suggestion of Jeff for the reference and things have changed. The basis matrix has different values and the gains signs have been flipped, so that may be why the magnitudes are different. The TFs don't show anything obviously wrong.
The templates are located at: /ligo/svncommon/SusSVN/sus/trunk/OFIS/H1/OFI/SAGM1/Data/
TITLE: 04/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Since my mid shift report (alog77381), we have been able to move SR3 and SR2 to get to a good alignment (Jenne's alog77388), and check that the squeezer also has alignment issues (alog77389), leading us to think that the OFI or surrounding baffles might be the cause of the issues (alog77392). Tony is now finishing up with an alignment with the large SR3 SR2 moves to see if we can lock like that for the night, then we will continue to understand what has changed with the OFI tomorrow.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:47 | FAC | Kim | MX | n | Tech clean | 17:52 |
| 16:53 | SQZ | Terry, Kar Meng | OptLab | local | SHG lab work | 19:31 |
| 16:58 | FAC | Bubba | MX | n | Measurements | 18:58 |
| 19:31 | PEM | Robert | CER | n | In and out to hunt for noise sources | 23:16 |
| 20:31 | SQZ | Terry, Kar Meng | Opt Lab | local | SHG lab work 2 | 00:31 |
We've asked Tony to try locking the IFO with SR3 and SR2 in these very different positions. With these optic positions, we don't want the AS_C offsets in place that we used to get locked yesterday. So, I have now accepted in safe.snap for the ASC model that the AS_C offsets are off (but I've left the numerical values).
If we're unable to lock, then the plan is to ask Tony to revert SR2 and SR3 and turn back on those offsets. Since the offset switches are part of SDF revert, to turn them on the plan should be to go Sitemap -> ASC -> Overview -> AS_C (bottom left) -> Turn on the offsets and save the diff in SDF.
First attachment is my saving the safe.snap file with the offsets off. Second attachment is where the offset buttons are.
We've gotten as far as PRMI locked (with arms held off resonance with ALS, as usual), and at some point as soon as PRMI ASC comes on MICH Yaw gets a 2.2 Hz wiggle.
EDIT to add that a thing to try could be to turn off the ASC during PRMI (set lines 737 and 738 of ISC_DRMI.py to False). If we have similar problems in DRMI ASC, also set lines 1026-1031 to False. Save, then reload ISC_DRMI guardian.
EDIT EDIT: I just set line 737 to False. It may be beneficial to tune up the alignment by hand.
EDIT EDIT EDIT: We're still getting wobbles, even though the guardian had turned off the MICH ASC, and I had by-hand turned off the PRC1 ASC.
EDIT EDIT EDIT EDIT : I also set PRC1 to False on line 738 and loaded. I have to go now though, so good luck Tony!
We had an almost 30 hour lock, but probably we want PRMI ASC to work again now that we're relocking. RyanS and I have just set lines 737 and 738 back to True to enable PRMI ASC.
Sheila, Jennie W
Sheila noticed our range was really high in the lock at 14:51 UTC on the 17th April.
All camera offsets are the same from the good range time (16:19:53 UTC) on the 17th (left cursor) compared to a lock from last night at 2024/04/24 13:20:30 UTC (right cursor).
The offsets for these currently (second cursor) are not in lsc_params and since we had better build-ups on the 17th (first cursor), we should fix these offsets and see if we can optimise A2L gains again in the next commissioning window after the IFO range is recovered.
The best build-ups were immediately after this good time when we changed the PIT2 and YAW3 but this made the range worse.
We looked at this again today and realised the camera offsets had been set back to their former values from before our changes to PIT2 and YAW3 on April 17th when the cameras servo guardian went through state 405 (TURN ON CAMERA FIXED OFFSETS). Then we realised we may have forgotten to reload the camer servo guradian when we made these changes so we took reloaded it then took it to DITHER ON state, then to CAMERA SERVO ON and now we have CAM PIT2 OFFSET = -173 and CAM YAW3 OFFSET = -349.5 as is set in lsc_params.
FIXED ISSUE
