Today I spent some more time moving POP spot positions as well as soft again. In the end we have gone back to where we were over the weekend.
At John W.'s request, I took another measurement now that several days have passed since pumping was stopped Pumping stopped last week at 14 microns -> Today's "post-pumping" reading was 29 microns (warm day, 92F).
TITLE: 06/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: locked and then commissioning
LOG:
In the past week we have had two timing alarms:
| Monday 6/12 01:19 UTC [Sunday 6/11 18:19 PDT) | EY GPS |
| Saturday 6/17 23:15 - 23:24 UTC (16:15 - 16:24 PDT) | MSR Master GPS |
The first was a short (one minute) alarm from EY GPS (CNS-II). I trended all the EPICS channels on this system and only found that the Dilution of Precision (DOP) and the Receiver mode channels showed any variation at this time (number of satellites locked did not change). Does this mean it is a real or bogus error?
The second was a longer alarm (9 minutes) with the MSR master's GPS receiver (I think the internal one). The only channels in alarm were "GPS locked", the the MSR comparator channel-01 (MFO GPS). This would suggest a real problem with the Master's GPS receiver?
Time to pass this over to the timing group for further investigation (Daniel, Zsuzsanna, Stefan?)
These are error messages seem real, but are non critical. The internal GPS is only used to set the GPS date/time.
O2 Update:
Tuesday Maintenance plans:
Refer back to LHO aLog 36739 to walk back through these reports. I'll attach the updated map to a comment shortly.
NOTICE--There is a location that may be quieter than ITMY STS2!!
Roam6 is located just west of of BSC4s NE SEI Pier. So this is certainly now farther from the south wall than ITMY STS2-B as well as any other previous Roam position. The attached plots show my typical plots comparing quiet time [18 June 1200 utc] to a windy time [16 June at 1800 utc.] These times are free of EQ activity.
The first plot is just the corner station wind. The windy time direction is a very steady 90 degrees or right down the Yarm to the CS.
The big news is seen on the X dof plot where the HAM5 roaming seismo is quieter than the ITMY STS2 during the windy period from about 90mHz down by maybe a factor of 2. Yes, the useism band is generally higher during the windy period.
Bottom line, keep looking while we have a machine functioning with which to look.
Here is the updated locations map.
While checking on the laser this morning I noticed the diode chiller warning light (on the LASER MEDM screen) turn red briefly, then back to green. I went to the chiller room and hung out for a few minutes, watching the diode chiller, and sure enough it was intermittently flashing a "Low Water Level" warning (not an alarm, just a warning). I added 500 mL of water and this behavior quit.
TITLE: 06/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
Wind: 13mph Gusts, 10mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.07 μm/s
QUICK SUMMARY:
TITLE: 06/19 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
Lock segment of 60+hrs ended during this shift. Back to observing in 35min. Have had very steady range hovering at or just under 70Mpc (with minimal glitch drops seen on the Inspiral Range plot). Had an odd temperature alarm (see earlier alog).
LOG:
FAMIS 7443 (from script) Laser Status: SysStat is good Front End Power is 33.95W (should be around 30 W) HPO Output Power is 156.9W Front End Watch is GREEN HPO Watch is GREEN PMC: It has been locked 12 days, 18 hr 22 minutes (should be days/weeks) Reflected power = 16.86Watts Transmitted power = 57.94Watts PowerSum = 74.8Watts. FSS: It has been locked for 0 days 2 hr and 32 min (should be days/weeks) TPD[V] = 2.812V (min 0.9V) ISS: The diffracted power is around 3.2% (should be 3-5%) Last saturation event was 0 days 2 hours and 32 minutes ago (should be days/weeks)
13:40utc: Received a "CS temperature is low" Verbal Alarm.
I checked the FMCS & Dust Monitor temperatures in the LVEA, but I did not see a drop in temperature. (In fact, the FMCS signals were all trending up at the time.) I'm wondering if I should be looking at another channel? Trends of the LVEA FMCS Zone Temps for the last 7days is attached.
For the Corner Station, Verbal looks at H0:FMC-LVEA_AVTEMP_DEGF. This channel does show a bit of a drop last night during the alarm (see attached 5 day trend), but this was not near its alarm limit and not even during the time of the alarm (see second attachment for 1 day plot of full data with a line on time of alarm). I have no idea why it may have falsely alarmed here, and I worry. I will look further into this.
About the test: The test will check that the temperature is within +/-1F of the nominal, with the nominal for the CS set to be 69.5F. This number I got when I asked either John or Bubba over a year ago, so it may need updating.
Most of the trends are flat on these trends.
H1:HPI-PUMP_EY_CONTROL_VOUT had a step up from 505 to 515 around May 23rd.
This CLOSES FAMIS #4533.
I suspect temperature when ever the pump output changes. Sure enough, the attached plot shows the VEA temp stepping just as the VOUT (pump speed) steps. Corey's time span just misses the much larger gyrations seen on the VEA temp and the pump speed.
H1 continues to run well (current lock is 59+hrs long). One glitch/range drop at around 9:22utc.
Noticed VIDEO2's medms (CDS & OPS overviews) were froze since Sat night, so opened new ones.
TITLE: 06/19 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 8mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.07 μm/s
Really low useism, sub-10mph winds, no EQs over magnitude 5.2 in the last 24hrs.
QUICK SUMMARY:
A EL3104 analog input Beckhoff terminal was replaced from EtherCAT End Station Chassis 3. Alog 36571 reported CH3 & CH4 on terminal 7 showing an offset. Used a voltage calibrator to verify offset was from EL3104 terminal and not upstream.
Updated FRS Ticket 6024. Once a few days have past, we'll review the data to confirm success and the problem is fixed.
Trend over the past 8 days. Nominal adjusted to 21.5 dBm.
J. Kissel FRS Ticket 6024 I attach two trends of the past 12 days (three more than Daniel's plot above), and the past 365 days of these local oscillator read backs of the H1 ALS Y WFS A system. One can see from the 365 day trend that these ADCs would on drift at a rate of (the equivalent of) ~0.1 [dBm / month], so we're not going to be able to see if the problem is true fixed in these 6 days since the module was swapped. So, my vote is that we close the ticket, but continue to monitor, and re-open if we find any drift in the future.