Lockloss @ 03:00 UTC - link to lockloss tool
No obvious cause. As usual with these, ETMX and LSC-DARM saw the first motion before lockloss.
FAMIS 26311, last checked in alog78477
All fans look largely unchanged from last check and all within range.
Lockloss @ 00:07 UTC - link to lockloss tool
Both stages of ITMY's ISI tripped, causing the lockloss. Some trends attached; looks like the GS13s and T240s saw a kick that ITMX did not. Unsure of the origin of this, but I was able to untip the WD and bring the ISI back without issue, and H1 is already relocking DRMI.
H1 back to observing as of 01:08 UTC. Fully automated relock.
TITLE: 06/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: RyanS
SHIFT SUMMARY:
Coordinated calibration run earlier & then a lockloss later in the shift was tough to recover from (ran an alignment immediately after the lockloss, but for locking, DRMI & PRMI looked bad. When Ryan arrived he helped me tweak PRMI by hand (with huge pointing/alignment changes) to finally get flashes, and then PRMI locked! And H1 is currently going to 60W). Not sure why alignment didn't look good after an alignment.
LOG:
H1 is now back to observing as of 23:56 UTC
TITLE: 06/22 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 18mph Gusts, 13mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY: Corey is working on locking DRMI; he's ran an alignment and MICH_FRINGES has run, but buildups still don't look good. We'll keep working at it.
Just completed the Saturday Calibration mesurement with L1 & V1. H1's been locked 12hrs. Winds are picking up slightly, outside temp is 88degF.
Coordinated with LLO & Virgo a few times for this--3hrs & 15min (via TeamSpeak) before the Calibration. And then about 2min before 1830utc (1130amPT), I spoke with each operator for a final reminder and then jumped into it.
NOTE: So, I knew about this measurement (which I'm fairly new at still) because of our Operator Checksheet, where this measurement is listed as 1130amPT. Also, on the LHO Control Room whiteboard, Saturday at 1130amPT there is a note. For a more official document for O4b Calibration measurements, Jenne pointed me to the document (L2400036). In this document the times for the calibration measurements are listed in Sec3.3. In the Ops Wiki Calibration Instruction page, old times were listed (mainly the wednesday dates). For O4b, we now run these calibrations on Thursdays at 830amPT & Saturdays at 1130amPT---I updated the wiki to show this.
Measurement NOTES:
Sat Jun 22 10:08:35 2024 INFO: Fill completed in 8min 32secs
TITLE: 06/22 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: 6mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY:
H1's been locked the last 7.5hrs and it's very quiet seismically. Today's forecast high is around 98degF.
Nuc33's gwistat webpage needed to have the tab/webpage reloaded.
Oh and if all goes well, plan to run the Saturday Calibration in about 3hrs (at 1830utc). Have sent post on mattermost and pokes via TeamSpeak to LLO & Virgo.
TITLE: 06/22 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: One candidate event and three locklosses from observing this shift; one from an EQ and two that weren't obvious as to a cause. We had a few hours of downtime this shift just from locklosses in random places that I can't seem to explain (states like ALS, FIND_IR, DRMI, and one in TRANSITION_FROM_ETMX). Eventually H1 made it back to NLN and has been observing for about an hour.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 18:36 | SAF | - | LVEA | YES | LVEA is laser HAZARD | 05:15 |
| 17:54 | sqz | karmeng | opticslab | yes.local | sqz work | 23:38 |
| 23:34 | CAL | Francisco | PCal Lab | n | Packing up equipment | 23:44 |
Lockloss @ 03:22 UTC - link to lockloss tool
No obvious cause; ground motion was calm at the time.
H1 was back to observing at 05:19 UTC after having to do some work to lock DRMI, but as I type this H1 lost lock again (observing for one minute) at 05:20 UTC. No immediate cause for this lockloss.
H1 again back to observing as of 07:06 UTC
Lockloss @ 01:17 UTC - link to lockloss tool
Looks like this was some kind of ground motion according to Picket Fence and the 30-100mHz BLRMS, possibly a M5.1 earthquake from the Philippines, but there was no alert from Seismon or a transition to EQ mode. Unsure why we would be so sensitive to ground motion this weak.
H1 is already relocking automatically up to ENGAGE_ASC after going through PRMI.
H1 back to observing as of 02:15 UTC. Fully automated relock.
For FC backscatter projection, I excited the FC length signal. I basically followed the LLO's FC backscatter estimation in 65120.
The excitation result is shown in the first attachment. The FC length is excited between 4 Hz and 400 Hz and the DARM excess noise is seen between 20 Hz and 200 Hz. In the plot, the FC length signal is not calibrated and the DARM is calibrated to displacement. Note that there is no coherence between the excited FC length signal and excited DARM so this is not a linear coupling.
The FC backscatter noise is estimated using the following formula.
DARM_FC_backscatter = FCL_no_exc * sqrt(DARM_exc^2 - DARM_no_exc^2)/sqrt(FCL_exc^2 - FCL_no_exc^2)
The projection is shown in the second attachment. The projected FC backscatter is below DARM by a factor of more than 40.
WP11914, WP11918 Install ADC in h1iscex for h1pemex readout
Fil, Marc, Erik, Jonathan, Dave
In preparation for testing the new LIGO DAC card in h1susex, an ADC was installed in h1iscex which will read the new DAC's signals.
This ADC belongs to PEM, it was purchased to expand the number of accelerometers.
The ADC, its ribbon cable and interface card were installed in the h1iscex IO Chassis (see drawing). A PEM AA-Chassis was installed and connected to the ADC.
Two models were changed:
h1iopiscex: add 5th ADC
h1pemmx: readout the 5th ADC, route all 32 channels into filter modules with the names H1:PEM-EX_ADC_4_CHAN_n where n=0-31
DAQ restart was needed.
Add WAP channels to DAQ
Erik, Dave:
We took the DAQ restart as an opportunity to use the latest H1EPICS_WAP.ini which adds the missing corner station WAPs. EDC and DAQ restart needed.
Add IRIG-B signals back to end station CAL models
Keita, Fil:
The CNS-II Clock GPS receivers independent IRIG-B signals were reattached to the h1isc[ex,ey] AA chassis.
DAQ Restart
Dave, Jonathan:
The DAQ was restarted for the above model and EDC changes. There were several issues:
gds0 needed a second restart
FW1 spontaneously restarted itself after 728 seconds.
Tue11Jun2024
LOC TIME HOSTNAME MODEL/REBOOT
09:00:01 h1iscex ***REBOOT*** <<< Add 5th ADC
09:01:42 h1iscex h1iopiscex <<< new model
09:01:55 h1iscex h1pemex <<< new model
09:02:08 h1iscex h1iscex
09:02:21 h1iscex h1calex
09:02:34 h1iscex h1alsex
09:11:04 h1daqdc0 [DAQ] <<< 0-leg restart
09:11:15 h1daqfw0 [DAQ]
09:11:15 h1daqtw0 [DAQ]
09:11:16 h1daqnds0 [DAQ]
09:11:24 h1daqgds0 [DAQ]
09:12:07 h1daqgds0 [DAQ] <<< 2nd GDS0 restart
09:12:12 h1susauxb123 h1edc[DAQ] <<< EDC for WAP channels
09:16:20 h1daqdc1 [DAQ] <<< 1-leg restart
09:16:31 h1daqfw1 [DAQ]
09:16:32 h1daqtw1 [DAQ]
09:16:33 h1daqnds1 [DAQ]
09:16:41 h1daqgds1 [DAQ]
09:27:57 h1daqfw1 [DAQ] <<< Spontaneous FW1 restart
IRIB-B code was restored at gps=1402156961 for EX and 1402159619 for EY.
I checked H1:CAL-PCALX_IRIGB_DQ and H1:CAL-PCALX_IRIGB_DQ starting at 1402159619 for 20 seconds using /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/Scripts/Timing/irig_check.sh and the IRIG-B code agreed with the timestamp of the data after the leapsecond correction (which the script automatically does).
H1 was running w/o independent IRIG-B from gps=1400946722 to 1402156961 for EX, from gps=1400947702 to 1402159619 for EY.
IRIG-B codes were confirmed good right before disconnection of the IRIG-B cables and right after the restoration.
The timing system behaved w/o any suspicious behavior during the IRIG-B outage, see the attached plot. Top: X and Y and timing error. 2nd from the top: Duotone zerocross check (not the full duotone fit) for iopiscex, ey, iopsusex and ey. 3rd from the top: Duotone zercross check for h1iopomc0. Bottom: h1iopiscex and ey DAC.
Glitch of the OMC duotone at day 7th (Tue June 04) should be Jeff's test during maintenance (alog 78238), and glitch at EX on day 14 is the rebood described in the parent alog of this.
During this period, we had 3 significant LVK GW public alerts, S240531bp, S240601aj and S240601co.
H1 back to observing at 06:32 UTC.
Relocking time extended due to a M6.0 EQ that came through after DRMI locked. Also had to wait in OMC_WHITENING for 45 minutes to damp violins. Otherwise an automatic relock.