TITLE: 05/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Straightforward shift with about half of it for Commissioning, Calibration measurement, and a relock. The relock was mostly automated but ALSx did start with low power (0.45) again.
LOG:
TITLE: 05/15 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 17mph Gusts, 12mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY: Locked for 6 hours, calm environment at the moment.
After coordinating with LLO & notifying Virgo, went with running the Wednesday Calibration Measurements (broadband [~5min] + simullines [~23min]) at ~ 21:10UTC.
Logistical Notes In Intersite Coordinating: At 2007utc (107pmPDT) contacted LLO Control Room via Teamspeak and JoeB/Anamaria wanted another hour so they could also have atleast 3hrs of thermalization. So will connect with LLO at 2110utc to coordinate our down time for our Wednesday calibration measurement. Then contacted the Virgo control room via teamspeak to give them a heads up for possible down time at 2110utc.
Measurement NOTES:
[Sheila, Jenne]
We did a first quick test of moving the spot on PR2 during our commssioning time this morning. Our biggest conclusion is that 'wow, we need to move a lot if we're going to center on PR2'. Since it was late in the commissioning window, and I had already broken lock once today when shaking HAM3 (alog 77851), we didn't shake HAM3 while doing these moves. That's something that we'd like to do at some point, to hopefully see that the effect in DARM is lower when the spot on PR2 is closer to center.
Sheila manual-ed the ISC_LOCK guardian to the PR2_spot_move state. This state watches how much PR3's slider moves, and moves the PRM and PR2 sliders to compensate that move. In the first attachment of the slider values for the 3 PRC optics, you can see that PRM and PR2 sliders are following along when Sheila moves the PR3 slider. We didn't see very much response in the ASC loops when we made a step, which means that these 'following along' scales for the PRM and PR2 sliders are still quite good, even though we haven't used this guardian state in several years. First we went a small amount one way, then we went a larger amount the other direction in yaw.
The second attachment is the top mass OSEM witness of the moves, and the third attachment is our cabity buildups. The x-axes of all these plots / screenshots are set to be the same. The bigger yaw movement (almost 3.6 urad in PR3 yaw) a little after -1h clearly shows a bump up in arm circulating power, that then goes away when PR3 is moved back to its nominal position. This bump is clear in the arm circulating powers, even though the IFO was still thermalizing. Interestingly, I don't see a similar bump in POP_LF, the amount of power circulating in the PRC.
While PR3 was at it's extremal yaw position for today, I did a rough Y2L optimization for PR2 with step sizes of 0.05, and found that a Y2L value of -7.40 was about the best I could do to minimize the peak (30 Hz, 1 ct using the ADS oscillator) in PRCL_OUT. After Sheila put PR3 back to its nominal position, I re-checked, and found a Y2L value of -7.50 was the best. This means that we moved the spot on PR2 by about 0.2 mm (out of the 15 mm we think we need to move) closer to center, when we changed the PR3 yaw alignment by 3.5 urad. I'll note that I did not have the 30 Hz notches in the quads' ISCINF pit and yaw filter banks engaged, but I'm not fully sure that those are helpful here (if they are important, we should add them to all of the other optics, not just the quads).
Just as a double check of whether we really should need to move PR3 that far: If I assume the distance between PR2 and PR3 is 1/3 of the PRC length 55m, my lever arm for a very naiive spot movement calculation is about 18m. At 18 meters away, a 3.5 urad angle change will move a beam 6.3e-5 m, or 0.06 mm. So, this very naiive estimate gives a smaller beam spot motion on PR2 for a given PR3 move than we measure using A2L, but it confirms that indeed we probably didn't make a very dramatic move on PR2 today.
H1 just completed a block of Commissioning time and is back to Observing. H1 is currently about 2hrs into thermalizing, so may try to coordinate a Calibration break with LLO (& give a heads up to Virgo).
Wed May 15 10:14:42 2024 INFO: Fill completed in 14min 38secs
Gerardo confirmed a good fill curbside.
I was working on shaking the HAM3 ISI to see the effect of potential clipping on the PR2 scraper baffle (with the idea that we were then going to move the spot on PR2 and see how DARM changed), but I was saturating the H3 actuator and the ISI's watchdog timed out and tripped off.
I had just increased the excitation by a factor of 2, to 10 counts going to H1:ISI-HAM3_ISO_Y_EXC, and that last factor of 2 is what started saturating the actuator. Since we were able to see some subtle effects in DARM with 5 counts, we'll try using that when we next get locked. We may be interested in a conversation with SEI folks about whether it is safe to override the actuator saturation watchdog during this type of test, in order to more clearly see the effect in DARM, but we'll save that for another day.
Sheila pointed out that it would be useful if verbal alarms would tell us when we are saturating a seismic actuator (similar to how it tells us if we are saturating a suspension).
Attached are screenshots of the amount of motion above ambient, as well as that this last factor of 2 increase in actuation is what caused the saturation monitor to start accumulating, as well as of the excitation settings. This DTT template is a copy of what was in the Noise Budget git space for HAM5, with the exception that the noise budget excitation value is 0.6 counts, and I wasn't really seeing an effect in DARM until I got to 5 counts.
Here's also the HAM3 watchdog plot, again showing that it was my actuation that caused the trip.
There is also the suspoint drive infrastructure that we've added to all of the ISI models, allowing you to drive the euler basis motion for a particular suspensions top stage suspension point. Not sure if that will help for this measurement or not. For each ISI there are filter modules called ISI-CHAMBER_SUSPOINT_DRIVE_L/T/V/R/P/Y, giving the necessary testpoints, EXC channels for those fms are stored in the daq at 2048. You will need to populate the downstream eul2cart epics matrix to get the correct translation to the ISI cartesian drives. Output from the eul2cart matrix is then summed into the error point of the cart basis isolation loops. The matl code for writing the coefficients is really simple, for PR2, on HAM3 it would be:
addpath /ligo/svncommon/SeiSVN/seismic/Common/MatlabTools/
cd /opt/rtcds/userapps/release/isc/common/projections
load('ISI2SUS_projection_file.mat')
sus={'pr2'}
for ii =1:length(sus)
fill_matrix_values(['H1:ISI-', upper(ISI2SUSprojections.h1.(sus{ii}).chamber), '_SUSPOINT_EUL2CART'],ISI2SUSprojections.h1.(sus{ii}).EUL2CART)
pause(.1)
end
This might fail on a couple of the coefficients, so it might be a good idea to run a couple times. Also, there's only 1 6-dof matrix per ISI, so if drives on multiple suspensions are needed on one table, you will need to populate the matrix for each suspension. Probably also best to zero out all of the matrix elements first, then write with the above code.
TITLE: 05/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 9mph Gusts, 6mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
Walked in to h1 locking PRMI (there was a lockloss 25min earlier (at 1405utc).
I believe Commissioning is in the morning today (along with a calibration measurement), but H1 will be thermalizing the next few hours.
Green arm x power is looking back to normal-ish with power closer to 1.0.
(Also there was box with a bat in it outside the entry to the Control Room.)
TITLE: 05/15 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: One lock loss with an easy relock. On the first lock I had to step out of Observing to do a sqz scan, this helped our range. Currently locked for 2.5 hours.
LOG:
Seemed very sudden, there was only a very minor wiggle in DARM msec before the lockloss.
Observing 0528 UTC.
I had no issues with ALSX power, it got up near 1 almost immediately. ALSY needed ETMY to be adjusted by 0.1urads for it to catch even though it had flashes near one...annoying. Other than that it was all auto.
RickS, FranciscoL
On Tuesday, May 14, we moved the pcal inner beam by 5 mm on the Rx sensor at X-End. This is the start of an investigation on potential sources of systematic variations to the pcal system.
Our procedure and notes are the following:
We expect this procedure to reflect the calculations done in T2400032 which depend on the position of the IFO beam and the pcal beams on the ETM. With this movement, and following the parameters from the technical note, we are expecting to see a change in the XY ratio of +19 HOPs (after - before). This procedure will be iterating in the following weeks, making a series of movements of the inner beam, with reports on the value obtained after making a beam movement.
0313-0321 UTC
Our range was around 135Mpc after the squeezer relocked itself at 0151UTC, and the SQZ FOM didn't look great. I stepped out of Observing to run SCAN_ALIGNMENT_FDS and SCAN_SQZANG before returning to Observing. We are currently at ~151Mpc, so it seemed well worth the 8 minutes.
FAMIS28353
ITMs look consistent in April, but ETMY looks to have changed since the April 30th measurement. I'd guess that this is due to Robert and Anamaria's changes to the ESD bias on May 5&7th (alog77633).
TITLE: 05/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Calibration
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
A light Mainteance day made for a nice & fairly quick return to observing (but our low range of 150Mpc continues---Sheila has a new tool to check on low range in this wiki LINK).
X-arm for ALS had low powers (0.65) after an alignment (which is low), but we made all the way back to NLN. (this was observed last night by Oli & Ibrahim, btw)
LOG:
After Maintenance Day today, I did my first LVEA Sweep of O4 (at about 1140PDT). There were a few items which came up as I swept:
"Confirm no mechanical shorts onto HEPI."
"Cranes in their "parking spots"
"Unplug unused power supplies/extension cords"
At any rate, these were items noticed during my LVEA sweep. I did not change ANYTHING (above) mainly because I had not done a sweep in ages, and perhaps these are things we are "OK" with. At any rate, just wanted to share observations from an old operator. :)
TITLE: 05/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY: Locked for 3 hours, low ALSX arm power for the last day has caused some locking issues. I'll be on the lookout for this.
Addressed TCS Chillers (Tues [May14] 1340-1350pm local) & CLOSED FAMIS #27789: