TITLE: 12/13 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.33 μm/s
QUICK SUMMARY:
H1 Is locked at NOMINAL_LOW_NOISE and OBSERVING for the past hour.
Violins lookin great!

TITLE: 12/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Relatively light maintenance day followed by some trouble getting locked, but after adjusting thresholds in ALS Guardians, was able to lock without much issue.

• 16:07 Lockloss from commissioning test, ISC_LOCK to IDLE
• 20:27 Maintenance finished, starting initial alignment
  • Troubleshooting lower ALS power
  • Manual-ed ALS Guardians to find IR; see alog74766
  • Rest of locking was fully automated
• 22:51 Reached NLN
• 22:55 Started observing

LOG:

Ryan S, Jenne D, Sheila

The ALS_COMM and DIFF nodes will check on the green arm transmission when finding IR to ensure that the arms are aligned well enough to move on. This threshold has been set to 0.75 but I lowered it to 0.65 since we've ran into this threshold as few times in the last week and have been unable to improve the arm transmission.

Last week this happened on Thursday (alog74655) and I just manualed around the state to continue locking. It worked for that lock to get us back up, and then it wasn't a problem with future locks until today. Today, the arm transmission was low for both arms so we went to confirm that there was no PR3 movement, and then we restored optics back to the start of the previous lock. This also didn't help. Looking at the arm power over the last few weeks (attachment 1), after the PR3 and table work from last Tuesday (alog74618) it has been lower than before then but as low as we were seeing today. The current thinking is that the PR3 move last week brought our powers lower, and while the table work improved the COMM beatnote, it did nothing for the arm powers. Once the IFO gets to a better full lock alignment, this alignment tends to give us better ALS power next lock acquisition, so lowering this threshold should help us get to that point and hopefully help sequential locks.

The long term solution would be to go back on table to realign the rest of the COMM path to camera, then renormalize the arm powers so that 1 is actually our max power, then bring this threshold back to the 0.75 that it was*. Going on that table always carries rick of making things worse, so we definitely don't want to be doing this right before the holidays. We will reconvene in 2024 on this issue if it's still an issue.

*There's a comment in the guardian code that it was 0.85 from Aug 12, 2020.

Jordan, Janos

We ran the functionality test on the main turbopumps in MX and EX during Tuesday Maintenance (12/12/23). The scroll pump is started to take pressure down to low 10^-02 Torr, at which time the turbo pump is started, the system reaches low 10^-08 Torr after a few minutes, then the turbo pump system is left ON for about 1 hour, after the hour the system goes through a shut down sequence.
 

MX Turbo:

Bearing Life:100%

Turbo Hours: 120

Scroll Pump Hours: 211

EX Turbo:

Bearing Life:100%

Turbo Hours: 277

Scroll Pump Hours: 6317

Closing WP 11573 and FAMIS 24846 FAMIS 24870

TJ, Camilla. WP11574

We borrowed the Ophir PH00235 USB MSP-NS-Pyro 9/5 bean scanner from CIT. It has a PH00092 removable 7.5" FL lens on the front and is on a 500mm rail. WE checked the scanner and rail worked in the lab using our Nanoscan laptop and the Nanoscan v1 software. 

On CO2X (layout T1200007) we added three Gold coated steering mirrors just after the power control waveplate. Added a beam block panel on the back of the table. While aligning we kept ther CO2 power requested at 0.1W.  Started aligning the beam to the beamscan but didn't finish before the end of maintenance. 

We left the beanscan and the three mirrors on the table, we moved the mirror that was in the path ("A" on photo) out of the path. Plan to finish aligning and take data next Tuesday. The cables and driver boxes are in a tote labeled "nanoscan" in the TCS cabinet and the laptop is back in the optics lab cabinet.  Photos of table and beampath (nominal lighter red) attached. 

Genie lift found plugged into outlet near TCSY table, unplugged.

Robert's shaker is still connected to near HAM2, it is plugged in but powered off.

All else looked good, followed T1500386

All but a few maintenance activities have wrapped up to the point where I've turned sensor correction back on and H1 has started lock acquisition.

As the first part of the TW0 raw minute trend file offload, tw0 is now writing to a new area freeing up the old files for transfer. 

nds0 was restarted at 10:44 PST to serve the past 6 months of data from their temporary location as the files are being transferred to h1daqframes-0. The file copy takes about 30 hours.

Tue Dec 12 10:08:21 2023 INFO: Fill completed in 8min 17secs

Gerardo confirmed a good fill curbside.

This morning at 8:15am (16:15UTC) I turned off the external power supply that powered both ITM HWS CCD cameras (Dalsa 1M60), located on the floor under the HWS table.  We'll plan to check the magnetometer data to see if the 74738 comb is still present.

After we stopped HWS code and remotely turned off camera's in 74738, the DARM comb still remained. Dan, Daniel, Nutsinee expect this could be the framegrabber in the HWS computer still sending a 7Hz signal. We can troubleshoot this and how the camera's are grounded to the optics table later. 

TITLE: 12/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventative Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.27 μm/s
QUICK SUMMARY:

H1 has just lost lock after 32 hours following a commissioning test. Maintenance activities have begun.

Workstations were updated and rebooted.  These were OS updates.  Conda packages were not updated.

I've taken the SUS_CHARGE node to DOWN so that the automatic in-lock charge measurements don't run before tomorrow morning's Tuesday maintenance time (and I can confirm that doing this does not take H1 out of observing). To re-enable the automated in-lock charge measurements, the SUS_CHARGE node should be requested to INJECTIONS_COMPLETE before next Tuesday.

First observed as a persistent mis-calibration in systematic error monitoring Pcal lines which measure PCAL / GDS-CALIB_STRAIN affecting both LLO and LHO, [LLO Link] [LHO Link], characterised by these measurements consistently disagreeing with the uncertainty envelope.
It us presently understood that this arises from bugs in the code producing the GDS FIR filters there exists a sizeable discrepancy, which Joseph Betzwieser is spear-heading a thorough investigation to correct,

I make a direct measurement of this systematic error by dividing CAL-DARM_ERR_DBL_DQ / GDS-CALIB_STRAIN , where the numerator is further corrected for kappa values of the sensing, cavity pole, and the 3 actuation stages (GDS does the same corrections internally). This gives a transfer function of the difference induced from errors in the GDS filters.

Attached in this aLog, and its sibling aLog in LLO, is this measurement in blue, the PCAL / GDS-CALIB_STRAIN measurement in orange, and the smoothed uncertainty correction vector in red. Attached also is a text file of this uncertainty correction for application in pyDARM to produce the final uncertainty, in the format of [Frequency, Real, Imaginary].