TITLE: 01/30 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Highlight of today was H1 being down for a 5.5hr Commissioning break, but it started with H1 down from a lockloss and there was a lockloss in the middle of this down time.

ALSx continued to have Autocenter issue (fix w/ FORCE button).  ALSy also would look bad after locklosses, but something happens with Full & Manual Alignment that stabilizes it for locking (mostly).  If there is still an issue, holding at LOCKING ARMS GREEN and waiting for ALS WFS to settle before moving on seemed to help.

Microseism continues to fall over the last 16hrs.

LOG:

• 1555--1619 technical cleaning in optics lab (kim)
  • 1849-1905 h2room swiffering (kim)
• 1606 Lockloss!  (right before the 1630 Commissioning time!!  For commissioning, switched gears since H1 was down to first heat OM2.
  • Initial locking attempts had ALS issues.  ALSx had issue seen yesterday where the Autocenter (WFS) was not working for ALSx, but ALS_XARM thought WFS were all offloaded.  For ALSy, the arm power just did not look stable (symptom:  arm power hovered around 1.0 but then would got into an waivering state with the power and then lose lock after a few seconds).
  • Ran Initial Alignment
    • BUT ALSx still has the Autocenter issue....so while green arms were aligning I clicked a FORCE button and WFS were engaged.  Then rest of alignment was fine.
  • Started locking....I believe this time ALSx autocenter was ok all on its own!  Also made it to NLN (1740utc) with no issues!
• 1630 Commissioning time starts:  OM2 heating was first (started around 1720); DARM offset meas with "hot" OM2; SEI test for ETMx by Jim...
• 1836-1846 CER and then to LVEA, treading lightly, to check cables (daniel)
• 1857 Dust Mon 6 (300nm) in LVEA alarm---jumped up to 34k & then 55k within 10min.
  • 1906-1912 RyanC walking out to East Bay to investigate/sniff around while treading lightly.  He did not smell anything, but did confirm seeing the large counts on the dust monitor
• 1945 LOCKLOSS
  • ALSy looked bad, so ran a manual alignment for green arms (1955-2004)
  • But still had issues with LOCKING ALS locklosses, so held at LOCKING ARMS GREEN while watching ALS WFS channels until they calmed down and then continued on past LOCKING ALS
  • DRMI initially looked ok, but not great, so eventually ran CHECK MICH FRINGES and PRMI to lock up DRMI.
• 1952-2036 Matt running down Yarm
• 2030-2122 Ibrahim Y-arm walk
• 2051-2217 CEBEX walkthru at MY (janos)
• 2101 Opening OSB Receiving Roll-Up Door (christina)
• 2158 Back to OBSERVING (post-commissioning)

TITLE: 01/31 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.28 μm/s
QUICK SUMMARY:

Observing at 156Mpc and have been Locked for over 3 hours. Secondary microseism is coming down and wind is low.

I turned on the filters for the esd etmx glitches, while we were relocking. These filters multiply to 1 so shouldn't cause any issues, the turn on didn't affect the ALS lock at the time. I have accepted the changes in the safe sdf. Still need to figure out the limit to try to ride out the glitches, so there is no effective change to the IFO at the moment. SDF changes will need to be accepted in OBSERVE, when we get there.

Thu Jan 30 10:07:13 2025 INFO: Fill completed in 7min 10secs

Gerardo confirmed a good fill curbside. TCmins [-61C, -59C] OAT (-1C, 30F) DeltaTempTime 10:07:13

Similar to a few times yesterday, the X-arm's ALS_XARM guardian thought it was good with WFS OFFLOADED, but X-Arm's Auto Center is RED w/ no inputs to the WFS filter banks (similar to what I saw in June (alog 78326). 

I'm attaching screenshot which shows a little bit of everything with ALSx: 

• X-arm locked with a low power below 1.0 (it's usually up at 1.3)  BUT it has no WFS signals---they're all zero on ndscope....eventhough it is at ETM TMS WFS OFFLOADED.
• ALS Overview with RED Auto Center
• Also have the Trigger Window

Back in June, I clicked the FORCE button on the Trigger Window and this would bring Autocentering back.  (Right now I'm running an Initial Alignment and the Autocenter was still OFF....so I did another FORCE).

H1 just lost lock before Commissioning Time (1422288412).

TITLE: 01/30 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.39 μm/s
QUICK SUMMARY:

H1's been locked 8.5+hrs.  The microseism which rose close to the 95th percentile in the last 24hrs looks like it's slowly decreasing over the last 6hrs (peaks still hitting the 95th.

On today's docket is a long Commissioning Down Time starting with Calibration in an hour at 1630utc/830amPT and a scheduled end at 2200utc/2pmPT.

TITLE: 01/30 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Currently relocking and at PREP_DC_READOUT_TRANSITION. Lockloss was due to a nearby earthquake, but luckily we didn't have to wait in DOWN for very long before we could start trying to relock.
LOG:

00:00 Relocking and at DHARD_WFS
00:27 NOMINAL_LOW_NOISE
00:30 Observing

04:55 Lockloss due to earthquake
    05:05 Started trying to relock, ran an initial alignment
 

Lockloss @ 01/30 04:55 UTC due to a nearby earthquake from Alaska. Holding in DOWN until the earth stops moving.

Currently Observing at 156Mpc and have been Locked for over 3.5 hours. Quiet evening, nothing to report.

TITLE: 01/29 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Had 2-locklosses this shift which were not trivial.  First lockloss had issues with ALS & Finding IR, but this was eventually was addressed with an Initial Alignment, but it still took about 2.5hrs to lock.  After the 2nd lockloss, ALSx had issues with its WFS not engaging (this happened for locking and a Manual Alignment), but when an Initial Alignment was run the ALSx WFS were fine.

EX HVAC continues to run with limited heater coils, but temperatures are OK, but if there is an issue, we should contact Tyler (he's not heard back from the vendor for purchasing more heater coils).
LOG:

• 1539-1620 MX parts search (eric)
• 1625-1637 Optics lab cleaning (kim)
• 16:41:44 - 16:41:46 Drop from Observing
  • Looks like accidental LOAD button push (according to ISC_LOCK log:  2025-01-29_16:41:44.344503Z ISC_LOCK system archive: code changes detected and committed
• 1722 Lockloss
  • Had issues with ALSx with repeated locklosses at LOCKING ALS (would also get a PDH error for ALSx).  Paused at LOCKING ARMS GREEN and then LOCKING ALS, and finally able to get past this.
  • ISS Adjustment (alog 82530):  During the pauses above, Jason came in to address the ISS Diffracted Power by increasing it from -1.90 to -1.88 (Jason ACCEPTED this in SDF).  Result is the low diffracted power increased from 2.8 to 4.0.
  • Then had issues with Finding IR.  ALS COMM was stuck in Fine Tuning (with the TRX_NORM value only making it to 0.6 which is low.  Tried moving the COMM OFFSET to find a better spot, but could not get above 0.6....eventually we got an "IR NOT FOUND", so at this point went for a Manual Alignment (skipping Green Arms which were good).
  • 1825-1845 Manual Initial Alignment
    • Input Align and PRC Align worked fine, but MICH Bright had issue (so it was skipped), and SRC also had issues.  Decided to run a full alignment and keep track of each step.
  • 1845-1915 Initial Alignment
    • Although the green arms looked good earlier, ALSX took quite a bit of time to offload (maybe due to temperature issue at EX?)....took about 15min to get through ALSx offloading
    • Rest of the alignment was totally fine!  So, operator error (me) was definitely the issue with the Manual Alignment above!
  • Locking Notes
    • Made it all the way to DRMI (for a lockloss), but got through the pesky spots earlier with ALSx & FIND IR
    • Sooooo----should have just run a full Initial Alignment from the beginning
    • Locking was fine all the way until Squeezing:  FC Alignment Tuning Needed
      • SQZ_FC was having trouble locking GR & Finding IR, so it was stuck in a loop.  
      • Luckily, Camilla was here, so I asked for help.  She went to the Troubleshooting SQZ wiki's Issues with SQZ_FC Guardian section.  Basically we needed to take SQZ_FC to DOWN, Close Input1, and manually lock the FC on Green (Camilla had the FCGS trans camera up and we saw that it was on the wrong mode and misaligned in pitch; as we watched it, it relocked on a 00 mode.  Now that we were on the right mode, we touched up FC2 (mostly with pitch).  Then took SQZ_FC to GR_LOCKED, and once green was locked, SQZ_MANAGER was taken to FREQ_DEP_SQZ.  Then that was it.
• 2025 Back to Observing
• 2031-2036 Odd noise shelf on H1!  Noticed noise on H1's DARM between 20-50Hz (stayed in observing during this noisy time).
• 2102-2244 ISS Array work in Optics Lab (keita,jennie, siva.myank)
• 2247 Lockloss
  • Several LOCKING ALS locklosses (but in hindsight noticed that ALSx did NOT have WFS engaged---it's power was at 1.0 or less vs the usual 1.2)
  • 2314 Manual Alignment, but ALSx for some reason was not engaging WFS! Sooooo, started.....
  • 2326 Initial Alignment started, and this time ALSx WFS engaged!  Frustrating :(
• 0030 Back to Observing!

TITLE: 01/30 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 0mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.37 μm/s
QUICK SUMMARY:

Currently relocking and at MOVE_SPOTS. Relocking has been going okay this time besides a bit of waiting at the beginning for ALS to behave and having a time where ALSX WFS didn't turn on because of it locking at the wrong mode.

FAMIS27807

No water was added, both levels looked to be at the top of their reseviours. All filters looked clean, and there was no water in the Dixie leak detection device.

Interestingly, water hasn't been added since Jan 7 according to the T2200289 sheet, but levels have stayed the same.

Closes FAMIS#28390, last checked 82163

Measurements analyzed for the data taken January 28th. Nothing looking too wild.

ITMX  ITMY  ETMX  ETMY

FAMIS26028

As noted in the last few checks, ITMX ST1 V1 and ITMY ST1 V2 seem to be higher than other dofs, and this time they are slightly above last week's check as well (alog82366).

Here're the bare-bones instructions to run the DARM loop critique -- an automated set of plots that were inspired by the presentations given over the years that compare the transfer functions of the DARM loop between the two sites, e.g. G1501372, G1700316, G2000149.

(0) Conda activate the latest pydarm environment.
    ~$ conda activate /ligo/groups/cal/conda/pydarm
This is a symbolic link to the latest tagged version of pydarm.
    () ~$ which pydarm
        /ligo/groups/cal/conda/pydarm/bin/pydarm
    () ~$ pydarm --version
        20240821.0
    () ~$ ipython
    In [1]: import pydarm
    In [2]: pydarm.__version__
    Out [2]: '20240821.0' 
Note the version of pydarm is the same on the command line and within the ipython session *because* we activated the correct pydarm conda environment. The command line pydarm internally activates this environment automatically, but any old ipython session may not have the right version of pydarm if you just import "from scratch" without making sure you're in the right environment first. So -- any time you're running script or python session pyDARM these days -- make sure that you've activated the conda environment.

Is this the right version? check https://git.ligo.org/Calibration/pydarm/-/tags see if that version is the latest, i.e. the top of the list.

It is. And this will *always* be true, by process of deploying the latest tag (see deploy script).
To compare previous versions of tags, go to https://git.ligo.org/Calibration/pydarm/-/compare?from=master&to=master and change the drop-down menu to compare one tag to the other.
If you want to activate an environment with an older version of pydarm, then head to the folder /ligo/groups/cal/conda/ and activate the environment you like.


(1) Grab the DARM loop model parameter sets that you want to plot and/or compare. If at LHO, wanting H1 parameter files, then (back out on the command line, not in yet in a python session)
Find the list of reports and tags:
   () ~$ pydarm ls -r
From that list, find the model parameters installed in the front-end:
   () ~$ pydarm ls -r | exported

Once you find what you like, go into that report directory, e.g.
   () ~$ cd /ligo/groups/cal/H1/reports/20240927T211612Z
Look for pydarm_H1.ini, and copy it somewhere you like, or at least store where it lives.

If you're at LHO, want L1 parameter files, then the easiest thing is to download it from the web. Head to the https://ldas-jobs.ligo-la.caltech.edu/~cal/ and scroll down to the list of all reports, and find the entry that's been exported most recently e.g. 20240408T200652Z, and download the pydarm_L1.ini and save it to a known location.

(2) Start critiquing:
~$ ipython
In [1]: from pydarm.darm import DARMModel

In [2]: d = DARMModel('/ligo/groups/cal/H1/reports/20240927T211612Z/pydarm_H1.ini')

# Plot a single parameter file's model:
In [3]: d.plot(filename='/ligo/home/jeffrey.kissel/2025-01-21/20240927T211612Z_pydarm_H1_critique.pdf',label=['H1'])

# Compare against another, say, previous version of the model
d_prenewdarm = DARMModel('/ligo/groups/cal/H1/reports/20231027T203619Z/pydarm_H1.ini')

from pydarm.plot import critique

critique(d,d_prenewdarm,filename='/ligo/home/jeffrey.kissel/2025-01-21/20240927T211612Z_vs_20231027T203619Z_pydarm_H1_critique.pdf',label=['H1 20240927T211612Z', 'H1 20231027T203619Z'])

# Compare two IFOs:
In [9]: d_H1 = DARMModel('/ligo/groups/cal/H1/reports/20240927T211612Z/pydarm_H1.ini')

In [10]: d_L1 = DARMModel('/ligo/home/jeffrey.kissel/2025-01-21/20240408T200652Z_pydarm_L1.ini')

critique(d_H1,d_L1,filename='/ligo/home/jeffrey.kissel/2025-01-21/20240927T211612Z_H1_vs_20240408T200652Z_L1_critique.pdf',label=['H1 20240927T211612Z','L1 20240408T200652Z'])

# Compare one IFO's parameters, while updating one of the parameters on the fly
In [9]: d_H1 = DARMModel('/ligo/groups/cal/H1/reports/20240927T211612Z/pydarm_H1.ini')
In [10]: d_H1_moreAA = DARMModel('/ligo/groups/cal/H1/reports/20240927T211612Z/pydarm_H1.ini') #Intentionally the same
# Update the parameter you want,
In [6]: d_H1_moreAA.sensing.omc_filter_noncompensating_modules
Out[6]: [[9, 10], [9, 10]]

In [7]: d_H1_moreAA.sensing.omc_filter_noncompensating_modules = [[9,10,10],[9,10,10]]

In [8]: critique(d_H1,d_H1_moreAA,filename='/ligo/home/jeffrey.kissel/2025-01-21/20240927T211612Z_H1_vs_20240927T211612Z_H1_2x16kDigitalAA_critique.pdf',label=['Nominal','1x More 16k AA'])