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.

Wed Feb 07 10:09:46 2024 INFO: Fill completed in 9min 42secs

Gerardo confirmed a good fill curbside

TITLE: 02/07 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: Maintenance
    Wind: 2mph Gusts, 0mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.30 μm/s
QUICK SUMMARY: The LVEA is still laser hazard with some more HAM7/6 work planned today.

Preparations:

ASC-AS_C was centered using SRM. It was moving more than I'd have liked but it was OK.

Confirmed that Irises on HAM6 were centered.

The laser beam was on both of OMC QPDs but sadly they were pretty off-centered. Things were swinging more than I'd have liked but anyway I roughly centered the beam on both QPDs using OM1/2/3.

This means that, due to the cable rerouting/retouching we've done when we put the shroud panel on last week (alog 75651), OMC is hanging at a different angle. That's OK as far as DAC of OM1/2/3 won't saturate once we pump down.

This also means that both WFSs are not centered at all. That's OK, we can pico.

OMCR was good:

We visually checked the centering on the OMCR diode using a viewer card. It was OK in that it's not close to the edge, so we left it as is. The distance from the edge of the V-damp to the OMCR is pretty mush the same as Julian's photo from Jan/31 (alog 75653).

OMC trans video beam doesn't come out of the shroud:

I scanned the OMC PZT2 and was able to see that the DCPDs are flashing, but no beam was visible on the steering mirror of the OMC trans video beam.

We removed the +X+Y-side short shroud panel, and immediately I saw the beam, it was faint but obvious using the IR card and the viewer combined. It was already hitting the steering mirror, and the beam was roughly going to the direction of the video viewport.

Using a ruler and the IR viewer card, we found that the beam height was, very roughly, 4" from the OMCS cage to the steering mirror. Maybe it was a tad low.

Rahul placed a ruler on the ISI table to mark the rough beam position close to the +X door, see his picture.

We put on the shroud panel and the beam is gone no matter what. We even did Betsy/TJ/Fil/RichM/Peter/Koji/Calum trick (alog 28944) they did back in 2016 to move the -X-Y-side short panel around more than designed, without success.

It's very hard to find where the beam is at the panel location. Since we know where the beam is at the edge of HAM6 close to video viewport, we can use a laser pointer to back trace the beam path and see if the baffle hole should move to +X or -X direction, but that won't change the fact that we couldn't bring the beam out with the shroud panel.

Fundamental problem is that the exit hole in the shroud panel is too small.

We cannot find OMC trans unused beam at all:

We also tried to see the unused OMC trans beam that comies out into -X-Y direction, but couldn't. Maybe the power of that beam is much smaller than the video beam.

Because of this, and because they did the aforementioned Bests/TJ/Fil/RichM/Peter/Koji/Calum trick for the old OMC, and because there's no position reproducibility whatsoever once that trick is used and the panel removed and reattached, there's no guarantee that the beam will come out once the panel is installed.

If the panel weren't there, it's unimaginable that the beam will miss the V-dump. Again, the problem is that the hole is too small. That was a problem in 2016, and that is the problem now.

How can we move forward:

Could we NOT reinstall the two problem shroud panels in -X-Y and +X+Y side?

Today's activities:
- EX pumpdown status: ~9.3E-8, exactly 1 week from the start - pretty good
- EX RGA bakeout: it is being baked, see details here: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=75750 ; RGA scan next Monday
- The purge air was disconnected from the input beam port, as HAM3 has been already closed. Now it is only at the OMC and HAM7 ports
- The new Agilent leak detector is now set up. It will be tested during the HAM6 RGA leak testing

Continuing from our plumbing escapades (alog75715 ) Jason and I confirmed there were no table leaks overnight and then fired up the freshly refurbished CO2X laser. Using our Thorlabs powermeter we saw 53W coming out, nice. The alignment was pretty far off in yaw though, so we had to do more alignment than last time we swapped the CO2Y laser (alog65393). We eventually got the beam to line up well on the irises and then had to translate the anular mask a small amount to match the main beam.

More details and pictures to come.

TITLE: 02/07 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: LVEA Laser Hazard all day today. Vent work today was in HAM6 and HAM7.
LOG:                                                                                                                                                                                                                                                                                                                                                                                                                                                               

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.