Summary:
- Delayed Calibration to run measurement with L1 (which didn't work, see below).
- Accidentally canceled the headless measurement (due to an errant "CTRL-C").
- pydarm report had an error and no report was generated.
- This Calibration measurement is therefore suspect due to Operator error (and should either be at next Target Of Opportunity, or just wait until Thursday)
Measurement NOTES:
- Posted heads up reminder for the Sat Morning Calibration on the IGWN channel on Mattermost and after consulting with L1 operator, decided to postpone calibration to allow L1 to thermalize.
- After all this coordination, of course when we were fixing to run the measurement, Doug gave the heads up that a thunderstorm was rolling through. We decided to proceed (1958utc) and hope L1 would survive the thunderstorm as the calibration measurement ran (L1 ended up having a lockloss within a few minutes of us starting the Calibration measurements.
- Following instructions (link)
- H1 at NLN for for ~9.5hrs (10+hrs at 60W).
- Calibration_Monitor medm screenshot is attached
- 1958-2034 utc Out of Observing for CALIBRATION
- Broadband measurement started at ~20:00utc (started twice because I [once again] I accidentally did a CTRL-C on this script [I just wanted to note the GPS time!])
- Measurement at: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250719T195955Z.xml
- Simullines measurement
- gps START time: 1436990958.617650 (20:09utc)
- gps STOP time:
- File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250719T200901Z.hdf5
- File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250719T200901Z.hdf5
- File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250719T200901Z.hdf5
- File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250719T200901Z.hdf5
- File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250719T200901Z.hdf5
- ISC_LOCK taken back to NLN for observing
Attached is a screenshot of the Calibration Monitor, and unfortunately, I did not get to run a PyDarm Report. I'm assuming this is due to my CTRL-C from the headleass measurement noted above. Because, also at the end of this measurement, there was an SDF Diff also! Luckily, Tony is here and he was able to take care of the SDF Diff. The SDF was for PCAL Y (medm is SiteMap/CAL EY) , and it was related to the In-Loop (OFS) PD(H1:CAL-PCALY_OFS_PD_OUT16) being railed at -7.8. Tony fixed this by toggling the Loop Enable Button (H1:CAL-PCALY_OPTICALFOLLOWERSERVOENABLE) to Off and then On. This is all mentioned on the top of the PCal Known Issues wiki.
Once the SDF was cleared H1 was taken back to Observing, but there was discussion about trying to run the calibration again since L1 was still relocking. Opted to not drop out of Observing for this since we were already out of Observing for over 30min.