While running the dust monitor check this morning, LVEA6's dust monitor has a warning requesting it to be checked.

TITLE: 02/08 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.28 μm/s
QUICK SUMMARY:

HAM6 & HAM7 work continues as we are still laser HAZARD in the LVEA.

The ITMX cps had started glitching this week, I tried reseating the cards to fix the glitching, but I guess I forgot to reconnect one of the sensors. The St1 h1 sensor is railed, so the watchdogs nominally can't be reset. I've temporarily bypass the st1 cps in the wd (via an epics variable that raises saturation threshold above the adc range), but the bypass will reset, eventually. I'll reconnect the st1 h1 sensor tomorrow morning.

part 1 (alog 75748)

Shroud panel update:

For the OMC Trans video beam, we further abused the shroud panel successfully move it enough such that the beam comes out. However, that made it somehow impossible to mount the panel on the cage using at least three screws.

We debated how we should secure the panel robustly, but in the end concluded that enlarging existing hole (by milling, good job Tyler!) is the way to go. That way we don't have to do crazy things for hardwares, the panels can stay where they are supposed to be. See Betsy's pictures for the milling vs drilling vs whatever-ing. The modified panels will be installed tomorrow.

We already installed a viewport simulator on HAM6.

Grounding problem was fixed:

ASC-AS_C grounding was fixed. We first touched the AS-AS_C cable on ISI table and nothing changed, we jiggled the cable coming from the top of the ISI to stage 0 and nothing changed, then we jiggled the section between stage 0 and the feedthrough and nothing changed.

Just to make sure, Rahul disconnected the DB25 connection on ISI table and the grounding was gone, which was a surprise. In the end, it was the unused QPD cable assy that was laying on top of the ISI table. ASC-AS_C and the unused QPD cable assy share the same DB25 connector. The shield collar on the unused PCB was touching the ISI table, causing problem for ASC-AS_C. We relocated the unused PCB so that it won't touch. See Rahul's pictures.

Today's activities:
- EX pumpdown status: it is at ~8.2E-8
- EX RGA bakeout: now it is ramped up to 150 deg C: this is the set temperature. RGA scans next Monday-Tuesday
- EX-BRS: it is ready for pumpdown. Everything is set, tomorrow the pumpdown starts
- The BSC8 AIP railed this morning: it pumped the BSC8 Annulus volume, while it was also backed with an Aux cart - the gas load is pretty high through an adjacent O-ring from the vented volume, so in the future all GV Annulus volumes will be pumped with aux carts with the AIP powered off, to avoid AIP overload
- The cable tray of west-side BSC8 has been placed back to its original position
- A leak was located on the HAM8 RGA calibrated leak. A pre-vent RGA scan will be done though, just to make sure if there is nothing severely out of the ordinary, and the issue will be handled during the vent

WP 11672

Entry of work done earlier this week

ECR E2200448 1/5/2024 – EX

In support of the installation for centering the BRS by picomotor, a DB9 cable was pulled from ISCTEX (picomotor driver) to the BRS enclosure. Breakout cable D2400020 breakouts the fifth channel from the DB25 picomotor cable.

ECR E2300367 1/5/2024 -1/6/2024 EX/EY

Network and power cables pulled from the SUS-R1/FAC-R1 racks to the Oplever pylon. Part of the installation for remote centering of the Oplevers. Network and power cables terminated. Network cable to be connected to the Beckhoff CU1128 hub.

Continued from previous ALOG75713

Replaced Meggit (Endevco) Accelerometer Power Conditioner with LIGO Accelerometer Power Conditioner. WP11653
S2300076 installed, all signals attached and powered up at 4:03pm PST.

We did have inrush current blow a fuse on the line, we replaced the 10A fast blow with a 3A slow blow fuse and this solved the issue.

The IO chassis did trip when we switched the accelerometer chassis on, I worked with EJ and Jonathan to restore the connection.

To Do:
MX power adapter cable install and signals transferred from Endevco boxes to the LIGO units.

This log goes into more detail from yesterday's work (alog75754) and what Jason and I did today.

After we checked the chiller lines had no leaks without the table in loop, we added the tables in next. The Y table was free of leaks, but the X table had a slow drip from a few od the push to connect fittings on the RF driver (attachment 1). We swapped all of these fittings for new ones and cut the 1/4" diameter tubes ~0.5", with a cutter that we borrowed from PSL, for fresh connections. This worked great and there were no more leaks.

To fire up the laser to wanted to avoid the fried opamps that we've had in the past, so we turned on the CO2X electronics in this order:

1. TCSX HV power supply - CER mezz
2. X & Y RF source - mech room mezz
3. X & Y power supplies - mech room mezz
4. X & Y AA chassis - CER
5. X & Y control box - rack by tables

No fried opamps this way. When we turned the newly refurbished laser on, it output 53W according to our Thorlabs S322C power head placed just after M1. The alignment was far off in yaw, not even hitting POL1. Jason and I first yawed the laser itself within its mounting bolt holes, which didn't move much, then started to align downstream. We eventually got the beam to the irises before the periscope, but had moved a large majority of the optics along the way - M1, ISSPO, PM1, PM2, M4, M5, M6 (table drawing). Using the FLIR One camera we got the beam to hit the irises in a similar way to before the laser swap (before, iris1 now, iris2 now). We then checked on the table FLIR for mask alignment. Here we noticed that the annular mask was a little off horizontally, so we translated the mask to better match the previous position (before, annular now). Once we inject into vacuum we might need to make some more minor changes on table, but this looks good for now.

The last steps today were to recalibrate the thermopile at the laser head and verify that the power meter is still centered on the beam. The power meter need a small translation to center the beam. The gain in the laser head WATTS filter was previously 8.58755 and we eventually ended up at 13.904. Jason used new_gain=old_gain*P_m /P_E , where P_m is power measured with the Thorlabs S322C just after M1 and P_E is the power reported in Epics with the old calibration. We iterated this a few times to make sure it was as close as we could feasibly get.

Next steps are to inject the beam into vacuum and check centering with the HWS. The plan is for this to be done just before commissioning starts in a few weeks.

We left the CO2X laser keyed off and ready for the upcoming laser safe work.

TITLE: 02/08 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: Work continued today on HAM6 and HAM7.
LOG:                                                                                                                                                                                                                                                     

WP 11676
FRS 13570

Issues reported with one of the BRS network cables, see FRS 13570. Cable was re-terminated with new RJ45 connector and new bulkhead (RJ45) installed. Cable now locks in place when connected.

WP 11678

Issues reported with the EX Picomotor Driver. Found chassis breaker in off position and would immediately trip if chassis was switched on. Unit removed and taken to EE lab. Found one of the 8702 Newport picomotor PZT drivers shorting the 24V power line. No spare Newport 8702 PZT drivers available. Spare chassis installed.

Steps taken before powering on spare unit.

1. Field cables tested for shorts; no issues found:
   1. Across pins 1&14, 2&15, 3&16, 4&17, 5&18, 6&19, 7&20, 8&21
   2. All pins to chamber/table ground
2. Unit powered on with no cables connected.
3. Beckhoff controls and readback cables connected and unit powered up.
4. Connected spare picomotors X&Y and tested all channels using the RJ9 front panel jacks. All channels tested fine.
5. Disabled EX Picomotor (MEDM) and reconnected field cabling.

Picomotor Driver S1107566 Removed
Picomotor Driver S1107550 Installed

Dana, Louis

Attached are two scripts that can be used to inquire when a sensing function measurement corresponding to a given report visibly appears in each of the five channels listed at the bottom of this post. The script get_measurement_gps_times.py takes as input the report ID and the channel you are interested in, and it outputs an ndscope command that shows plots for all five channels, including the channel that was requested, for the time span corresponding to the desired measurement. If you would rather look at the data for all reports in one place, this can be found at /ligo/home/dana.jones/Documents/sensing_func_meas_times/measurement_gps_times.csv (I could not attach the file here unfortunately). The channel names are shortened within the csv file for simplicity, and the lower and upper bounds for each channel represent the total time span over which the measurement appears to last.

The report IDs that have already been included in the script stop at October 27th. If you would like to add additional report IDs not already in line 13 of get_measurement_gps_times.py, you must first regenerate the measurement_gps_times.csv file, whose data the py script relies on. To do so, add the desired report IDs to line 93 in output_measurement_gps_times.py (and in line 13 of get_measurement_gps_times.py) and then run the script in a terminal. Note: pydarm is required to run this script. If using a Hanford control room machine you can simply run:

source /ligo/groups/cal/local/bin/activate

python output_measurement_gps_times.py

The output file measurement_gps_times.csv should be generated. Once you have done this, or if you do not wish to add any additional report IDs, simply copy the already generated csv file that can be found at /ligo/home/dana.jones/Documents/sensing_func_meas_times/measurement_gps_times.csv into your home directory and run the script get_measurement_gps_times.py followed by two arguments: the desired report ID and the channel you wish to target (as a number 1 - 5). Here is an example command:

python get_measurement_gps_times.py 20230913T183650Z 2

This should return something like the following:

###################################################################### 
Report ID = 20230913T183650Z, channel name = H1:SUS-ETMX_L2_CAL_EXCMON
Measurement start time = 1378665360 s, end time = 1378666740 s
###################################################################### 
ndscope H1:SUS-ETMX_L3_CAL_EXCMON , H1:CAL-PCALY_SWEPT_SINE_EXCMON . H1:SUS-ETMX_L2_CAL_EXCMON , H1:LSC-DARM1_EXCMON . H1:SUS-ETMX_L1_CAL_EXCMON -t 1378665360 -t 1378666740 --trend min

The line that starts with "ndscope" can be pasted into a terminal window and, when executed from a Hanford control room machine, will pull up an ndscope window showing the desired measurement during the requested time frame for all five channels. Note: the channel numbers correspond to the following channels (also listed inside get_measurement_gps_times.py):

I have been upgrading my hourly cds_report.py code to access the IPMI system and report on sensor warnings and power supply failures. One of the systems I am scanning, h1cdsrfm, has its chassis intrusion sensor triggered (the lid was removed at some point in the past). To clear this warning, at 13:09 I cleared the sensor using the IPMI web interface. This appears to have caused a glitch in the long-range-dolphin IPC channels. We saw IPC errors over EX, EY and CS models (see attachement).

I have DIAG_RESET these transient errors.

The previous timing master which was again running out of range on the voltage to the OCXO, see alogs 68000 and  61988, has been retuned using the mechanical adjustment of the OCXO.

Today's readback voltage is at +3.88V. We will keep it running over the next few months to see, if it eventually settles.

Naoki, Camille, Julian, Rahul

Summary: We measured beam profiles in HAM7 and HAM6 using the SQZ beam, after the PSAMs offloading work from 75677 75709 and the alignment work from 75732. We noticed that there is a lot of astigmatism on the beam in HAM6, but not in the HAM7 location that we were able to reach with the profiler. 

Details:

In HAM6 we measured at three locations marked by the letters a,b,c in the sketch that Julian will attach. The red lines in the sketch show the irises. 

Location 6A is 1.75 inches from the iris, Location 6B is 2 inches from the iris (closer to OM1).  At location 6C we measured the beam in reflection off OM1, 23.25 inches after OM1.  (The fast shutter is further in the -Y direction in chamber than what is shown in the CAD drawing).  We also would like to measure at position 6D, once the second iris is removed. 

We also measured beam profiles on the -X side of the HAM7 table, location 7A is 6.25" in the +X direction (closer to ZM5) from the iris, 7B is 8.25" from the iris in the + X direction, and location 7C is 12" from the iris in the +X direction.  We weren't able to move the profiler further into the chamber without blocking the beam heading towards FC1.

We measured 13.5% widths, with A1 as the vertical axis and A2 as horizontal. 

* strain guage still drifting

Stll left to do:

• Measure distance from HAM6 first iris to OM1. 
• Measure distance from HAM7 iris (on -X side of table) to ZM5.
• take a better photo of the beam position on ZM5.
• try to put beam profile in location of iris near OM1 (location 6D).

Useful distances from Don:

Don Griffith sent us some useful distances in HAM7 which are useful for interpreting these measurements, based on the CAD model that he updated in in March 2022 based on the as built photos of HAM7 (D1900365-v1). 

• B:M4 (last optic on VIP) to ZM4 = 1086.36mm
• ZM4 to ZM5 = 1681.23mm
• ZM5 to Beam Diverter + 1183.54mm
• ZM5 to Edge of Table = 1822.70mm
• ZM5 to ZM6 = 4680.61mm

The previous timing master which was again running out of range on the voltage to the OCXO, see alog 61988, has been retuned using the mechanical adjustment of the OCXO.

Today's readback voltage is at +3.05V. We will keep it running over the next few months to see, if it eventually settles.