Displaying reports 2901-2920 of 83069.Go to page Start 142 143 144 145 146 147 148 149 150 End
Reports until 12:50, Thursday 30 January 2025
H1 ISC
jim.warner@LIGO.ORG - posted 12:50, Thursday 30 January 2025 - last comment - 14:02, Thursday 30 January 2025(82552)
ETMX glitch whiten/dewhiten filters turned on, still need to figure limit threshold out

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.

Comments related to this report
corey.gray@LIGO.ORG - 14:02, Thursday 30 January 2025 (82553)ISC, SEI, SUS

Here are the SUSETMx SDF diffs ACCEPTED from Jim's work noted above.

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 10:11, Thursday 30 January 2025 (82549)
Thu CP1 Fill

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

Images attached to this report
H1 General
corey.gray@LIGO.ORG - posted 08:39, Thursday 30 January 2025 - last comment - 11:23, Thursday 30 January 2025(82548)
ALSx Trigger Issues Again With No WFS

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: 

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).

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 11:23, Thursday 30 January 2025 (82551)OpsInfo

Attached is an ndscope snapshot Ryan C. took from this morning where one can see the ITMx Camera is off in pitch and yaw and No WFS engaged for ALSx, but as soon as the Force button (H1:ALS-X_WFS_AUTOC_TRIG_FORCE) is pressed, ALSx WFS are engaged and aligment is optimized for the X-arm.  

Ryan  S. / Ryan C. also saw this ALSx beahvior over the weekend as well (alog 82464).

Images attached to this comment
H1 AOS
corey.gray@LIGO.ORG - posted 08:14, Thursday 30 January 2025 (82547)
H1 Loses Lock 25min Before Commissioning/Calibrtion Start Time At 830am local

H1 just lost lock before Commissioning Time (1422288412).

LHO General
corey.gray@LIGO.ORG - posted 07:37, Thursday 30 January 2025 (82544)
Thurs DAY Ops Transition

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.

H1 General
oli.patane@LIGO.ORG - posted 22:02, Wednesday 29 January 2025 (82543)
Ops Eve Shift End

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
 

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 20:57, Wednesday 29 January 2025 (82542)
Lockloss

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

H1 General
oli.patane@LIGO.ORG - posted 20:04, Wednesday 29 January 2025 (82541)
Ops EVE Midshift Status

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

LHO General
corey.gray@LIGO.ORG - posted 16:34, Wednesday 29 January 2025 (82524)
Wed DAY Ops Summary

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:

H1 General
oli.patane@LIGO.ORG - posted 16:17, Wednesday 29 January 2025 - last comment - 16:32, Wednesday 29 January 2025(82539)
Ops Eve Shift Start

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.

Comments related to this report
oli.patane@LIGO.ORG - 16:32, Wednesday 29 January 2025 (82540)

00:30 UTC Observing

H1 TCS
thomas.shaffer@LIGO.ORG - posted 14:48, Wednesday 29 January 2025 (82538)
TCS Chiller Water Level Top Off - Biweekly

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.

H1 SUS
oli.patane@LIGO.ORG - posted 14:24, Wednesday 29 January 2025 (82537)
In-Lock SUS Charge Measurements FAMIS

Closes FAMIS#28390, last checked 82163

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

ITMX  ITMY  ETMX  ETMY

Images attached to this report
H1 SEI
thomas.shaffer@LIGO.ORG - posted 14:14, Wednesday 29 January 2025 (82536)
H1 ISI CPS Noise Spectra Check - Weekly

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).

Non-image files attached to this report
H1 General
corey.gray@LIGO.ORG - posted 11:38, Wednesday 29 January 2025 (82533)
Lockloss at 1722utc

Lockloss (ETMx Glitch tag) at 1722utc.

Relocking was not trivial.  Had issues with consecutive LOCKING ALS locklosses (pauses appeared to help), but then had ALS COMM Fine Tuning issues where TRX could not get above 0.6 (which is too low).  Ultimately, a full Initial Alignment did the trick.  Now finally getting ready to power up H1.  It's been over 2hrs so far and hope to make it back up within 45min.

H1 General (Lockloss, SEI)
ryan.crouch@LIGO.ORG - posted 18:10, Sunday 26 January 2025 - last comment - 11:52, Wednesday 29 January 2025(82476)
2025-01-26 11:42 UTC Lockloss

Lockloss tool tags anthropogenetic, there was a ground motion spike in the 0.3 - 1.0 band that matches up to the lockloss. We lose lock right around the CS_Z motions peak.

Images attached to this report
Comments related to this report
ryan.crouch@LIGO.ORG - 11:52, Wednesday 29 January 2025 (82534)PEM

Tagging PEM

H1 ISC (CAL, ISC)
jeffrey.kissel@LIGO.ORG - posted 15:33, Tuesday 21 January 2025 - last comment - 14:01, Thursday 30 January 2025(82387)
Creating DARM Loop Critique via pydarm on the Control Room Machines
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'])

Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 10:35, Thursday 30 January 2025 (82550)CAL
For the record, this DARM model object, "d" mentioned above literally contains everything about the DARM loop. 

So if you want parts of the DARM loop, then you can ask for things like
    $ conda activate /ligo/groups/cal/conda/pydarm
    $ ipython

    : import pydarm
    : pydarm.__version__
         '20240821.0'
    : from pydarm.darm import DARMModel   
    : d = DARMModel('/ligo/groups/cal/H1/reports/20240927T211612Z/pydarm_H1.ini') 
    : import numpy as np
    : freq = np.logspace(1,6,2500)
    : G = d.compute_darm_olg(freq)              # Open Loop Gain == G = A*C*D
    : R = d.compute_response_function(freq)     # Response Function == (1+G)/C = (1/C) + D*[A_T + A_P + A_U]
    : C = d.sensing.compute_sensing(freq)       # Sensing Function, C
    : D = d.digital.compute_response(freq)      # DARM filter bank, D
    : A = d.actuation.compute_actuation(freq)   # Total super actuator, A

And if you need more compartmentalized transfer functions, you can explore the methods available in
darm.py (for things like the overall loop shape)
sensing.py (for detailed components of the sensing function)
actuation.py (for detailed components of the actuation function)
jameson.rollins@LIGO.ORG - 14:01, Thursday 30 January 2025 (82554)

Fwiw the "pydarm model" command on the command line will also produce frequency response plots of these DARM model transfer functions.

H1 CAL (Laser Safety)
anthony.sanchez@LIGO.ORG - posted 10:29, Friday 22 November 2024 - last comment - 11:08, Wednesday 29 January 2025(81416)
PCAL Lab LASER Powered OFF for Ceiling light fixture replacement

On Tuesday NOV 19th Eric started the replacement of the ceilign light fixtures in the PCAL Lab.
Francisco and I grabbed 3 HAM Door covers to stretch out over the PCAL table to minimize dust particles on the PCAL optical bench.
I also put all the Spheres away in the cabinet and made sure that they all had their apature covers on.
I went in to shutter the laser using the internal PCAL TX module shutter, and the shutter stopped working.
I then just powered off the laser, removed the shutter, and repaired the shutter in the EE lab.
Put in an FRS ticket: https://services1.ligo-la.caltech.edu/FRS/show_bug.cgi?id=31730
The Shutter is repaired and just waiting for the FAC team to finish the Light fixture replacement to reinstall.

Update: Friday NOV 22nd, there are 2 more light fixtures in the PCAL LAB that need to be replaced. One directly above the PCAL Optics table.
PCAL Laser Remains turned off with the key out. 
 

Comments related to this report
anthony.sanchez@LIGO.ORG - 11:08, Wednesday 29 January 2025 (82531)

Since this event the Lab shutter from inside the Tx module hasn't been reading back correctly. Today Fil and I figured out why after replacing the switching regulator LM22676.

There is a reed switch Meder 5-B C9 on the bottom of the PCB that gets switched on via a magnet mounted on the side of the shutter door.
One of these reed switches is stuck in the "closed" position, which leaves the OPEN readback LED on all the time. Parts incoming.

 

Displaying reports 2901-2920 of 83069.Go to page Start 142 143 144 145 146 147 148 149 150 End