Elenna, Gabriele, Camilla 

This afternoon we updated the MICH Feedforward, it is now back to around the level it was last Friday, comparison attached. Last done in 72430. Maybe need to be done so soon because of the 72497 alignment changes on Friday.

The code for excitations and analysis has been moved to /opt/rtcds/userapps/release/lsc/h1/scripts/feedforward/

Elenna updated in guardian to engage FM1 rather than FM9 and sdf accepted. New filter attached. I forgot the accept this in h1lsc safe.snap and will ask the operators to accept MICHFF FM1 when we loose lock or come out of observe(72431), tagging OpsInfo.

Attached is a README file with instructions.

FAMIS 26055, last run in alog 72310

Most V_eff values are trending upwards while a few are staying flat, with ETMX's increase being the most dramatic (more noticeable likely because the ETMX measurement has not been run in over a month according to this week's plot).

Vicky, Naoki, Sheila

Summary: We tried to improve squeezing by walking alignments, this wasn't sucsesful.  We did see that we were able to increase the ADF IQ SUM while decreasing sqz, which we didn't understand.

Since we saw a small improvement in sqz on the homodyne yesterday after moving ZM3, today we tried to move the filter cavity axis to see if we could reduce clipping while injecting sqz into the IFO.  We injected the ADF and set offsets on the FC green trans green QPD A, and watched for higher ADF.  The QPD offset didn't have much of an effect itself, we did however see a 10% increase in the ADF IQSUM channel while the AS42 loops had a large transient because of our QPD step.  

We were able to recreate the higher ADF IQ SUM by setting an offset of -0.3 in AS_A_RF42_YAW, but this didn't visibily improve the squeezing or range (we tried switching the offset back and forth several times, the initial improvement wasn't reproduced). 

We did some further steps, and saw that we could increase the ADF IQ SUM even further, but that the squeezing level was reduced with the higher ADF.  We wondered if we were being confused by a change in the squeezing angle.  We checked the sqz angle with and without the yaw offset engaged, rotating the sqz angle didn't explain the difference we saw with the alignment offset. 

After regenerating the NonSENS c-code and restarting the h1bos and h1oaf models yesterday, I tried some new cleaning during our commissioning time this afternoon.  Now I can get all 3 of LSC, Jitter, and Laser noise subtraction all to work, with no mysterious minus signs needed.

Attached is my DTT 'NonSENS budget' from a time when we were still in commissioning.  The blue is the CALIB_STRAIN_NOLINES channel, and red is CALIB_STRAIN_CLEAN.  The black is the sum of all the other colors' noise estimates.  This LSC subtraction was from a time before the MICH FF was retuned, so it may not have as big an effect were I to turn it on now that MICH FF was updated.

TITLE: 08/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 12mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: H1 started observing about 15 minutes ago after the ADC issue was fixed. Wind is not as bad as yesterday.

• All systems look good

TITLE: 08/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

Lock#1:

Lockloss at 16:18UTC

The squeezer kept losing lock all morning, and the ISS saturated.

Lock#2:

After some investigation while we were relocking it was found that FC1 was having troubles, Fil power cycled the chassis and then swapped the coil driver and satellite box for a spare. But none of these actions were successful to fix the issue.

We required NLN at 17:52, but we stayed out of Observing while the FC1 investigation/work was ongoing. It was narrowed down to an issue with the T3 BOSEM on FC1. An old (2011) ADC card ended up being swapped for a new one (2021) which was the root of issue! Fil swapped back the original coil drivers and satellite box. Alog72558 documenting the process

I took a broadband and simulines calibration measurement during the investigation time, then a second one later on in the afternoon.

Back into Observing at 22:46UTC after squeezer commissioning and MICHFF testing.                                                              

LOG:                                       

I ran a 2nd calibration sweep today, starting with broadband:

/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20230830T212846Z.xml

Simulines:

2023-08-30 21:58:00,615 | INFO | Commencing data processing.
2023-08-30 21:58:56,567 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20230830T213653Z.hdf5
2023-08-30 21:58:56,585 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20230830T213653Z.hdf5
2023-08-30 21:58:56,611 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20230830T213653Z.hdf5
2023-08-30 21:58:56,636 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20230830T213653Z.hdf5
2023-08-30 21:58:56,661 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20230830T213653Z.hdf5

GPS start: 1377466629.697354

GPS stop: 1377467954.983395

Brian and I had a meeting with seismologist at the National Earthquake Information Center in Colorado. They pointed us to a very cool tool called MUSTANG that shows statistics for every seismic station that is fed into the IRIS Data Management Center (DMC).

The tool can be found here:https://services.iris.edu/mustang/

It can be queried by changing the URL at the top, they have a few examples. One interesting rabbit hole we went into was looking at spectrograms for the LHO vault seismometer, known to the IRIS DMC as UW.LIGO. Here are the spectrogram results for the three components:

https://services.iris.edu/mustang/noise-pdf-browser/1/spectrogram?target=UW.LIGO..HH*.M&starttime=2019-03-01&endtime=2023-07-01 (also shown in figure attached)

You can see the seasonality of the microseism and also another periodic low frequency signal of unknown origin. There are tons of interesting things to look at, like the ground motion models:

http://services.iris.edu/mustang/noise-pdf-browser/1/breakout?target=UW.LIGO..HHZ.M&time=2022-01-01T00:00:00&interval=year (also shown in figure attached)

Just putting it out here in case anyone wants to check it out and go down the same rabbit hole Brian and I did.

J. Kissel, L. Dartez

Given that we now like Gabriele / Elenna's new DARM2 boost filter in FM8, and it's been turned on permanently as of 2023-08-30 19:03:47 (12:03:47 PDT) -- see LHO:72562 -- we need to update the calibration infrastructure to handle it. Attached is a screenshot of the DARM1 and DARM2 filter banks as we want them now.

As such, we've done the following:

(1) Copy over the latest H1OMC.txt filter file (where we just have to know that that's where the DARM2 lives) that has the new filter in it over to the calibration SVN's filter archive.
    $ chans
    $ cd filter_archive/h1omc/
    $ ls -ltr # to find the latest filter file -- is H1OMC_1377459704.txt, and it was modified at 2023-08-30 12:41 PDT
    $ cp H1OMC_1377459704.txt /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/H1CalFilterArchive/h1omc/
    $ cd /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/H1CalFilterArchive/h1omc/
    $ svn add H1OMC_1377459704.txt
    $ svn commit -m "(our commit message)"

(2) Update the call to this filter file, and the filter modules used in "the" pydarm parameter file.

   (a) Make sure the local copy of the pydarm_H1.ini list of "static" parameters is up-to-date with no local changes.
    $ cd /ligo/groups/cal/H1/ifo/
    $ git fetch
    # use a combination of 
        $ git status
        $ gitk 
        $ git gui 
    # and just *looking* at the pydarm_H1.ini file to understand where things stand.

    # We found that there were lots of local uncommitted changes from a major overhaul on July 30 where all comments were stripped from the file and variables were re-arranged
    # We *think* there was no functional change, so we committed all the changes.
    $ git add pydarm_H1.ini
    $ git commit -m "(our commit message)" pydarm_H1.ini
    # got some git crap about my email address not beign the right email address... had to
    $ git config --global user.name "Jeff Kissel"
    $ git config --global user.email jeffrey.kissel@ligo.org
    $ git commit --amend --reset-author
    # that popped open another message with vim interface, had to blindly hit enter or :wq, or q a bunch of times...
    # ran 
    $ git log
    # to confirm that we've staged the commit appropriately (and Louis assures me I have)
    $ git push
    This brings pydarm_H1.ini to git hash 0185c1d7.

    (b) *Now* make the changes that we actually need to change,
    $ gedit /ligo/groups/cal/H1/ifo/pydarm_H1.ini
        # change line 48 
        digital_filter_modules = 1,2,3,4,7,9,10: 3,4,5,6,7 ==>> digital_filter_modules = 1,2,3,4,7,9,10: 3,4,5,6,7,8
        # change line 50
        digital_filter_file = cal_data/H1OMC_1336944438.txt ==>> digital_filter_file = cal_data/H1OMC_1377459704.txt
    $ git add pydarm_H1.ini
    $ git commit -m "(our commit message)" pydarm_H1.ini
    $ git push
    This brings pydarm_H1.ini to git hash 3c57e5f9.

(3) We *also* need to make sure that this "cal_data" folder is meaningful. So we have to update a disctionary inside the pydarm_cmd_H1.yaml "pydarm command line infrastructure parameter set,"
    (a) We also checked the local status of this file against the mothership, and we see that there are also lots of uncommitted differences. 
        Louis assures me that he understands these differences, but we can't commit them now. *sigh*

    (b) So, we changed the local file as it was.
        # change line 78
        digital_filter_file: "Common/H1CalFilterArchive/h1omc/H1OMC_1336944438.txt" ==>> digital_filter_file: "Common/H1CalFilterArchive/h1omc/H1OMC_1377459704.txt"

    Again, this version of the pydarm_cmd_H1.yaml NOT yet committed.

I ran a calibration sweep this afternoon, starting with the broadband:

/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20230830T190736Z.xml

Simulines:

2023-08-30 19:36:43,647 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20230830T191430Z.hdf5
2023-08-30 19:36:43,663 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20230830T191430Z.hdf5
2023-08-30 19:36:43,674 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20230830T191430Z.hdf5
2023-08-30 19:36:43,684 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20230830T191430Z.hdf5
2023-08-30 19:36:43,696 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20230830T191430Z.hdf5

GPS start: 1377458086.806734

GPS stop: 1377459422.017018

We've reaquired NLN at 17:52UTC after a lockloss this morning but we're not in observing due to a potential electronics issue on FC1 for the squeeze system which is being investigated.

[Elenna, Dan, Gabriele]

We tested a filter (FM8 in DARM2) that increased the DARM gain below 3-4 Hz, where most of the RMS is accumulated.

The DARM RMS is reduced by a factor of 3. There is no immediate evident effect on the DARM noise aboev 10 Hz. However, it would be useful to test this new filter for a longer time in the future.