Per WP11435 I performed a health check on the Kepco power supplies at EY, EX, and CER.
EY -All supplies pass, no excess vibrations, no sounds, good airflow, no temperature issues.
EX - All supplies pass, no excess vibrations, no sounds, good airflow, no temperature issues.
CER - All but one supplies pass, no excess vibrations, no sounds, good airflow, no temperature issues.
** ISC C1 - Slot 38 RHS N18V 6A 99F at fan housing, 105 at rear, very slight fan stumbling / rumbling. We need to keep an eye on this one, spare supply is staged.
While heading out to EX I spied some wildlife very close to the OSB. Coyote attacks on people are very rare. What to do if a coyote approaches you, make noise, clap your hands, whistle, they will move along.
Detchar, please tell us if the 1.66Hz comb is back.
We changed the OM2 heater driver configuration from what was described in alog 72061.
We used a breakout board with jumpers to connect all OM2 thermistor readback pins (pin 9, 10, 11, 12, 22, 23, 24, 25) to Beckhoff at the back of the driver chassis. Nothing else (even the DB25 shell on the chassis) is connected to Beckhoff.
Heater voltage inputs (pin 6 for positive and 19 for negative) are connected to the portable voltage reference powered by a DC power supply to provide 7.15V.
BTW, somebody powered the OM2 heater off at some point in time, i.e. OM2 has been cold for some time but we don't know exactly how long.
When we went to the rack, half of the power supply terminal (which we normally use for 9V batteries) was disconnected (1st picture), and there was no power to the heater. Baffling. FYI, if it's not clear, the power terminal should look like in the second picture.
Somebody should have snagged cables hard enough, and didn't even bother to check.
Next time you do it, since reconnecting is NOT good enough, read alog 72286 to learn how to set the voltage reference to 7.15V and turn off the auto-turn-off function, then do it, and tell me you did it. I promise I will thank you.
Thermistors are working.
There is an OSEM pitch shift of OM2 at the end of the maintenance period 3 weeks ago (Aug 29)
Having turned the heater back on will likely affect our calibration. It's not a bad thing, but it is something to be aware of.
Indeed it now seems that there is a ~5Mpc difference in the range calculations between the front-ends (SNSW) and GDS (SNSC) compared to our last observation time.
It looks like this has brought back the 1.66 Hz comb. Attached is an averaged spectrum for 6 hours of recent data (Sept 20 UTC 0:00 to 6:00); the comb is the peaked structure marked with yellow triangles around 280 Hz. (You can also see some peaks in the production Fscans from the previous day, but it's clearer here.)
To see if one of the Beckhoff terminals for thermistors is kaput, I disconnected thermistor 2 (pins 9, 11, 22 and 24) from Beckhoff at the back of the heater driver chassis.
For a short while the Beckhoff cable itself was disconnected but the cable was connected back to the breakout board at the back of the driver chassis by 20:05:00 UTC.
Thermistor 1 is still connected. Heater driver input is still receiving voltage from the voltage reference.
I checked a 3-hour span starting at 04:00 UTC today (Sept 21) and found something unusual. There is a similar structure peaked near 280 Hz, but the frequency spacing is different. These peaks lie on integer multiples of 1.1086 Hz, not 1.6611 Hz. Plot attached.
Detchar, please see if there's any change in 1.66Hz comb.
At around 21:25 UTC, I disconnected OM2 thermistor 1 (pins 10, 12, 23, 25 of the cable at the back of the driver chassis) from Beckhoff and connected thermistor 2 (pins 9, 11, 22, 24).
Checked 6 hours of data starting at 04:00 UTC Sept 22. The comb structure persists with spacing 1.1086 Hz.
Electrical grounding of the beckhoff systems has been modified as a result of this investigation -- see LHO:73233.
Corroborating Daniel's statement that the OM2 heater power supply was disrupted on Tuesday Aug 29th 2023 (LHO:72970), I've zoomed in on the pitch *OSEM* signals for both (a) when the suspected time of power distruption (first attachment), and (b) when the power and function of OM2 was restored (second attachment). One can see that upon power restoration and resuming the HOT configuration of TSAMS on 2023-09-19 (time (a) above), OM2 pitch *decreases* by 190 [urad] over the course of ~1 hour, with a characteristic "thermal time constant" exponential shape to the displacement evolution. Then, heading back to 2023-08-29, we can see a similar shaped event that causes OM2 pitch to *increase* by 160 [urad] over the course of ~40 minutes (time (b) above). Then at 40 minutes IFO recovery from maintenance begins, and we see the OM2 pitch *sliders* adjusted to account for the new alignment, as had been done several times before with the OM2 ON vs. OFF state changes. I take this to be consistent with: The OM2 TSAMS heater was inadvertently turned OFF and COLD on 2023-08-29 at 18:42 UTC (11:42 PDT), and The OM2 TSAMS heater was restored turned ON and HOT on 2023-09-19 18:14 UTC (11:14 PDT).
This morning I ran the OPLEV charge measurement for both of the ETMs. ETMY saw some overflows during the measurement.
ETMX seems to be trending downward towards zero but most of the quads are above +\- 50 [V], ETMY seems stable and none of the quads are above +/- 50 [V].
Tue Sep 19 10:05:33 2023 INFO: Fill completed in 5min 30secs
Note, cooler outside temps mean the TCs did not saturate at -200C.
After we found the CO2X power has been degrading in 72943, I recalibrated the CO2 rotation stages this morning. Last done in March 66724.
Added a README.txt file to /opt/rtcds/userapps/release/tcs/h1/scripts/RS_calibration/ with instructions.
Also adjusted lscparams to output the existing values. Plan to relock with yesterdays output and then during lock, adjust CO2X to output 1.68W as the start of O4.
tcs_nom_annular_pwr = {'X': 0.95, #change back to 1.03 after alog72943 test
'Y': 1.19}
Picket Fence was updated with new epics channels that report IOC uptime, Picket Fence window uptime, and time since last good data was processed, from which a run status variable is determined.
New channel names are:
H1:SEI-USGS_SERVER_START_STR
H1:SEI-USGS_SERVER_UPTIME_SEC
H1:SEI-USGS_SERVER_UPTIME_STR
H1:SEI-USGS_LAST_PROCESS_GPS
H1:SEI-USGS_LAST_PROCESS_STR
H1:SEI-USGS_SINCE_LAST_PROCESS_SEC
H1:SEI-USGS_SINCE_LAST_PROCESS_STR
H1:SEI-USGS_SERVER_RUNNING
H1:SEI-USGS_IOC_START_GPS
H1:SEI-USGS_IOC_GPS
H1:SEI-USGS_IOC_START_STR
H1:SEI-USGS_IOC_UPTIME_SEC
H1:SEI-USGS_IOC_UPTIME_STR
H1:SEI-USGS_IOC_HOSTNAME
H1:SEI-USGS_IOC_PROCESS
TJ, Camilla. At 15:20 to 15:37 we drove CO2Y PZT at 80Hz and then 45Hz using H1:TCS-ITMY_CO2_PZT_OUT_GAIN_EXC via awggui, see attached. This was to check that we could drive a line using the CO2 PZT that we can later use to inject noise into DARM to understand if in future we'll need to re-install the CO2 ISS (Aidan started T2200341). Hope to repeat with H1 locked later.
Also saw that that CO2Y power meter that is measuring power injected to te IFO saw more lines than CO2X when no excitation was driving either PZT, see attached.
Control room wall displays were updated and restarted.
TITLE: 09/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventative Maintenance
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 6mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.51 μm/s
QUICK SUMMARY: H1 unlocked around 5 hours ago and was not able to relock (see alog 72955 for details). H1 is now down for Tuesday maintenance.
Workstations were updated and rebooted. The updated included OS packages and Conda packages. The default Conda environment is also upgraded to Python 3.10.
A list of updated Conda packages can be found here in both the September 5th and 4th versions.
The IFOs been struggling to relock following this LockLoss. It couldnt find DIFF IR a few times and I had to intervene (I only had to tap DIFF offset once or twice and it found it) and I ended up doing an initial alignment as it couldn't get
past PRMI, we spent about 10 minutes in CARM_TO_TR before it said "NO IR IN arms" after the IA. It lost lock shortly after at 14:24UTC.
Each relock seems to have the same trouble with DIFF IR, it being just 1 or 2 taps away but saying NO IR found
TITLE: 09/18 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 135Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Windstorm rolled through this evening and it was surprising how long H1 was able to stay locked through it (it almost made it through, but eventually succombed.). Squeezer caused one drop from Observing.
LOG:
Green arms are now aligned but H1 has had locklosses at early stages (i.e. FIND IR & LOCKING ALS), but winds are still hitting about 25mph. So will hold at LOCKING ARMS GREEN and then try for more in about 30min.
The wind storm still rages, but it might be showing hints of calming.
There was a 2-min drop from observing due to the Squeezer's IR Filter Cavity unlocked at 0114utc (it came back on its own).
Lockloss at 0327 (Observatory mode taken to LOCK ACQUISITION at 0330 as I was making supper).
At the time winds were beginning to calm down.
Currently at INCREASE FLASHES for both arms.
Starting around 30+min ago, the wind gusts have passed the 30mph threshhold and are touching 40mph! This is leading to our local "perfect storm": (1) high winds (see image #1) and (2) high microseism (see image #2).
Jeff mentioned the distinct noise bump on DARM between 20-80Hz (see image #3) is characteristic of stray light hitting our EX Cryobaffle when we have a noisy environment such as this. This has also dropped our range down around 100Mpc (from 140) [see image #4].
With all this said, it's impressive H1 is riding through this noisy Earth! According to NOAA, we will be under a red flag warning (screenshot is image #5) for another ~3hrs (or 8pmPT / 0300utc).
~0018utc Wind gust hit around 50mph at EY!
The BBB channel was continually going into the alarm range. It's been removed from Picket Fence FOM and EPICS.
The steps for removal were:
1. Edited /opt/rtcds/userapps/release/isi/h1/scripts/Picket-Fence/LHO-picket-fence.py. Commented out the block at line 39 that adds the "BBB" channel.
2. VNC to nuc5. Close the Picket Fecne window.
3. ssh as controls to nuc5. Run "start/launch.sh". This restarts the Picket Fence FOM, which also sets the EPICS variables.
Thanks Erik.
FYI - There are a bunch of stations around the Vancouver area, but BBB is the only one hosted by PNSN. We've reached out to see if we can get access to a similar low-latency server so that we can hopefully find a quieter station to use. These stations are useful for monitoring incoming motion from Alaska.