TITLE: 10/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.47 μm/s
QUICK SUMMARY: IFO been in NLN for 4h40

High Pitched Fire Panel alarm in the CUR was on 15:58 to 15:00:45UTC as the FAC team worked with the fire system. Tagging DetChar

ITMY mode 5 and 8 are not damping so I will try turning gains to zero, plot attached. 73826. Tagging SUS.

The H1 system gave me a call this morning (~10:20 UTC 10/30), but when I checked the system in NoMachine, the IFO was at INCREASE DARM OFFSET and relocking and I couldn't find any issue (perhaps the timer ran over the limit?). However, once we got to NLN (10:26), I did see that the SQZ_MANAGER guardian was having some trouble, showing the warning, SQZ ASC AS42 not on??? in the guardian message log. It would cycle between this message and going back into FDS, so I hit RESET_SQZ_ASC before trying to go back into FDS, which looked to have solved the issue. - Tagging SQZ.

TITLE: 10/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Austin
SHIFT SUMMARY: We stayed locked the whole shift 13:07 as of 07:00UTC, I found new settings for ITMY mode8 (FM1+FM6+FM10, G=+0.4) and possibly ITMY mode5/6 (FM6+FM8+FM10, G=-0.02) I left mode 5s gain at zero since I'm not too sure about it yet.

05:21 I went to comissioning to run a calibration measurement alog73828

05:53: Back to Observing

• DIAG_MAIN kept flashing "PSL_FSS_TPD: RefCav transmission is low, fix alignment" tagging PSL
• ITMY mode8 and mode5 nominal settings are no longer working
  • I've tentitively found some new settings for ITMY mode 8 that are working quite well this lock, FM1+FM6+FM10, G=+0.4, I swapped FM3 to FM6 (+60 to +30 phase). I'll see if it continues to work on another lock before adding it to lscparams in which I set the gain to 0 to avoid ringing it up during automated owl locks and I reloaded ISC_LOCK after I finished the calibration measurement. Tagging Opsinfo, SUS
  • I probably should have set mode5s gain to zero as well in lscparams but I forgot, I also think I found new working settings. I swapped FM7 for FM8 (-30 to +30 phase) and used the same gain of -0.03 and the mode seemed to start to damp without ringing up mode6. It's pretty slow so it probably not the optimal setting

INFO | bb output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20231030T052240Z.xml

Simulines:

GPS start: 1382678928.729304

GPS stop: 1382680256.772195

2023-10-30 05:50:38,627 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20231030T052832Z.hdf5
2023-10-30 05:50:38,648 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20231030T052832Z.hdf5
2023-10-30 05:50:38,659 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20231030T052832Z.hdf5
2023-10-30 05:50:38,671 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20231030T052832Z.hdf5
2023-10-30 05:50:38,683 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20231030T052832Z.hdf5
ICE default IO error handler doing an exit(), pid = 2479290, errno = 32
 

STATE of H1: Observing at 155Mpc

• We've been locked for 9:10 (Longest lock this weekend)
• Microseism is rising

TITLE: 10/29 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Camilla (DAY)
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.20 μm/s
QUICK SUMMARY:

• The IY modes continue to be a little troublesome, ITMY mode5 is now rising under nominal settings, ITMY mode8 seems to be damping today with a positive gain. I'll set ITMY mode8 gain to 0 in lcsparams.py if we have a LL and reload ISC_LOCK
• VAC/Dust/SUS/SQZ looks good, H1LSC_GDS has a CFC error - this was from Camilla alog73773
• If I see Livington lose lock I'll run a calibration suite
• We've been locked for 5:15

TITLE: 10/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:  Didn't take calibration measurements as we weren't thermalized, if LLO is down Ryan with take it.
LOG: ITMY mode8 was increasing so I turned off the gain this morning and then used half the gain (0.1) with the opposite sign to slowly damp it this afternoon. Ryan tried this in 73812. Nothing changed in lscparams but Ryan thinks we should save lscparams to keep gain at zero if we have a lockloss. Tagging SUS.

• 16:01UTC Lockloss 73818
  • Intital alignment to relock.
  • 25 minutes for ADS to converge before observing.
  • SQZ High Freq again started bad, I attempted to adjust OPO temperature but it didn't help.
  • 18:16UTC Back to Observing
• 18:30 - 18:31 UTC Out of Observing to revert OPO temperature change
• 22:35- 22:46UTC SQZ SHG unlocked and FC struggled to relock 73822

SHG PZT volts was close to railed at 100V with temperature drifts, see attached. We do have a checker for this when the IFO isn't in NLN 71595 but this drift was quick.  It automatically relocks at a better PZT value (56V, middle of range). It unlocked at 22:33UTC and we were back in observing at 22:46.

SHG was v. quick to relock but the FC was slow, not really finding IR ad failing at TRANSITION_TO_IR. it took ~7 attempts to lock. I paused SQZ_FC in DOWN after 4 failed lock attempts an touch FC2 as in 73797 but the green FC trans was already good. After 3 more attempts it locked itself.

Sun Oct 29 10:09:07 2023 INFO: Fill completed in 9min 3secs

After 3h56 at NLN. 1382630509 this is the longest lock we've had in 24 hours.

Similar glitches in DARM/ETMX in the 750ms before lockloss, see attached and compare to 73817, 73578, 73539.

As yesterday, 73804, we still have some large temperature drifts in LVEA zone 5. Plot attached. Also seeing EY VEA temperature drop, will keep an eye on this..

TITLE: 10/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY: IFO has been locked for 3 hours. Plan to do calibration measurements at 11amPT.

There was a lockloss at 10:49UTC 1382611811 after 3h45 at NLN. Followed by an automatic relock (3 locklosses around DRMI locking).

Took MICH FF measurements following instructions in lsc/h1/scripts/feedforward/README.md but running MICHFF_excitation_ETMYpum.xml. Data saved in lsc/h1/scripts/feedforward/ as .txt files. Last tuned MICH in 73420. 

I saved a new filter in FM6 as 27-10-23-b (red trace) but it made the MICH coupling worse between 20 and 80Hz so we left the original (pink trace). We could try to re-fit the data to load in Wednesday's commissioning period.

Sheila, Naoki, Camilla

We took FDS, Anti-SQZ and Mean SQZ data at different NLGs: 14, 17, 43, 82 and 123. We think we see evidence of frequency noise. We see less squeezing at high NLGs: around 4.5dB of SQZ at NLG < 43.1 but at NLG 81.9 and 122.8, squeezing at 1kHz reduced to 3.6 and 3.1dB. Attached Plot.

Each time we optimized SQZ angle around 1kHz. Because of this, the low frequency increased noise at high NLGs could be due to incorrect rotation, rather than phase noise. 

Data saved in /camilla.compton/Documents/sqz/templates/dtt/20231025_GDS_CALIB_STRAIN.xml

Vicky and Naoki did an NLG sweep on the Homodyne in 73562.