TITLE: 12/14 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

IFO is in NLN and COMMISSIONING

17:56:40: Range Loss Investigation 

• Dropped out of observing temporarily for 2 seconds from 17:56:40 UTC to 17:56:38 UTC. Brief investigation showed that there was a brief SDF diff in SUSETMX. There also appeared to be a BLRMs glitch around then as well as a OMC DCPD spike.
• Oli also noticed that the range dropped before the SUSETMX diff and trending this implies that the diff happened as a cause of the range drop, which then may imply that the range drop happened due to the BLRMs glitch. Note that since the range monitor is on a one minute trend, we can’t tell if the range drop happened exactly at 17:55 UTC or in the minute prior, so if this is the “first cause”, it would be hard to know.
• These have not caused SDF diffs in the past though, so will continue investigating.
• Investigating the BLRMs shows that there was a glitch at 17:54 UTC in all but 1-2khz range BLRMs. This implies that indeed the range drop was caused by a BLRMs glitch that did not register on the scope until the monitor updated its minute trend. This then could be a completely unrelated issue.
  • The OMC DCPD Window also expectedly shows a glitch at the same time around 17:53:52.
• I’ll keep an eye out if this happens again. Feel free to investigate further. Screenshots below.

(4 Screenshots)

20:45 UTC - Started running calibration measurements (1 screenshot)

• Note: New configuration for EX was active during all calibration measurements

20:50 UTC - Broadband calibration measurement started

• Note: Feedforward was off during broadband calibration

21:18- UTC - Next calibration (simuLines) started.

21:19 - UTC - lost lock (alog 74814)

21:20 UTC - Relocking

21:27 UTC - Nds0 daqd restarted by Dave right after lockloss - caused all ndscopes to stall and require resetting.

22:37 UTC - Air handler red alarm started blaring. Eric was the last person in there earlier to check on these. I called him and he’s investigating. Trends show that it was off for about 15 minutes. Alarm is back to normal as of 14:50 UTC.

23:08 - Reached NLN - Resumed commissioning.

LOG:

With different iteration than yesterday of DARM offloading configuration, I checked MICH with the current MICHFF FM8 orange and the MICH FF fitted from yesterday's data FM9 black 74791, plot attached. Surprising that in our 20-70Hz band the new FF was worse. Maybe as the data was taken when the IFO was thermalizing yesterday (2h30) rather than today after 14hr in lock.

Retook the MICH excitations at ~21:20UTC using FM8 and fit using Gabriele's InteractiveFitting GUI. Results attached. Loaded this fit into FM1 as '12-14-23' ready for when we next use the new DARM filters. Lost lock before we could test the new fit.

21:18- UTC - Calibration Measurement (simuLines) started. 

21:19 - UTC - Lost Lock

• Hepi EX watchdog tripped
• ISI EX Stage 1 and 2 watchdogs tripped
• The lockloss may have been caused by driving ETMX too hard with the new EX configuration. Louis is currently working to improve simulines so that it doesn’t happen again (see screenshot).
• Another potential cause is a 63/64hz ring-up - investigation ongoing.

Potentially (but unlikely) related - Oli also lost lock during Simulines during their shift - alog 74716

Relocking Now as of 21:20 UTC.

IFO is in NLN and OBSERVING. We are about to transition into planned comissioning for the next 3 hours (20:00 UTC - 23:00 UTC).

Thu Dec 14 10:09:22 2023 INFO: Fill completed in 9min 18secs

Travis confirmed a good fill curbside.

TITLE: 12/14 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: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING

We were kicked out of observing due to the BS camera not updating and the camera servo going back onto ADS. The ITMX camera also seems to be reading only 0's. Dave is currently working to fix this.

Happened on Nov 11 - alog74160 and Oct 25 - alog73749

TITLE: 12/14 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Lockloss 5:48 UTC https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=74799

Relocking:
6:09 UTC 2 locklosses before DRMI; starting an initial alignment.
7:14 UTC NOMINAL_LOW_NOISE reached.
7:18 UTC Observing reached.

LOG:
no log

Unknown lockloss:
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1386568144

This lockloss seems more mystierious than the last one. Wind ,Ground motion, and Pi's were all just fine.

Louis, Sheila, Jenne

Today we tried a new DARM loop configuration. We are not implementing this for observing right now, we would need to retune feedforward and redo calibration before we could do that.

There is a new guardian state in ISC_LOCK, called NLN_ETMY. This state turns off feedforward and transitions DARM control to ETMY (L3,L2, L1), it can be used when we are in nominal low noise (but not necessarily from any states before LOWNOISE_ESD_ETMX).  This was tested Tuesday morning and today, so it has worked twice.

We set up a new configuration of filters for ETMX.  Louis has been using pyDARM to model the DARM crossovers, and we will add more details about these new filters in a later alog.  The first attached screenshot shows the configuration that we first transitioned to, without the new boost.  This keeps the overall loop similar to our earlier configuration, the main differences are:

• we no longer have some low pass and high pass filters in L2 and L3 drivealign (these were left over from a DARM loop design of a very long time ago which wasn't implemented, but relied on a distributed control idea and we've struggled to get rid of them in the past.) 
• The PUM plant inversion is also moved into L2 drivealign, and we have a crossover filter copied from LLO for the L2/L3 cross over.  Now that we have removed the high pass and low pass and put our plant inversion in drivealign, it should be easier to make changes to this loop.  
• The UIM filters are kept mostly the same, with the plant inversion from L2 copied to L1 to avoid making a change.  We would like to change this so that we have more offloading to the UIM, but decided to make fewer changes at the same time today and come back to changing the UIM in the future (this should be easier to do now).
• Added a gentle 4.5Hz boost to the PUM designed by Gabriele, which reduces the drive to the ESD (which was our goal).
• removed a boost from the DARM filter bank. (Moving low frequency gain from the DARM filter bank to the PUM lock should reduce our ESD drive nonstationarity.)

Measurements:

• OLG: /ligo/home/sheila.dwyer/LSC/DARM/DARM_model/DARM_OLG.xml  (ref 14 is previous configuration, ref 1 is the new configuration without the gentle pum boost, ref 2 is new configuration with the gentle pum boost) (1st screenshot)
• PUM LOCK IN1/IN2:  /opt/rtcds/userapps/trunk/lsc/h1/templates/DARM/PUM_crossover.xml  (ref 20 new configuration without pum boost, ref 25 new configuation with pum boost). 
• the UIM crossover template needs to be retuned with the filter changes, but we didn't have time for that today. 

The last attachment shows spectra of the DAC counts for ETMX, and DCPD SUM. The new configuration with the boost on reduces the RMS counts on the ESD by a little more than a factor of 2 compared to the configuration we've been using (most of the improvement is from the additional boost).  The new configuration also supresses DCPD sum more below 10Hz.

Camilla looked at the MICH FF with the new configuration and saw that it needs to be retuned, she took measurements that can be used to do that. 

We lost lock as I was trying to semi-manually transition DARM control back to ETMY from this new configuration.

New MICHFF measurements with the new DARM offloading on were taken at at 23:20UTC after 2h30 in NLN. Saved in /opt/rtcds/userapps/release/lsc/h1/scripts/feedforward

Followed the README in the same folder and used LSC_FF_PrepareData.ipynb to create mich_ff_tofit.txt, plan to fit this tomorrow morning so we can try new MICHFF during commissioning when we next turn on the new DARM offloading.

Sheila, Elenna, Camilla. Last done in August 72140. Doing now as BRUCO shows ASC coherences 74664 and want to understand current ASC coupling beofre OM2 commissioning.

Saved in /ligo/gitcommon/NoiseBudget/aligoNB/aligoNB/H1/couplings/

The new CHARD_Y quiet time reference of H1:ASC-CHARD_Y_SM was very different to the old quiet time reference: compare new (red) to 10th August (blue) of bottom left plot attached.