40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
 40m Log, Page 73 of 339 Not logged in
ID Date Author Type Category Subject
16736   Fri Mar 18 18:39:13 2022 YehonathanSummaryCDSc1auxey1 slow controls acromag chassis installed, powered

{Yehonathan, Anchal}

We connected the c1auxey1 chassie to the different boxes (coil drivers, SAT amp, etc.) using DB9 cables and labeling them in the process. We ran out of 2.5 foot DB9 cables so we used 5 foot as a temporary solution.

The chassie was powered, but a two issues arised:

1. The Acromags didn't turn on.

2. When connecting the green laser shutter BNC cable, the power supply overloaded.

We took the chassie back to the bench. The wire that powers the Acromags was disconnected. We made a new longer wire and made sure it is not connected flimsily.

The issue with the BNC turned out to be a much deeper problem: The GND and EXC wires on the DIN rail connector were switched! Making the shield of the BNC to have high volatage compared to the shield of the green shutter causing current to overflow when the BNC was connected.

We switched back the EXC and GND wires. Not trusting the digital I/O tests that were done before due to this mistake we tested some of the I/Os using a spare coil driver. We tested both the inputs and the outputs and they all seemed to work.

Finally, we also noticed that the 2 RTS DB9s were wrongly female type so we switched them to males. We closed the lead on chassie and installed it back in the rack. We connected the cables and saw that the green shutter BNC cable was no longer shorting the power supply.

16737   Fri Mar 18 19:10:51 2022 AnchalSummaryCDSc1auxey1 slow controls issues

I started the modbusIOC service on c1auxey1 and added PD variance channels for UR and SD as well.  There are unfortunately two issues here:

• The enable monitors are reading NOT of what they should read. The optical isolator circuit might need to be changed.
• ETMY is not damping now. This is strange and was seen in the use to other acromag chassis as well where AS4 and PR2 are unable to damp. This is weird since the acromag chassis are not part of the damping loop, maybe it is a coincidence. Next time we should check if we still have this issue when acromag chassis is disconnected from ETMY.

16740   Mon Mar 21 18:24:07 2022 AnchalSummaryBHDPart IIa of BHR upgrade - Green laser alignment on Yarm

[Anchal, Tega]

We did the following alignment steps on Yarm today:

• We aligned the green beam going into the ETMY chamber to the three irises on the path.
• We aligned ETMY to get counter-propagating prompt reflection from ETMY.
• We were able to see light in the reflection photodiode for the green PDH loop.
• Then we went to ITMY chamber and checked where the beam is coming to. It was coming very low in height.
• We walked the beam on the end to get it near the center of ITMY.
• Then we changed the ETMY alignment again to get back the reflection beam on the reflection photodiode.
• Then we went again to ITMY chamber and changed the ITMY alignment to get counter-propagating reflection from ITMY.

After this, we came back to the control room. One peculiar thing to note is that the C1:LS-Y_REFL_DC_OUT channel is inverted i.e. it is showing negative values for the reflection DC voltage. On this signal, we see a little bit higher-order mode flashing but it is not bright enough to be seen on the face camera of the suspension. We'll continue aligning the cavity using CDS now to get TEM00 mode.

After trying for a bit, we were able to get flash of about 2000 counts which is about 16% of the max value of 12200 counts. We adjusted the ITMY angular position using the IFO_ALIGN screen but used the OPTICAL_ALIGN offset screen to adjust the angular position of ETMY. The pitch and yaw values for ITMY are 1.0360 and -0.260 respectively whereas the pitch and yaw values for ETMY are 5664.0 and -4937.0 respectively.

16741   Mon Mar 21 18:42:06 2022 AnchalSummaryCDSc1auxey1 slow controls issues

Another issue, Green Y Shutter can not be controlled with the EPICS controls right now. This needs to be investigated.

16742   Thu Mar 24 19:20:28 2022 AnchalSummaryBHDPart IIa of BHR upgrade - Green laser alignment on Yarm

[Anchal, Paco]

Uneloged: yesterday, Paco and Ian tried locking the green laser on Yend to the Y-arm. Nothing noteworthy happened, no luck.

• Started with aligning the green injection to the Iris on table (it was misaligned) and getting it on the ITMY center.
• Then we realized that the beam is going through the focusing leans very offceter. This makes the beam warped and deflected inside that needs to be corrected by mirrors.
• So we decided to adjust the lens position first.
• We realized that lens position is hard to adjust along with keeping the beam hiting ITMY.
• So, we decided to remove the lens first and just align the green beam directly with the Iris on the table and the ITMY center. The beam became as big as ITMY when it reached there without the lens in path. We aligned it to fall on the mirror.
• Then we placed the lens back so that the beam goes through the center of the lens.
• Then we aligned ETMY to get the reflection back to the reflection PD.
• But then when we checked the beam at ITMY again, it was severely missing ITMY. The possible reason is that ETMY is a diverging lens for the beam as well and changing its position changed the beam direction in the beam tube.
• We decided to do another iteration of lens positioning with the new ETMY position. So same steps, removed lens, aligned beam with iris and ITMY, placed back the lens, aligned ETMY again to get reflection back on the PD.
• This time the beam was still reaching ITMY. So we were glad that our iterations converged in 2 repititions.
• Then we aligned ITMY to get counter propagating beam.
• At the end of this alignment:
• We see dips in relfection photodiode counts from 12200 to 9500.
• The ETMY oplev is partially out of range (only 1 of the quadrant seeing light) but that could be because we changed the lens position. So Oplev servo is off.
• We confirmed that the PDH servo is properly connected and loop is on. But we see no HOM catching lock for YARM even after us doing about 10 min search with ITMY-ETMY alignments.
• We are leaving things as it is. We'll continue trying to align the cavity tomorrow. Everyone is welcome to try as long as they restore the positions of the optics to a good state at the end.

16744   Fri Mar 25 18:20:28 2022 AnchalSummaryBHDPart IIa of BHR upgrade - Green laser alignment on Yarm

[Anchal, Paco, Shruti]

• Today we found out that the laser controller at the Yend had it's inputs disconnected for the FAST PZT input and the Slow temperature control input. The cables were also not labeled that were lying nearby.
• I tracked the cables and connected the Fast input adn the slow input.
• We then adjusted the temperature slider to go to previously marked laser crystal temperature of 40.1 degrees celsius. But we could not find the the beatnote of Y end IR with teh Main laser IR.
• We scanned the laser crystal temeprature until we could see a beatntoe with the main IR laser and stopped in that region.
• Then we continued looking for flashing and HOM, but no luck.
• It was interesting that when the PDH loop was closed, we saw fluctuations in relfection photodiode DC value, but not so much when the loop was not closed.
• We tried flipping the sign of the loop with no luck and we tried changing the gain of the loop as well, but no luck.
• The behavior of this Yend laser and its controller is still suspicious to us. When the loop is closed, the PZT feedback signal should not cause a change in amplitude of the light so much as we see it.
• Also the fact that when loop is clsoed we do not see signs of flashing in the reflection photodiode is interesting. If anyone has any ideas, that would be good.
16745   Sat Mar 26 13:04:38 2022 PacoSummaryBHDPart IIa of BHR upgrade - Green laser alignment on Yarm

I came for a bit to check on the "1Y0 burning smell" reported by Koji last evening. I agree that there's a toasty smell around the 1Y0 rack, but it is hard to tell where it comes from exactly. I think we can use the FLIR heat camera, but this will have to wait for Monday when someone with an iphone is around.

I also played a bit with the YAUX alignment (which is still poor) but I didn't try anything different nor did I seem to have more success. This is also an outstanding item for Monday, where maybe the next step is to install the GTRY path for a CCD.

16747   Tue Mar 29 15:07:11 2022 TegaSummaryVACOpening of MC and ETM chambers

[Anchal, Chub, Ian, Paco, Tega]

Today, we opened the MC chamber, ETMX chamber and ETMY chamber.

16749   Thu Mar 31 18:58:16 2022 Ian MacMillanSummaryBHDPart IIa of BHR upgrade - IR laser alignment on Xarm

[Ian, Paco]

We continued to try and lock the IR laser to the x-arm. Last time we adjusted TT2 PR2 and PR3 to adjust the beam to hit the center of the ITMX. Today we continued to adjust the same optics to make the beam hit the center of the beam splitter and make sure the beam is going in the direction of the ITMY. Then removed a mirror that wasn't even bolted down. I put it on the front right corner of the hood with all the other optics (right in front of a suspended mirror). With this unknown mirror removed the path was clear and hit the center of ITMX. From there we went and opened the ETMX chamber and using the IR scope we adjusted ITMX to put the beam on the center of the ETMX. We continued adjusting ETMX and ITMX until we had three reflections. We stopped here because we realized we should set up POX. We think this because any adjustment to set up the POX would mess up the work we had done on the x arm alignment.

16750   Fri Apr 1 14:26:19 2022 Ian MacMillanSummaryPEMParticle counter setup near BS Chamber

I mounted the particle counter over the BS chamber attached to the cable tray as seen in Attachment 1. The signal cable runs through an active 30ft cable to the 1x2 rack. the wire is labeled and runs properly through the cable tray. The particle counter is plugged in at the power strip attached near the cable tray. The power cord is also labeled.

I restarted the particle counter service in the c1psl computer in the /etc/systemd/system/ folder using the commands

sudo systemctl restart particleCounter sudo systemctl status particleCounter

I cannged the usb hub assigned in the service file to ttyUSB0 which is what we saw the computer had named it.

Checking the channels from this elog show the same particle count as when testing with the buttons and checking the screen. It seems that the channels had been down but are now restarted.

16754   Sat Apr 2 15:46:13 2022 ranaSummaryPEMParticle counter setup near BS Chamber

nice - please update the particle counter page in the 40m wiki. Its probably years out of date.

 Quote: I mounted the particle counter over the BS chamber attached to the cable tray as seen in Attachment 1. The signal cable runs through an active 30ft cable to the 1x2 rack. the wire is labeled and runs properly through the cable tray. The particle counter is plugged in at the power strip attached near the cable tray. The power cord is also labeled.

16756   Mon Apr 4 17:03:47 2022 AnchalSummaryCDSc1susaux2 slow controls acromag chassis fixed and installed

[Anchal, JC, Ian, Paco]

We have now fixed all issues with the PD mons of c1susaux2 chassis. The slow channels are now reading same values as the fast channels and there is no arbitrary offset. The binary channels are all working now except for LO2 UL which keeps showing ENABLE OFF. This was an issue earlier on LO1 UR and it magically disappeared and now is on LO2. I think the optical isolators aren't very robust. But anyways, now our watchdog system is fully functional for all BHD suspended optics.

16757   Tue Apr 5 18:15:06 2022 AnchalSummaryBHDPart IIa of BHR upgrade - IR laser alignment on Xarm

[Paco, Anchal, Ian, JC]

We attempted the alignment of IR beam into the arm cavities. We used PR2 and PR3 (moved manually as well as using cdsutils) and got the YAW aligned pretty good on both X and Y directions. PIT alignment however turned out to be much harder to align. PR2 PR3 didn't have much range, so we zeroed there offset and tried to use TT1, TT2, MMT1, and MMT2 to align the PIT but it would get clipped before reaching BS table if we were to correct for PIT misalignment happening downstream. We concluded that the issue is that one of the PR2, PR3 mirrors have too much PIT offset in equilibrium position. We have requested Koji to change the output resistors in the coil drivers of PR2 and PR3 so that we can correct for the PIT offset in them directly using the coils and reduce load on upstream optics. We have tweaked TT1, TT2, MMT1, and MMT2 positions today, so we do not have the previous reference anymore.

16758   Wed Apr 6 01:20:48 2022 KojiSummaryBHDPart IIa of BHR upgrade - IR laser alignment on Xarm

PR2/PR3 Output R for fame OSEMS reduced from 1.2K to 1.2K//100Ohm

I put the R=100Ohm for PR3 with the functions of the units mistakenly swapped. This affects imbalanced actuation of PR3 right now as well as too strong SD

PR2 Coil Driver 1 (UL/LL/UR) / S2100616 / PCB S2100520 / R_OUT = (1.2K // 100) for CH1/2/3

PR2 Coil Driver 2 (LR/SD) / S2100617 / PCB S2100519 / R_OUT = (1.2K // 100) for CH3

PR3 Coil Driver 1 (UL/LL/UR) / S2100619 / PCB S2100516 / R_OUT = (1.2K // 100) for CH3 only

PR3 Coil Driver 2 (LR/SD) / S2100618 / PCB S2100518 / R_OUT = (1.2K // 100) for CH1/2/3

----

The output R was reduced from 1.2k to 1.2k//100 = 92 Ohm.

This means that the face coil gains were increased by a factor of 13.

The original gains for PR2 Pos/Pit/Yaw were {0.7, 0.3, 0.2}. To keep the same loop gain, the new gains were supposed to be {0.054, 0.023, 0.015}.
With the new gain, the oscillations were very slowly reduced. Therefore, I increased the gains to have the gain margin of 2. (i.e. increased the gains until I have the oscillation, and then made it half.)
The new values were {0.2, 0.1, 0.05}. The side gain was 20 and unchanged

For PR3 the same operation has been done.

The original gains for PR3 Pos/Pit/Yaw were {1, 0.52, 0.2}. They were supposed to be reduced to  {0.077, 0.04, 0.015}.
The gains were increased to {0.5, 0.1, 0.1}. The side gain was also increased from 1 to 5.

16759   Wed Apr 6 12:03:51 2022 AnchalSummaryBHDPart IIa of BHR upgrade - IR laser alignment on Yarm

[Anchal, Paco]

After Koji reduced the output resistors on PR2/PR3 coil drivers, we got much better actuation range. We aligned TT1 TT2 again to get beam centered on PR2 and PR3. Then we used only PR2 and PR3 to do the input beam alignment to Y arm cavity. Using access in ETMY chamber, we aligned the input beam parallel to cavity axis. Slight changes were required in ETMY alignment offsets to get first roundtrip in same spot on ITMY. remaining alignment is finer and needs to be done with a help of a reflection photodiode and cameras in the control room. Immediate next step is to setup POY path for locking the Yarm with IR.

Side note: Because of the large PIT correction required in PR3, we found that our upper OSEMs were hitting totally bright limit and lower OSEMs were hitting totally dark limit on PR3. This also destablized our damping loops. We pushed the upper OSEMs slighlty and pulled back the lower OSEMs slightly to get the PD signal in half shadow region again. This worked and our damping loops are stable again. However, we think we should repeat free swing test in future to diagonalize the input matrix for new OSEM positions.

16760   Wed Apr 6 22:51:47 2022 KojiSummaryBHDPart IIa of BHR upgrade - IR laser alignment on Xarm

[Yuta Koji]

We took out the two coil driver units for PR3 and the incorrect arrangement of the output Rs were corrected. The boxes were returned to the rack.

In order to recover the alignment of the PR3 mirror, C1:SUS_PR3_SUSPOS_INMON / C1:SUS_PR3_SUSPIT_INMON / C1:SUS_PR3_SUSYAW_INMON were monitored. The previous values for them were {31150 / -31000 / -12800}. By moving the alignment sliders, the PIT and YAW values were adjusted to be {-31100 / -12700}. while this change made the POS value to be 52340.

The original gains for PR3 Pos/Pit/Yaw were {1, 0.52, 0.2}. They were supposed to be reduced to  {0.077, 0.04, 0.015}.
I ended up having the gains to be {0.15, 0.1, 0.05}. The side gain was also increased to 50.

----

Overall, the output R configuration for PR2/PR3 are summarized as follows. I'll update the DCC.

PR2 Coil Driver 1 (UL/LL/UR) / S2100616 / PCB S2100520 / R_OUT = (1.2K // 100) for CH1/2/3

PR2 Coil Driver 2 (LR/SD) / S2100617 / PCB S2100519 / R_OUT = (1.2K // 100) for CH3

PR3 Coil Driver 1 (UL/LL/UR) / S2100619 / PCB S2100516 / R_OUT = (1.2K // 100) for CH1/2/3

PR3 Coil Driver 2 (LR/SD) / S2100618 / PCB S2100518 / R_OUT = (1.2K // 100) for CH3

16762   Thu Apr 7 17:59:51 2022 AnchalSummaryBHDPart IIa of BHR upgrade - IR laser alignment on Yarm

[Anchal, Paco, JC, Tega]

Today we have aligned the Yarm cavity for IR, with verified 1.5 roundtrips. We also placed following optics in the BS table.

• POXM1 (installed earlier, not eloged)
• SRMOL2
• POYM1
• SRMOL1
• POYM2

We also cleared the in-air BS table of all previous optics. JC and Tega setup HeNe laser for Oplevs roughly for now. Tega also transported the POY RFPD from ITMY in-air table to the BS in-air table. We aligned the POY path to the table, but we had to move ITMY after that to get 2nd roundtrip in the arm cavity, which misaligned our POY path again. POY path would need to be modified tomorrow.

16768   Fri Apr 8 17:21:31 2022 Ian MacMillanSummaryBHDPart IIa of BHR upgrade - IR laser alignment on Yarm

[Ian, Paco, Tega]

Paco and I opened the ETMY and ITMY chamber to work on yesterdays efforts to lock the y arm. We temporarily in stalled a camera behind the ETMY to look at the transmission as we adjusted the ETMY and ITMY. We then moved on to setting up the POY. the beam was too large for the apature of the PD so we installed a lens in the beam path to decrease it.

Once that was installed we saw some flashing on the C1:LSC-POYCD_OUT channel. We also could see the flashing on the monitors in the control room. The flashing beam seemed to be in the middle of ITMY but was slightly to the right on the ETMY. From here we tried to walk the beam using PR3 and ETMY to move the beam to the center of the ETMY.

16770   Mon Apr 11 21:13:21 2022 PacoSummaryBHDPart IIa of BHR upgrade - POY11 debugging

[Paco, Koji]

I asked Koji for some advice regarding closing the loop on YARM using POY11. A few things seemed off including

• The YARM transmission; which was peaking at ~ 20 (typically, TRY is normalized so that under nominal input power conditions we see TRY in the range [0, 1])
• The POY11 DCPD level was quite low; we expect a few tens of uW in this low power configuration where no more than 100 mW are going through IMC.

We looked at the POY11 RFPD first. We tried flashing an incandescent lamp in-situ and saw some weak response using an oscilloscope and the DC Out readout. We then used the OPHIR power meter and recorded ~ 1.2 uW of light incident on the POY11 RFPD... Initially, we suspected our beam was not filling the PD sensitive area (~ 2 mm diameter), but a quick estimate using the 200 mm focusing lens currently installed in the ITMY table gave us quite a generous margin of error... so we questioned the OPHIR measurement. We swapped the power meter and this time got ~ 18.4 uW, which is more in line with what we expected (phew).

Moving on, from the POY11 RFPD responsivity, and our ~ 20 uW of incident power, we expected on the order of a 20 mV of DC Output, but weren't really seeing this on the scope, so we decided to test the pins on the power of the RFPD. The DB15 cable not only supplies bipolar 15 VDC but also monitors several other test points such as Tsens, or DCout in the RFPD. We quickly noticed a weird signal on the ENAB testpoint, so we removed POY11 RFPD from the ITMY table and took it to the PD testbench. After redoing the soldering on the breakout board and RF amplifier (ZXX-500LN+), which we tested separately, we saw the expected behavior using a +- 15 VDC power supply... thus verifying that the RFPD and breakout board seemed to work ok. We turned our attention to the upstream DB15 connection, and after quickly checking the newly run cables, we ended up debugging the eurocrate PD interface. After attempting a simple power cycle and failing, we removed this card and looked at the schematic. It would seem that the logic enabling ICs (one or both) failed, thus preventing the card from enabling its outputs correctly.... We bypassed the logic by soldering pins 4,8,14 on U1, U20 and then checked the circuit in-situ, and we saw it worked fine again.

Now none of the status LEDs (which are driven by the logic IC portion) work on this card, but the card itself works fine at least for POY11.

We moved on, and installed the DB15 cables, checking the functionality at every step... Then we looked at the POY11_I_ERR signal and were happy to see nice pdh wavelets. We pushed forward a little bit more to try and lock YARM. First, we went to the Y end and centered the ETMY Oplev so as to register the position where the YARM is flashing... The ITMY Oplev is still not online. Then, we optimized the ETMY damping gains somewhat to try and make it less noisy, and finally, played with the LSC YARM loop gain to attempt locking. This last push was not as successful, but we have an idea of what next steps are needed to reduce the SUS noise, including

• Install ITMY Oplevs, and close loop
• Optimize ITMY damping gains

To be continued....

16771   Mon Apr 11 21:44:14 2022 KojiSummaryBHDPart IIa of BHR upgrade - POY11 debugging

We took out the right most PD interface board D990543 and removed the 74LS04 chips. In fact two out of 4 were already replaced with enabling wires, however it seemed that one of the remaining two got failed.
These remaining two chips were removed and the enabling signals were connected to VCC (+5V). This operation made the status LED light not functional. (We didn't bother to fixed them by connecting them to the GND)

The new schematic diagram was attached here, and the corresponding DCC entry (https://dcc.ligo.org/D1900318-v1) was modified. Attachments #2-3 show the circuit after the changes, and the front view respectively.

16778   Thu Apr 14 10:18:35 2022 PacoSummaryBHD2 in oplev mirrors incompatible with LMR2V

[Paco, JC]

We realized the 2 in oplev mirrors (Thorlabs BB2-E02) for ITMYOL, SRMOL, and BSOL, are 0.47 in thick, while the LMR2V fixed mount is 0.46 in deep, even without taking the retaining ring into account. After a brief exchange with Koji, and Ian, we decided to glue the mirrors onto the mounts using Torr Seal (a vac compatible epoxy). They are curating in the clean room and should be ready to install in about 2 hours.

16779   Thu Apr 14 11:52:57 2022 yehonathanSummaryBHDPart IIa of BHR upgrade - POY11 debugging

{JC, Paco, Yehonathan, Ian}

POY lens was moved to infront of the POY steering mirror to make the POU beam focused on the POY11 RFPD. We measured the DC output with an oscilloscope and optimized it with the steering mirrors. We get ~ 16.5mV.

The new lens position blocked the BS OpLev ingoing beam, so we repositioned the OpLev mirrors to make the beam path not hit the lens.

We went to the control room to observe the PDH signal. We observed a series of PDF osscillation and then the signal died infront of our eyes! There is just noise.

We go and check the +/-15V powering the RFPD and we find that the V- is ~ 14V which is good but the V+ was ~ 2.7V which is not.

We went to the PD interface and measure the POY11 output oltages using a breakout board and got the same result.

The PD interface was taken out for inspection. All the OP27 on channel 3 were replaced with new ICs (without need turns out)...

The PD interface card turned out to be OK. What happened is that one of the Kepcos in the RF rack died because its fan crumbled as seen in Attachment #2 (could this be the source of burning smell?). In response, the rack was drawing from the other Kepco (connected in parallel) way too much current  (4A) and the current limiter dropped its voltage from 15V to 2.7V.

The Kepco pair was removed and replaced with a single Sorensen. The POY PDH signal was restored (see attachment).

16780   Thu Apr 14 18:34:51 2022 PacoSummaryBHDITMY Oplev reinstalled (Re: 2 in oplev mirrors incompatible with LMR2V)

[Paco, Yehonathan]

We installed ITMYOL1 and ITMYOL2 on the ITMY chamber. We aligned the ITMY OpLev beam and closed the loop successfully, we then had a second round of YARM aligment, where we brought the Y peak transmission up from 0.04 counts to 0.09 counts (up by a factor of two). We still couldn't close the YARM loop but we have a better alignment.

16781   Thu Apr 14 18:39:13 2022 PacoSummaryBHDPart IIa of BHR upgrade - POY11 debugging

[Paco]

Q1: What is the product number of the broken Kepco?

A1: Kepco JQE 0-25 V 4A (1/4 rack mountable 100 W linear power supply)

Q2: Do you feel the burning smell on this broken kepco?

A2: Not very clearly. It just smells like generic broken electronic, but the fan was already long gone by the time we detected its problem.

Q3: How much current does the +15 VDC line draw from the Sorensen?

A3: The Sorensen current monitor reads 6.3 Amps

Q4: Is there a linear power supply in the market that can handle this much current with some margin?

A4: Probably... but we would have to look around.

Q5: Do we really need a linear power supply there?

A5: Good question, I guess anything that is not contaminating the RF electronics with HF noise (e.g. switching PS) can work?

Q6: Is the same fan problem happening on other Kepcos?

A6: Other fans are on, but at least one or two have the "ill" sound... It may be worthwile to give them maintenance if we can.

16783   Mon Apr 18 14:52:47 2022 Ian MacMillanSummarySEISeismic Study of Buildings and Caltech Campus

[Ian, JC]

I want to take measurements of seismic noise at different places on Caltech's campus and in different buildings. I will try to use the accelerometer in my phone for this but first I must calibrate it (Against the 40m accelerometers).

I placed my iPhone 11 pro next to the seismometers at the 40m MC as seen in Attachment 1.

The calibration from the instrument was done using cts/rthz * 1V/16384cts * 1/ampgain * g/10V * 10m/s^2/g. The ampgain for all was 100.

Next, I took 100 seconds of data on both the iPhone and the three orthogonal Wilcoxon accelerometers.

The ASD for both of the total acceleration is shown in Attachment 2

The ASD for the individual directions acceleration is shown in Attachment 3

The coherence between the individual directions acceleration and the 40m's individual directions is shown in Attachment 4. For this calculation, the 40m data were downsampled to roughly match the phone's sample rate. This coherence is not very good. It should be higher. Because the phone and 40m sensors were picking up the same data as the phone. Because of this I also looked at the coherence between the individual 40m sensors.

In Attachment 5 I look at the coherence between the individual 40m sensors. This should give me a good idea of whether this is some other issue giving me mow coherence. This plot shows that the coherence between the individual 40m sensors is much better than between the phone and the 40m sensors.

Now I wanted to see what kind of data the iPhone could get from real-world tests. I placed it in a number of locations described below and plotted their ASDs in Attachment 6. The locations are thus:

 Identifier Location Notes QIL QIL Lab in the Sub-basement of west bridge In sub-basement not much activity when taking measurements. WBSH West bridge sub-basement hallway on floor in hallway no activity around WB1H West Bridge 1st floor Hall placed on the floor near pillar near stairs to LIGO offices on the ground floor of west bridge 40m desk on my desk at the 40m placed on the desk while people were walking around and I had my feet on the desk. should be noisy

Notice how at the low end the amplitudes follow the relative amplitudes I would expect. QIL and WBSH are the lowest then WB1H is noisier and 40m desk is the noisiest. However, this is only true up until about 0.5 Hz then they all overlap. Since I would expect the 40m desk should be much noisier at all frequencies I suspect that the phone accelerometer is not suitable for measurements higher than 0.5 Hz.

Possible Problems:

One possible problem with my measurement is that my phone was in a leather case. this may have damped out higher frequencies. Also, my phone was not weighed down or bolted to the floor. this stronger connection would make it better at detecting higher frequencies. I could repeat the experiment with no case and a weight on top of my phone.

What's next:

Since I don't think the phone can give me accurate data above 0.5Hz for quiet environments. It may not be suitable for this task. It would seem that the right instrument is the Wilcoxon 731A but it requires an amplifier that I can't track down.

I included all the data and code in the zip file in attachment 7

16786   Mon Apr 18 17:53:45 2022 PacoSummaryBHDPart IIa of BHR upgrade - POY11 debugging

[Paco, Ian]

We aligned the X-arm IR laser

• First fix pointing on the ITMX by moving the BS (mostly pitch)
• then open etmx chamber and fine tune the pointing using the BS until it is centered on ETMX
• using beam card we quickly see the third reflection back misaligned on pitch so we move ITMX pitch to center it on ETMX
• fine tune the ITMX alignment on ETMX and check higher order reflaction overlaping with input

at this point we checked C1:LSC-TRX_DQ using ndscope and luckly we see a tiny bit of flashing (about 0.04 in normalized high gain PD counts). So we closed ETM chamber and ITM chamber and go to control room to optimize this signal. The optimization was done in the following way:

• First, just reiterate on the last steps from above, by maximizing the peak transmission using ITMX/ETMX pair.
• Then, slide BS alignment, mostly in PIT, and return to ITMX/ETMX pair.
• At some point, turning the BS PIT made a huge improvement, so I turned the control room light off and looked at the camera on the quad monitors.
• Based on the location of the flashes (now brighter) on the ITMX/ETMX, the beam seemed to be off in PIT more than YAW, so we focused on correcting the pointing (moving BS) and then correcting with ITMX/ETMX, until the flashes got centered around ETMX.

Final peak transmission (C1:LSC-TRX_DQ) was ~ 1.3 in normalized high gain PD counts. Power budgeting tells us the peak should be ~ 2.0. The flashing on this arm is much better than YARM, so we will press on by installing POX11 RFPD and attempt locking tomorrow. This also means that YARM can be improved by a combination of alignment and/or SUS damping.

In the end we turned on the ETMX oplev and centered it to "save" our flashing position using this reference.

16798   Thu Apr 21 17:32:35 2022 Ian MacMillanSummarySEISeismic Study of Buildings and Caltech Campus

[Rana, Ian]

We built a power supply for the accelerometer shown in Attachment 1 based on the diagram shown in the Wilcoxon manual and shown in attachment 2. We used a 9V power supply and a capacitor value of 680uF. We did not use a constant current diode.

When hooked up to an oscilloscope we saw vibrations from hitting our hands on the table but we did not see the same amplitude in the negative and positive directions. For example, when I held the accelerometer and moved it down you would see a dip then a peak as the accelerometer accelerated down then accelerated up when I stopped the down word movement. But weirdly when I did the opposite (moved the accelerometer up the same dip then a peak appeared. This is a little concerning because it should be the opposite. it should be a peak then a dip. This in addition to the seemingly decreased sensitivity in one direction make me think that the accelerometer is broken.

I labeled the box with "might be broken" before I returned it to the cryo lab.

16815   Wed Apr 27 16:28:57 2022 AnchalSummaryBHDBHD Upgrade - Retreiving arm cavity alignment

[Anchal, Paco, JC]

We had to open ITMY, ETMY chamber doors to get the cavity aligned again. Once we did that, we regained cavity flashing and were able to align the input injection and cavity alignment to get transmission flashing to 1.0 (C1:LSC-TRY_OUT_DQ). JC later centered both ITMY and ETMY oplevs. The ITMY oplev had become completely out of range.

We also opened ITMX, ETMX chamber doors to get Xarm alignment. Again, it seems that ITMX had moved a lot due to cable post installation.

To be continued

16817   Thu Apr 28 11:53:10 2022 AnchalSummaryBHDPOP_SM4 and POP_SM5 Assembly

### POP_SM4

I tried out this stack today and found some change of plans.

• The attachment in elog 40m/16640 says to use 1/4-20 silver coated non-vented screws for joining BA2V to PLS-T238, however PLS-T238's bottom hole is a blind hole and is not vented. So we actually required <1 in long silver plated vented 1/4-20 cap screw for this purpose. Jordan and I were only able to find the correct length silver plated screw but it is not vented. So we decided to make a venting hole on the post from the side.
• I had to use a 0.14" spacer as washer between PLS-T238 and BA1V. The 1" post shim that Koji got for this purpose had too small a hole in the center to let the 8-32 screw pass (I know, weird). but I think we had 3 spare 0.14" ad we bought 10 when we required 7, so we should be good.
• The attachment in elog 40m/16640 also says to use 8-32 silver coated vented setscrew for joining TR-1.5 to LMR1V mount. I found one vented silver coated set screw nearby in the clean room but it turned out to be too long. Worse, I overtightened the setscrew when trying this connection which damaged the inner threads of one of the LMR1V. So we need to buy one more LMR1V (maybe an additional spare too) for future installation of OMC1R1/OMC2R1.
• Then Jordan and I searched for a smaller silver coated and vented 8-32 setscrew but didn't find any. Jordan also noted that LMR1V is an aluminium mount and we should not use silver coated setscrew with it. Since the TR-1.5 mount is ok to be sacrificed if a cold weld happens, we'll just use an uncoated SS 8-32 setscrew to join TR-1.5 and LMR1V. We could not such vented setscrews, but we have plenty of non-vented once. So Jordan is going to make a venthole in TR1.5 top end as well. LMR1V already has a vent hole on its side.

tl,dr; Jordan is preparing PLS-T238 and TR-1.5 with venting holes and C&B and they would be ready by tomorrow. I have collected all other parts for assembly, still looking for the mirror but I know other lab members know where it is, so no big issue there.

### POP_SM5

The assemly of this mirror is complete. A slight change here as well, we were supposed to use the former POYM1 (Y1-2037-0) mirror for POP_SM5 but I could not find it. It was stored on the right most edge of the table (see 40m/16450), but it is not there anymore. I found another undocumented mirror on the flow bench on the left edge marked (2010 July: Y1-LW1-2037-UV-0-AR) which means this mirror has a wedge of 1 degree and an AR coating as well. We do not need or care about the wedge or AR coating, so we can use this mirror for POP_SM5. Please let me know if someone was saving this mirror for some other purpose.

I'll finish assembly of POP_SM4 tomorrow and install them in ITMX chamber and resurrect POP path.

 Quote: Here is more detail of the POP_SM4 mount assembly. It's a combination of BA2V + PLS-T238 + BA1V + TR-1.5 + LMR1V + Mirror: CM254-750-E03 Between BA1V and PLS-T238, we have to do a washer action to fix the post (8-32) with a 1/4-20 slot. Maybe we can use a 1" post shim from thorlabs/newport. Otherwise, we should be able to fasten the other joints with silver-plated screws we already have/ordered. I think TR-1.5 (and a shim) has not been given to Jordan for C&B. I'll take a look at these.

16826   Tue May 3 14:02:09 2022 AnchalSummaryBHDInstalled POP path in ITMX Chamber

[Anchal, JC]

I installed POP_SM4 and POP_SM5 in the ITMX chamber in the nominal positions. This must have affected the ITMX Oplev because I could see that one of the ITMX oplev beam was going through POP_SM5. It needs to be changed in order to follow the original plan. However, since POP_SM5 is a 1064 line mirror, it is transparent to the opleve beam, so maybe we can just use the ITMX oplev in the current fashion.

## Next steps:

• Get flashing back on the XARM.
• Try to get the correct phase angle in POX11 so that we can lock XARM with IR too.
• Inspect ITMX Oplev. The quadrant sum is low so maybe it needs adjustment in the in-ar table.
• Check if ITMX oplev path needs to be adjusted inside the chamber.
16836   Mon May 9 15:32:14 2022 Ian MacMillanSummaryComputersQuantization Noise Calculation Summary

I made the first pass at a tool to measure the quantization noise of specific filters in the 40m system. The code for which can be found here. It takes the input to the filter bank and the filter coefficients for all of the filters in the filter bank. it then runs the input through all the filters and measures the quantization noise at each instance. It does this by subtracting the 64-bit output from the 32-bit output. Note: the actual system is 64 bit so I need to update it to subtract the 64-bit output from the 128-bit output using the long double format. This means that it must be run on a computer that supports the long double format. which I checked and Rossa does. The code outputs a number of plots that look like the one in Attachment 1. Koji suggested formatting a page for each of the filters that is automatically generated that shows the filter and the results as well as an SNR for the noise source. The code is formatted as a class so that it can be easily added to the IFOtest repo when it is ready.

I tracked down a filter that I thought may have lower thermal noise than the one that is currently used. The specifics of this will be in the DCC document version 2 that I am updating but a diagram of it is found in attachment 2. Preliminary calculations seemed to show that it had lower quantization noise than the current filter realization. I added this filter realization to the c code and ran a simple comparison between all of them. The results in Attachment 3 are not as good as I had hoped. The input was a two-toned sin wave. The low-level broadband signal between 10Hz and 4kHz is the quantization noise. The blue shows the current filter realization and there shows the generic and most basic direct form 2. The orange one is the new filter, which I personally call the Aircraft Biquad because I found it in this paper by the Hughes Aircraft Company. See fig 2 in paper. They call it the "modified canonic form realization" but there are about 20 filters in the paper that also share that name. in the DCC doc I have just given them numbers because it is easier.

Whats next:

1) I need to make the review the qnoisetool code to make it compute the correct 64-bit noise.

a) I also want to add the new filter to the simulation to see how it does

2) Make the output into a summary page the way Koji suggested.

3) complete the updated DCC document. I need to reconcile the differences between the calculation I made and the actual result of the simulation.

16881   Fri May 27 17:46:48 2022 PacoSummaryComputersCDS upgrade visit, downfall and rise of c1lsc models

[Paco, Anchal-remote, Yuta, JC]

Sometime around noon today, right after cds upgrade planning tour, c1lsc FE fell. We though this was ok because anyways c1sus was still up, but somehow the IFO alignment was compromised (this is in fact how we first noticed this loss). Yuta couldn't see REFL on the camera, and neither on the AP table (!!) so somehow either/all of TT1, TT2, PRM got affected by this model stopping. We even tried kicking PRM slightly to try and see if the beam was nearby with no success.

We decided to restart the models. To do this we first ssh into c1lsc, c1ioo and c1sus and stop all models. During this step, c1ioo and c1sus dropped their connection and so we had to physically restart them. We then noticed DC 0x4000 error in c1x04 (c1lsc iop) and after checking the gpstimes were different by 1 second. We then did stopped the model again, and from fb1 restart all daqd_* services and modprobe -r gpstime, modprobe gpstime, restart c1lsc and start the c1x04 model. This fixed the issue, so we finished restarting all FE models and burt restore all the relevant snap files to today 02:19 AM PDT.

This made the IFO recover its nominal alignment, minus the usual drift.

* The OAF model failed to start but we left it like so for now.

16885   Wed Jun 1 12:56:44 2022 PacoSummaryElectronicsSTEMlab 125 handout

[Paco, Deeksha]

Yesterday I handed Deeksha a red pitaya (stemlab 125 - 10) to begin her summer work in the lab. The short term goal (~1 week) is to get it to work as a network analyzer and perhaps characterize its ADC/DAC noise spectra.

16921   Wed Jun 15 17:12:39 2022 CiciSummaryGeneralPreparation for AUX Loop Characterization

[Deeksha, Cici]

We went to the end Xarm station and looked at the green laser setup and electronics. We fiddled with the SR-785 and experimented with low-pass filters, and will be exploring the Python script tomorrow.

16933   Tue Jun 21 14:59:22 2022 CiciSummaryGeneralAUX Transfer Function Loop Exploration

[Deeksha, Cici]

We learned about the auxillary laser control loop, and then went into the lab to identify the components and cables represented by our transfer functions. We connected to the SR785 inside the lab so that we can use it to insert noise next time, and measure the output in various parts of the control loop.

16939   Wed Jun 22 17:04:06 2022 DeekshaSummaryElectronicsCharacterising the AUX control loop

[Cici, Deekha]

Setup loop to measure transfer function of control loop - the aim is to find the open loop gain of the system using the SR785 to inject noise (a swept sine) into the system and taking observations using the scope. We tried to calculate the gain algaebraically, in order to understand what our readings meant and what we can determine from them. Need to figure out how to run python script for the SR785, but took readings from cmd today.

Included - changes/additions made to circuit; frequency reponse obtained (need to check the frequency response as it does not look like the expected result, need to correct the loop itself, or increase the magnitude of the inserted noise as its possible that the noise is currently being suppressed by the system).

To do - circuit needs to be checked + laser lock improved - laser keeps leaving resonance while trying to take readings.

16955   Tue Jun 28 16:26:58 2022 CiciSummaryGeneralVector fitting open loop transfer function/Audio cancellation of optical table enclosure

[Deeksha, Cici]

We attempted to use vectfit to fit our earlier transfer function data, and were generally unsuccessful (see vectfit_firstattempt.png), but are much closer to understanding vectfit than before. Couple of problems to address - finding the right set of initial poles to start with has been very hard, and also however vectfit is plotting the phase data is unwrapping it, which makes it generally unreadable. Still working on how to mess with the vectfit automatically-generated plots. In general, our data is very messy (this is old data of the transfer function from last week), so we took more data today to see if our coherence was the problem (see TFSR785_28-06-2022_161937.pdf). As is visible from the graph, our coherence is terrible, and above 1kHz is almost entirely below 0.5 (or 0.2) on both channels. Figuring out why this is and fixing it is our first priority.

In the process of taking new data, we also found out that the optical table enclosure at the end of the X-arm does a decent job of sound isolation (see enclosure_open.mp4 and enclosure_closed.mp4). The clicking from the shutter is visible on a spectrogram at high frequencies when the enclosure is open, but not when it is closed. We also discovered that the script to toggle the shutter can run indefinitely, which can break the shutter, so we need to fix that problem!

16956   Tue Jun 28 16:59:35 2022 PacoSummaryALSALS beat allan deviation (XARM)

[Paco]

I took ~ 7 minutes of XALS beatnote data with the XAUX laser locked to the XARM cavity, and the XARM locked to PSL to develop an allan deviation estimator. The resulting timeseries for the channel C1:ALS-BEATX_FINE_PHASE_OUT_HZ_DQ (decimated timeseries in Attachment #1) was turned into an allan variance using the "overlapped variable tau estimator":

$\sigma_y^2(n\tau_0, N) = \frac{1}{2n^2\tau_0^2(N - 2n)} \sum_{i=0}^{N-2n-1} (x_{i+2n} - 2x_{i+n} + x_i)^2$

Where $x_k$ represents the k-th data point in the raw timeseries, and $n\tau_0$ are the variable integration intervals under which two point variances are computed (the allan variance is a special case of M-point variance, where M=2). Then, the allan deviation is just the square root of that. Attachment #2 shows the fractional deviation (normalized by the mean beat frequency ~ 3 MHz for this measurement) for 100 integration times spanning the full duration (~ 7 min = 420 s).

The code used for this lives in Git/40m/labutils/measuremens/ALS/

If this estimate is any good, wherever the fractional beatnote deviation reaches a minimum value can be used as a proxy for the longest averaging time that give a statistical increase in SNR. After this timescale, the frequency comparison is usually taken over by "environmental instabilities" which I don't think I can comment further on. In our particular estimate, the 100 second integration gives a fractional deviation of ~ 0.44 %, or absolute deviation of 12.925 kHz.

16959   Tue Jun 28 18:53:16 2022 ranaSummaryALSALS beat allan deviation (XARM)

what's the reasoning behind using df/f_beat instead of df/f_laser ?

 Quote: [Paco] I took ~ 7 minutes of XALS beatnote data with the XAUX laser locked to the XARM cavity, and the XARM locked to PSL to develop an allan deviation estimator.

16962   Wed Jun 29 14:28:06 2022 PacoSummaryALSALS beat allan deviation (XARM)

I guess it didn't make sense since f_beat can be arbitrarily moved, but the beat is taken around the PSL freq ~ 281.73 THz. Attachment #1 shows the overlapping tau allan deviation for the exact same dataset but using the python package allantools, where this time I used the PSL freq as the base frequency. This time, I can see the minimum fractional deviation of 1.33e-13 happening at ~ 20 seconds.

 Quote: what's the reasoning behind using df/f_beat instead of df/f_laser ?

## Another, more familiar interpretation

The allan variance is related to the beatnote spectral density as a mean-square integral (the deviation is then like the rms) with a sinc window.

$\sigma^2_\nu = 2 \int_0^{\infty} S_\nu(f) \lvert \frac{\sin({\pi f \tau})}{\pi f \tau} \lvert ^2 df$

16964   Thu Jun 30 17:19:55 2022 DeekshaSummaryElectronicsMeasured Transfer Functions of the Control Loop, Servo (OLTF); got Vectfit working

[Cici, Deeksha]

We were able to greatly improve the quality of our readings by changing the parameters in the config file (particularly increasing the integration and settle cycles, as well as gradually increasing our excitation signals' amplitude). Attached are the readings taken from the same (the files directly printed by ssh'ing the SR785 (apologies)) - Attachment 1 depicts the graph w/ 30 data points and attachment 2 depicts the graph with 300 data points.

Cici successfully vectfit to the data, as included in Attachment 3. (This is the vectfit of the entire control loop's OLTF). There are two main concerns that need to be looked into, firstly, the manner in which to get the poles and zeros to input into the vectfit program. Similarly, the program works best when the option to enforce stable poles is disabled, once again it may be worth looking into how the program works on a deeper level in order to understand how to proceed.

Just as the servo's individual transfer function was taken, we also came up with a  plan to measure the PZT's individual transfer function (using the MokuLab). The connections for the same have been made and the Moku is at the Xend (disconnected). We may also have to build a highpass filter (similar to the one whose signal enters the PZT) to facilitate taking readings at high frequencies using the Moku.

16966   Thu Jun 30 19:04:55 2022 ranaSummaryPSLPSL HEPA: How what when why

For the PSL HEPA, we wanted it to remain at full speed during the vent, when anyone is working on the PSL, or when there is a lot of dust due to outside conditions or cleaning in the lab.

For NORMAL conditions, the policy is to turn it to 30% for some flow, but low noise.

I think we ought to lock one of the arms on IR PDH and change the HEPA flow settings and plot the arm error signal, and transmitted power for each flow speed to see what's important. Record the times of each setting so that we can make a specgram later

16967   Thu Jun 30 19:24:24 2022 ranaSummaryPEMeffect of nearby CES construction

For the proposed construction in the NW corner of the CES building (near the 40m BS chamber), they did a simulated construction activity on Wednesday from 12-1.

In the attached image, you can see the effect as seen in our seismometers:

this image is calculated by the 40m summary pages codes that Tega has been shepherding back to life, luckily just in time for this test.

Since our local time PDT = UTC - 7 hours, 1900 UTC = noon local. So most of the disturbance happens from 1130-1200, presumably while they are setting up the heavy equipment. If you look in the summary pages for that day, you can also see the IM lost lock. Unclear if this was due to their work or if it was coincidence. Thoughts?

16968   Fri Jul 1 08:50:48 2022 yutaSummaryLSCFPMI with REFL/AS55 trial

[Anchal, Paco, Yuta]

We tried to lock FPMI with REFL55 and AS55 this week, but no success yet.
FPMI locks with POX11, POY11 and ASDC for MICH stably, but handing over to 55's couldn't be done yet.

What we did:
- REFL55: Increased the whitening gain to 24dB. Demodulation phase tuned to minimize MICH signal in I when both arms are locked with POX and POY. REFL55 is noisier than AS55. Demodulation phase and amplitude of the signal seem to drift a lot also. Might need investigation.
- AS55: Demodulation phase tuned to minimize MICH signal in I when both arms are locked with POX and POY. Whitening gain is 24dB.
- Script for demodulation phase tuning lives in https://git.ligo.org/40m/scripts/-/blob/main/RFPD/getPhaseAngle.py
- Locking MICH with REFL55 Q: Kicks BS much and not so stable probably because of noisy REFL55. Offtet also needs to be adjusted to lock MICH to dark fringe.
- BS coil balancing: When MICH is "locked" with REFL55 Q, TRX drops rapidly and AS fringe gets worse, indicating BS coil balancing is not good. We balanced the coils by dithering POS with different coil output matrix gains to minimize oplev PIT and YAW output manually using LOCKINs.
- Locking MICH with ASDC: Works nicely. Offset is set to -0.1 in MICH filter and reduced to -0.03 after lock acquisition.
- ETMX/ETMY actuation balancing: We found that feedback signal to ETMX and ETMY at LSC output is unbalanced when locking with POX and POY. We dithered MC2 at 71 Hz, and checked feedback signals when Xarm/Yarm are locked to find out actuation efficiency imbalance. A gain of 2.9874 is put into C1:LSC-ETMX filter to balance ETMX/ETMY. I think we need to check this factor carefully again.
- TRX and TRY: We normalized TRX and TRY to give 1 when arms are aligned. Before doing this, we also checked the alignment of TRX and TRY DC PDs (also reduced green scattering for TRY). Together with ETMX/ETMY balancing, this helped making filter gains the same for POX and POY lock to be 0.02 (See, also 40m/16888).
- Single arm with REFL55/AS55: We checked that single arm locking with both REFL55_I and AS55_Q works. Single arm locking feeding back to MC2 also worked.
- Handing over to REFL55/AS55: After locking Xarm and Yarm using POX to ETMX and POY to ETMY, MICH is locked with ASDC to BS. Handing over to REFL55_I for CARM using ETMX+ETMY and AS55_Q for DARM using -ETMX+ETMY was not successful. Changing an actuator for CARM to MC2 also didn't work. There might be an unstable point when turning off XARM/YARM filter modules and switching on DARM/CARM filter modules with a ramp time. We also need to re-investigate correct gains and signs for DARM and CARM. (Right now, gains are 0.02 for POX and POY, -0.02 for DARM with AS55_Q (-ETMX+ETMY), -0.02 for CARM with REFL55_I with MC2 are the best we found so far)

Next:
- Measure ETMX and ETMY actuation efficiencies with Xarm/Yarm to balance the output matrix for DARM.
- Measure optical gains of POX11, POY11, AS55 and REFL55 when FPMI is locked with POX/POY/ASDC to find out correct filter gains for them.
- Make sure to measure OLTFs when doing above to correct for loop gains.
- Lock CARM with POY11 to MC2, DARM with POX11 to ETMX. Use input matrix to hand over instead of changing filter modules from XARM/YARM to DARM/CARM.
- Try using ALS to lock FPMI.

16975   Wed Jul 6 19:58:16 2022 PacoSummaryNoiseBudgetXARM noise budget

[Anchal, Paco, Rana]

We locked the XARM using POX11 and made a noise budget for the single arm displacement; see Attachment #1. The noise budget is rough in that we use simple calibrations to get it going; for example we calibrate the measured error point C1:LSC-XARM_IN1_DQ using the single cavity pole and some dc gain to match the UGF point. The control point C1:LSC-XARM_OUT_DQ is calibrated using the actuator gain measured recently by Yuta. We also overlay an estimate of the seismic motion using C1:PEM-SEIS_BS_X_OUT_DQ (calibrated using a few poles to account for stack and pendulum), and finally the laser frequency noise as proxied by the mode cleaner C1:IOO-MC_F_DQ.

A couple of points are taken with this noise budget, apart from it needing a better calibration;

1. Overall the inferred residual displacement noise is high, even for our single arm cavity.
1. By looking at the sim OLTF in foton, it seemed that the single arm cavity loop TF could easily become unstable due to some near-UGF-funkiness likely from FM3 (higher freq boost), so we disabled the automatic triggering on it; the arm stayed locked and we changed the error signal (light blue vs gold (REF1) trace)
2. The arm cavity is potentially seeing too much noise from the IMC in the 1 to 30 Hz band in the form of laser frequency noise.
1. Need IMC noise budget to properly debug.
3. At high frequency (>UGF), there seem to be a bunch of "wiggles" which remain unidentified.
1. We actually tried to investigate a bit into these features, thinking they might have something to do with misalignment, but we couldn't really find significant correlation.

RXA edit:

1. we also noticed some weirdness in the calibration of MC_F v. Arm. We think MC_F should be in units of Hz, and Paco calculated the resulting motion as seen by the arm, but there was a factor of several between these two. Need to calibrate MC_F and check. In principle, MC_F will show up directly in ALS_BEATX (with the green PDH lock off), and I assume that one is accurately calibrated. Somehow we should get MC_F, XARM, and ALS_BEAT to all agree. JC is working on calibrating the Mini-Circuits frequency counter, so once that is done we will be in good shape.
2. we may need to turn on some MC_L feedback for the IMC, so that the MC length follows the NPRO frequency below ~20 Hz.
3. Need to estimate where the IMC WFS noise is in all of this. Does it limit the MC length stability in any frequency band? How do we determine this?
4. Also, we want to redo this noise budget today, whilst using AS55 instead of POX. Please measure the Schnupp asymmetry by checking the optimum demod phase in AS55 for locking Xarm v Yarm.
16976   Wed Jul 6 22:40:03 2022 TegaSummaryCDSUse osem variance to turn off SUS damping instead of coil outputs

I updated the database files for the 7 BHD optics to separate the OSEM variance trigger and the LATCH_OFF trigger operations so that an OSEM variance value exceeding the max of say 200 cnts turns off the damping loop whereas pressing the LATCH_OFF button cuts power to the coil. I restarted the modbusIOC service on c1susaux2 and checked that the new functionality is behaving as expected. So far so good.

TODO

Figure out the next layer of watchdogging needed for the BHD optics.

 Quote: [Anchal, JC, Ian, Paco] We have now fixed all issues with the PD mons of c1susaux2 chassis. The slow channels are now reading same values as the fast channels and there is no arbitrary offset. The binary channels are all working now except for LO2 UL which keeps showing ENABLE OFF. This was an issue earlier on LO1 UR and it magically disappeared and now is on LO2. I think the optical isolators aren't very robust. But anyways, now our watchdog system is fully functional for all BHD suspended optics.

16979   Thu Jul 7 21:25:48 2022 TegaSummaryCDSUse osem variance to turn off SUS damping instead of coil outputs

[Anchal, Tega]

Implemented ramp down of coil bias voltage when the BHD optics watchdog is tripped. Also added a watchdog reset button to the SUS medm screen that turns on damping and ramps up the coil PIT/YAW bias voltages to their nominal values. I believe this concludes the watchdog work.

 Quote: TODO Figure out the next layer of watchdogging needed for the BHD optics.

16982   Fri Jul 8 23:10:04 2022 KojiSummaryGeneralJuly 9th, 2022 Power Outage Prep

The 40m team worked on the power outage preparation. The detailed is summarized on this wiki page. We will still be able to access the wiki page during the power outage as it is hosted some where in Downs.

https://wiki-40m.ligo.caltech.edu/Complete_power_shutdown_2022_07

16983   Mon Jul 11 11:16:45 2022 JCSummaryElectronicsStartup after Shutdown

[Paco, Yehonathan, JC]

We began starting up all the electronics this morning beginning in the Y-end. After following the steps on the Complete_Power_Shutdown_Procedures on the 40m wiki, we only came across 2 issues.

1. The Green beam at the Y-End : Turn on the controller and the indicator light began flashing. After waiting until the blinking light becomes constant, turn on the beam.
2. C1lsc "could not find operating system"-unable to SSH from Rossa : We found an Elog of how to restart Chiara and this worked. We proceeded by adding this to the procedures of startup.
16988   Mon Jul 11 19:29:23 2022 PacoSummaryGeneralFinalizing recovery -- timing issues, cds, MC1

[Yuta, Koji, Paco]

## Restarting CDS

We were having some trouble restarting all the models on the FEs. The error was the famous 0x4000 DC error, which has to do with time de-synchronization between fb1 and a given FE. We tried a combination of things haphazardly, such as reloading the gpstime process using

controls@fb1:~ 0$sudo systemctl stop daqd_* controls@fb1 :~ 0$ sudo modprobe -r gpstime
controls@fb1:~ 0$sudo modprobe gpstime controls@fb1:~ 0$ sudo systemctl start daqd_*
controls@fb1:~ 0$sudo systemctl restart open-mx.service without much success, even when doing this again after hard rebooting FE + IO chassis combinations around the lab. Koji prompted us to check the local times as reported by the gpstime module, and comparing it to network reported times we saw the expected offset of ~ 3.5 s. On a given FE ("c1***") and fb1 separately, we ran: controls@c1***:~ 0$ timedatectl
Local time: Mon 2022-07-11 16:22:39 PDT
Universal time: Tue 2022-07-11 23:22:39 UTC
Time zone: America/Los_Angeles (PDT, -0700)
NTP enabled: yes
NTP synchronized: no
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2022-03-13 01:59:59 PST
Sun 2022-03-13 03:00:00 PDT
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2022-11-06 01:59:59 PDT
Sun 2022-11-06 01:00:00 PST
controls@fb1:~ 0$ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== 192.168.123.255 .BCST. 16 u - 64 0 0.000 0.000 0.000 which meant a couple of things: 1. fb1 was serving its time (broadcast to local (martian) network) 2. fb1 was not getting its time from the internet 3. c1*** was not synchronized even though fb1 was serving the time By looking at previous elogs with similar issues, we tried two things; 1. First, from the FEs, run sudo systemctl restart systemd-timesyncd to get the FE in sync; this didn't immediately solve anything. 2. Then, from fb1, we tried pinging google.com and failed! The fb1 was not connected to the internet!!! We tried rebooting fb1 to see if it connected, but eventually what solved this was restarting the bind9 service on chiara! Now we could ping google, and saw this output controls@fb1:~ 0$ ntpq -p
remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+tor.viarouge.ne 85.199.214.102   2 u  244 1024  377  144.478    0.761   0.566
*ntp.exact-time. .GPS.            1 u   93 1024  377  174.450   -1.741   0.613
time.nullrouten .STEP.          16 u    - 1024    0    0.000    0.000   0.000
+ntp.as43588.net 129.6.15.28      2 u  39m 1024  314  189.152    4.244   0.733
192.168.123.255 .BCST.          16 u    -   64    0    0.000    0.000   0.000

meaning fb1 was getting its time served. Going back to the FEs, we still couldn't see the ntp synchronized flag up, but it just took time after a few minutes we saw the FEs in sync! This also meant that we could finally restart all FE models, which we successfully did following the script described in the wiki. Then we had to reload the modbusIOC service in all the slow machines (sometimes this required us to call sudo systemctl daemon-reload) and performed burt restore to a last Friday's snap file collection.

## IMC realign and MC1 glitch?

With Koji's help PMC locked, and then Yuta and Paco manually increased the input power to the IFO by rotating the waveplate picomotor to 37.0 deg. After this, we noticed that the MC REFL spot was not hitting the camera, so maybe MC1 was misaligned. Paco checked the AP table and saw the spot horizontally misaligned on the camera, which gave us the initial YAW correction on MC1. After some IMC recovery, we saw only MC1 got spontaneously kicked along both PIT and YAW, making our alignment futile. Though not hard to recover, we wondered why this happened.

We went into the 1X4 rack and pushed MC1 suspension cables in to disregard loose connections, but as we came back into the control room we again saw it being kicked randomly! We even turned damping off for a little while and this random kicking didn't stop. There was no significant seismic motion at the time so it is still unclear of what is happening.

ELOG V3.1.3-