Sheila, Rana, Kiwamu, Alexa, Daniel

We had not been able to lock the PRMI all of today. During the day's usual ISI shaking we noticed that the AS beam had gone nearly of the camera and so spent awhile chasing trends, etc.

After not finding the cause of that, we noticed that the AS45 and REFL45 signals had dropped off to nothing around 3AM local time. As far as we can tell, no one was on site at the time.

Afer some hunting, we found a particularly horrible electronics setup for the 45 MHz modulation amplifier in the H1 CDS electronics room on the same rack as the 9 MHz Marconi generator:

There was an unsecured ZHL-1A amplifier on top of the rack, powered by a DC bench supply (of the lowest quality available), and connected by damaged Banana cables. The banana power cables are intermittent and turn off the amplifier power once in awhile. We could see the power supply current vary to any value between 0 and 400 mA as we brushed the cables - I wouldn't trust this amplifier any more.

Several people disavowed any knowledge of this setup (even after we found https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=11986). It contained a few low quality L-Com cables and several cheap BNC barrels. We must never use BNC connections and these kinds of unreliable adapters in our low noise RF setups. Only N and SMA connections are allowed.

We have relocked the PRMI after removing this setup. The modulation voltage for 45 MHz is now 4x lower. It would be best to make a higher quality RF amplifier setup underneath the PSL table as was done at LLO. We'll be using this weaker modulation for another few days, but we want the higher modulation depth by mid next week, when we get back to the 3f locking.

Here's a 1-minute video of a PRMI sideband lock, from the AS port camera.  Kiwamu, Rana, and Sheila will write more about this later in the evening.

Yesterday by the end of the day the main path through to the pericope had been aligned on the X-arm table.  This morning we started with a projection as described in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=13975.  As part of this we realigned the beam through the mask to optimize the shape on the screen.

Later today we aligned the power meter, and ISS photodiodes.  The QPDs were checked and are stlil aligned.  We calibrated the photodiodes and then started to calibrate the rotation stage for the output power to the CP.  However we found a maximum throughput of only 2.5W.  Clearly  we are losing a lot of power somewhere.

The table has a second IR camera located on the optical table.  Before the adjustment during the projection the beam on this looked quite uniform.  After finding that we were losing power I looked at the image on this camera, which is taken using a 50% splitter mirror from the beam going to the CP.  The image is attached, but appears to show that we are now not well aligned through the mask.  We'll need to redo this alignment, but it is surprising that the image from the projection and the image on the table look so different.  Possibly this is just the lower resolution of the camera used to image the projected beam.

RGA is baking overnight -> The 1.5" gauge pair pump port valve is closed as well as the 10" gate valve -> Leaving PT346B off while unpumped (i.e. while the 10" gate valve and 1.5" valves are closed)

On the BSC-ISIs, things have been running differently at LHO and LLO for quite a while.

I took a look at a random chamber (ITMY) for both sites to see how we can make the best out of both configurations.

LLO ITMY Status:

Stage 1

- X, Y: 45mHz blend, FeedForward from HEPI, Sensor Correction

- Z: 90mHz blend, FeedForward from HEPI, Sensor Correction

- RX, RY: 250 mHz blend

- RZ: 200mHz blend

Stage 2

- X, Y: 250mHz Blend

- Z, RX, RY, RZ: Damping only

LHO ITMY Status:

Stage 1

- X, Y, Z: 45mHz blend

- Z: 90mHz blend

- RX, RY, RZ: 250 mHz blend

Stage 2

- All DOFs: 750mHz Blend

As we can see, the main difference is on Stage 2: most of the DOFs are turned off (damping only) at LLO. On the other hand, they have more features (FeedForward, Sensor Correction) installed on ST1 then at LHO.

By looking at the results, we see pretty similar results in X and Y.  LLO seems to do a little better at 0.5Hz (better blend design, sensor correction). But, by looking at the rotational degrees of freedom, we can see that having a high blend on ST2 at LHO doesn't affect the low frequencies and help a little around 1Hz (we see that also in the optical lever).

In conclusion, turning on the sensor correction at LHO seems to be the next step. At LLO, it seems that turning ON the stage 2 loops with high blend filters wouldn't hurt.

The commissioners have been complaining about too much motion in Yaw on the BS (almost 2microns peak to peak at 10 mHz (!!)).

We know we have some pick up between Z and RZ (see the various SEI logs from the last 6 months), so I switched from a ~100mHz blend in Z to a 750mHz. Relaxing the actuation in Z reduced the pick up seen in RZ.

I was afraid to degrade pitch with this change, but we improved yaw by a factor of ~5 without changing the pitch integrated RMS (it introduced a peak around 1Hz though).

I've tried to implement a 250mHz blend, but no improvement...

Thus, the configuration that seems to satisfy the commissioners is:

- Tbetter: X, Y, RX, RY

-Tcrappy: RZ

- T750: Z

I'll check what is the status of this "pick up" on the other chambers ASAP.

TACQ driver S1100025 was replaced with newly modded (L1200226-v2) S1000356 as SRM M3.

Swapped out Top acquistion coil drivers in PR2, SR2
Old                       New
S1100020                  S1100040
S1100009                  S1100028
S1100032                  S1100012
S1100052                  S1100003

Waiting on tests to finish to replace SRM.

This closes work permit 4852:

Fixed bug in get_last_keep_alive when no keep alive was recorded in the database. Updated exception handling and argument parsing.

Does not affect the database or server.

The H3 ~6hz zero didn't soften as much as on HAM4 but it is smaller.  See attached for the comparison the HAM5 ISI L2L TF with 5hz vs 2hz ugf HEPI Pos Loops.

9:45 am, Aaron to the CS VEA, replacement of coil drivers per WP#4850
10:02 am, Peter K to CS VEA, work inside H2 lser enclosure.<-- Done
10:48 am, Travis to CS VEA, West bay area, work at the test stand.<--- Done
11:55 am, Karen to Y-End station, driving over to drop off bottled water.<---Done
1:03 pm, Alexa and Jeff, control room, software changes to new drivers on WP#4850.
1:26 pm, Travis to CS VEA, West bay area, test stand work.
1:36 pm, Betsy to CS VEA, West bay area, test stand work.
2:30 pm, Patrick from control room, update conlog per WP#4852.<---Done
3:44 pm, Dan to CS VEA, HAM6 area to break and fix some stuff. 
4:00 pm, Andres to CS VEA, West bay area, retrive information.  Door are locked.

Nothing special as these are generic Lvl1 controllers.  They work.  The attached pdf shows all the details of all controllers.

Alastair, Greg, Patrick

Alastair tried to use the TCSX rotation stage to change the power this morning. Nothing on the medm screen seemed to indicate that anything was happening.

When I request a search for home, the 'Actual Cmd Position', 'Actual Velocity' and 'Drive Time (ms)' change on the 'Rotation Stage Readback' medm, but the 'Counter Actual Angle' does not.

A. Sevingy, J. Kissel, A. Staley

Continuing with the installation of modified triple acquisition drivers into all lower stages of Recycling Cavity HSTSs, as per ECR E1400369, Integration Issue 936, and work permit 4850. Aaron will post serial numbers when the final install of SRM is complete, however, anxious to use the new drivers, Alexa and I followed yesterday's procedure (see LHO aLOG 13958, we started at Step 2) to make the necessary software changes to support the new drivers on H1SUSPR2 and H1SUSSR2. The only difference was that, unlike PRM, the "twos" needed BOTH stages of COILOUTF filters modified, since they did not have a prior modified driver installed in M2.

new safe.snaps, filter files, and top-level models have been committed to the userapps repo. As with yesterday's changes, no DAQ restart was required.