Some, maybe all of the CDS WIFI access points (WAP) were left on since the CDS network upgrade on February 21 2024.

The WAPs at EY and MY were on.  At least one WAP in the corner station, either CER or LVEA was on.

Most likely every WAP was on, since they were in the on state on February 21.

Control of the WAPs is as follows:

- An medm screen has an off and on button for each WAP, and for each WAP, an indicator that changes color from red to green when the WAP is on.

- Commands from the MEDM are relayed by an EPICS IOC to a central server named 'wap-control'. 

- The server is connected by network to the WAPs and turns the WAP radios on or off as commanded from the MEDM.

- The server maintains a status record of each WAP which is queried by the IOC and used to update the STATUS indicator on the MEDM.

The failure happened for these reason:

1. One of the network switch ports used by the central server was not configured correctly during the network upgrade.  This severed the control link between the server and the WAPs, and made the MEDM screen useless.

2. When a WAP is disconnected, the central server reports to the IOC the desired state of the WAP radios.  The MEDM screen then incorrectly indicates the WAP is at the desired state, so the MEDM screen appeared to be operating correctly.

The network port is now fixed and the WAP radios are off.

We plan next Tuesday to change the MEDM screen to indicate when a WAP is disconnected and the state of the radios isn't known.

Related post here: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=77860

Ryan Short has written a couple of useful commands for working outside the default conda environment.

'killconda' will drop you out of conda in the current shell.  New shells will still be in the default conda environment.

'noconda ....'  will run a single command outside the conda environment.  When the command is done, the shell will return the to conda environment.

TITLE: 05/16 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Wind
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 34mph Gusts, 28mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY: Currently still trying to recover from the PR moves that happened earlier today, but the wind is also preventing this recovery a bit. Trying to lock PRMI at the moment, but flashes are dismal. I might run a yet another initial alignment soon.

TITLE: 05/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Today was primarily a commissioning day (with 90min of OBSERVING at the start of the shift).  PR3 was moved to a new spot along with some picomotor moves (Sheila/Jenne/Menyo).  Attempting to keep this configuration for the night (see Sheila's alog) to continue commissioning tomorrow to see if this new configuration can improve the overall range for H1 tomorrow---Jenne gave TJ a summary of this state of H1 for tonight.
LOG:

• 1444-1506 Optics Lab cleaning/checks (karen)
• 1459 Received "Hanford Emergency Information" automated phone call for EXCERCISE of a Take Cover/Shelter-In-Place/Simulate for the 200W Area.  We are NOT participating in this exercise; I responded with a receipt of the messsage.  (Received a similar message at 1511 & 1621, which listed LIGO and others which was different from 1st call....but they said it's an EXERCISE and for 200W; Richard said we can disregard and we are not particpating.)
• 1510-1513 Quick peek in LVEA (richard,sheila)
• 1539-1637 wood shop cleaning (karen)
• 1600 COMMISSIONING
• 1615 re-ran launch script for nuc33 again due to dtt crashing overnight.
• 1620 LOCKLOSS
• 1635 police exercises occurring (bubba phoned)
• 1647-1658 EY to check wifi (erik)
• 1652-1800 MY roof inspections (tyler/3-vehicles)
  • 1800- Now MX
• 1927-1931 Wifi tests for MSR (erik)
• 1939 Different wifi checks at MX (erik)
• 2032-2036 Restoring HAM3 black glass (sheila)
• 2115-2117 Happened to see Trash truck approach LSB to access dumpster. 
• 2215 LOCKLOSS----commissioners will keep unique alignment configuration and run an involved Initial Alignment.

Jenne, Sheila, Minhyo, KarMeng

• HAM3 -Y -X viewport black glass guillotine removed 16:04 UTC, quiet time until 16:11 UTC to see how the 48Hz scatter looked before we started.
• new DHARD P boost engaged at 16:13 UTC 16:18 UTC
• Then we started to move PR3 in lock with the move_PR2_spot_position guardian state moving sliders on PR2, IM4 and PRM.  We lost lock after moving about 1 urad PR3 -yaw in full lock. 
• We then looked at doing the move with just the green arms locked, thinking that we might be able to move the HAM3 POP/ALS pico to keep the green beat notes good to track the pointing onto POP.  This didn't work well because we seem to be starting with the beam not well aligned onto the TRX diode, so we fell off that diode quickly.
• We then decided to leave the green arms locked with the ASC engaged at 2W to move the PR2 spot there. This worked well but slowly, Jenne moved PR3 yaw while letting the guardian state PR2_SPOTMOVE move PR2, PRM and IM4.  Roughly every -1 urad of PR3 yaw, Jenne moved PICO_A_MOTOR_8_X by -50 counts to bring the ALS trx,  comm and diff beatnotes, and POP18 and POP90 back.  After ~15 urad, we noticed that we were starting to fall off POPAIR_B, and Jenne moved PR3 pitch to cancel the cross coupling due to the yaw move.  This restored the powers on POPAIR B to what they were before we started.  The attached screenshot shows the powers changing as PR3 pitch and yaw and the pico were adjusted.  The second attached screenshot shows that the arm transmissions increased slightly during this move, although it's hard to say if that's thermal or a result of reducing clipping on PR2.  This moved ASC POP A yaw by 0.4 urad, so if we need to continue several times further than this, as we suspect, we will need to pico POP A.
• We stopped after having move PR3 -36urad in yaw, an hour before the end of the commissioning time.  We've unlocked the IFO to run an initial alignment and see that we can relock.
• THe PRC optics were verry misliagned when we started initial alignment so we ran wfsreliefpast.py 1399917552 to restore them to the location they were when we were locked at 2W and the ASC was on.  This restored the input alignment to the X arm, but also moved the arm optics, so we started over with green arm alignment, the whole alignment went smoothly after this.
• In our first locking attempt we locked DRMI without issue and let the ASC run, which uses the POP A QPD, but we didn't think about how this had shifted because of our PR3 move, so DRMI ASC shifted our vertex alignments quite a bit compared to what initial alignment did.  We restored everything to before the DRMI alignment.
• When PRMI ASC came on we saw osccialtions at around 23Hz in DRMI LSC.  We reduced the MICH gain from 3.2 to 2.8 and didn't have this oscillation.  We were then able to run PRMI ASC and DRMI ASC without the PRC1 (POP QPD) loop.
• This allowed the FULL IFO ASC to engage, although there was a large transient along the way.  Once everything was converged, the POPA QPD was at -0.187 PIT and 0.797 YAW. We powered up without an issue.
• When we got to low noise, a large broadband noise showed up in DARM which is not coherence with LSC, ASC or jitter (screenshot attached).  I put the black glass guillotine back, this didn't help. 
• Ran SCAN_ALIGNMENT for the squeezer, results here: here
• Jenne remeasured the spot position on PR2, we are closer to center in yaw and no vertical move. Minhyo ran CalcSpotPos.py, and says that the PR2 Y2L gain is now -6.75 which means that alpha is -0.32215 (see alog 31402) and the spot position is at -13.595mm. 
• Jenne also did a HAM3 excitation, which does not come close to explaining the extra noise.
• We've been sitting here with the large noise from 20:37 UTC to 21:07 UTC
• We moved another -28 urad on PR3 in full lock while pico'ing for LSC POP.
• In parallel we were looking at why we had poor squeezing, and Anamaria suggested turning off squeezing. The squeezer is responsible for the loarge low frequency noise after the PR3 move. We tried running the alignment script and SQZ angle script again, they ran well and found a local max for alignment, but this seems not to be as good of an alignment as before the PR3 move.  We may need to walk the squeezer beam in full lock to restore the same level of high frequency squeezing that we had before.  I also checked the filter cavity detuning, by changing the detuning we can make this low frequency noise worse.
• We lost lock and have started a manual intial alignment, we had to move IM4 quite a lot, it seems that the PR2 spot move script moves IM sliders too much. 
• After running the green arms alignments Jenne touched the HAM3 pico to increase the ALS beatnotes, a smaller move than the earlier ones.
• We did some trending and resetting according to top mass osems for IM4 + PR2, then initial alignment went smoothly.

The POP QPD is still not used in DRMI ASC.

Terrry,  Kar Meng

The spare SHG in the optics lab is now fully assembled and producing green light. The conversion efficiency looks quite respectable with 29 mW of green at 61 mW of pump (IR) power. I've extended Nutsinees model alog(40199)  down to lower powers and added our data points measured at low power (circled points). We did not go to higher powers as there is some worry about unnecessarily degrading the lifetime of the crystal.

• H1's been down for COMMISSIONING & Sheila/Jenne are working on restoring H1 with a new alignment.
• Winds slowly picking up over the last few hours.
• (And after an exciting Ping Pong Finals match-up, FranciscoL was the runner-up with Janos taking the championship!)

This morning before we started the PR3 moves which unlocked the IFO, I tried turning on a gentle boost in DHARD P, shown in the first screenshot:

  zpk([0.5+i*0.6245;0.5-i*0.6245],[0.34375+i*0.429344;0.34375-i*0.429344],1,"n")gain(4.00641)gain(0.639513)gain(0.82635)

This made a modest reduction in the RMS, which could be slightly better if the boost is made more aggresive. 

The noise at 1Hz is coherent with LSC MICH. 

Thu May 16 10:14:58 2024 INFO: Fill completed in 14min 54secs

Gerardo confirmed a good fill curbside.

With our 3-hr range drop earlier this morning which is coincident mainly with seismic from 3-10Hz in corner (smaller at end stations & for 10-30Hz band), got some practice running new "Low-Range Check" dtt template (wiki link) with a time of 1317utc (617PDT).  Notables on it is the noise increase seen in the DARM spectrum from 18-70Hz; can also see slight jitter increase for WFS B Yaw from 7-13Hz.

Template Note:  Sheila mentioned for Input tab/NDS2, we can leave Epoch Start Time as is, and for the Stop Time you can go back 10min (I'll  update the wiki to show this note).

This morning H1's range had a 15 Mpc dip during the morning traffic (around 5am local, 13 UTC time), due to noise from 20-50Hz (summary pages plot).  This also shows up as more glitches in this frequency band in omicron.

This spike in traffic happens at this time each weekday, but has not had this kind of impact on the interferometer in previous days.

TITLE: 05/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

H1's been locked 21.25+hrs.  There was a notable drop in range of 20Mpc over the last 3hrs and it's fairly coincident with a similar environmental 3-30Hz (larger in 3-10Hz band) seismic increase seen primarily at the corner station (and to a smaller extent at the EX/EY buildings) over the same time of the H1 range drop.  Winds have been normal during this time.

Commissioning is planned again from 9-noon this morning.

nuc33's SQZ dtt crashed 2nd day in a row.

TITLE: 05/16 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Observing for the entire shift. Locked for almost 15 hours.

Jenne, Sheila

This morning we accepted SDF diffs for A2L gains at the end of the commissoning time, as Jenne had been working on and ran the new A2L script (first screenshot).  After going back to observing, the CHARD P coherence with DARM was still high, so after the calibration measurements I took a few minutes to manually tune P2L for the ETMs only (second screenshot).

We need to reduce the DHARD rms to make our SRCL to darm coupling more stationary, (77729 77666) I ran a noise injection to measure the DHARD P loop this morning.

Elenna measured the hard loops and compared them to a model while we had 430kW in the arms in 69597, today's measurement is with 375kW. I used a template I found in userapps/h1/asc/templates/DHARD/DHARD_P_broadband_excitation.xml, which I think is the one that Elenna tuned in 69597.

Attached is a very simple script that uses dttxml to get the transfer function data from an xml file, getting the IN2/exc/IN1/exc unbiased transfer function.  I also plotted uncertainties based on 10506, calculating an uncertainty for magnitude and phase from in1/exc and in2/exc separately and adding them in quadrature (this is not the correct way to add these uncertainties).

It seems like we have room to add a boost to this loop. 

We got a notification that the WAP was on in the LVEA, EX, EY at 1700PT (0000UTC). Trending the H1:CDS-WAP_{LVEA,EX,EY}_STATUS channel they transition from state 2 (off) to state 0 for ~5 seconds. This last happened on April 20th, again at exactly 1700PT. CDS was looking into this, but I don't think we know yet if the wireless actually came on or not.

Closes FAMIS 25991 last checked in alog 77785.

Things of note:

ETMY_ST1 has a notably different trace shape for channels, Y_ST1_CPSINF_V1, EY_ST1_CPSINF_V2, EY_ST1_CPSINF_V3:

1. In the 1Hz-10Hz range, the more current reading has less noise
2. In the 10-20Hz range, the more current reading has more noise in the form of both new and higher amplitude peaks.

Other than this, measurements look comparable to last week's check. PDF Attached.