Displaying reports 1561-1580 of 83205.Go to page Start 75 76 77 78 79 80 81 82 83 End
Reports until 17:15, Tuesday 22 April 2025
H1 PSL (PSL)
keita.kawabe@LIGO.ORG - posted 17:15, Tuesday 22 April 2025 - last comment - 17:15, Tuesday 22 April 2025(84044)
Change in PSLFSS and PSLPMC (Keita, Dave)

WP 12463: This will close this FRS: https://services1.ligo-la.caltech.edu/FRS/show_bug.cgi?id=5861

We changed PSLFSS and PSLPMC model and related MEDM screens and confirmed that the PMC and FSS relocked right away before RyanS started his work in the PSL room. Guardian was modified to accomodate this. Safe SDF for PMC and FSS were updated.

(FYI, the motivation for this ancient ticket was to kill the habit of using arbitrary number for ON/OFF status, which was really bad in all PSL models. Depending on who wrote what, sometimes 1 means ON, sometimes -1, some other times -30000, and these status were cdsEpicsInput which are floating point. Now they're cdsEpicsBinIn, which is binary, ON is 1, OFF is 0.)

Model changes:

I pulled pslfss and pslpmc model from svn to close the FRS above. We'll have to keep some local modifications unique to LHO at least until the end of the run. Due to local changes, the models will not be committed to SVN upstream.

Changed models: ${userapps}/release/psl/common/models/pslfss.mdl, ${userapps}/release/psl/common/models/pslpmc.adl, ${userapps}/release/psl/h1/models/h1pslfss.mdl.

See the first two screen shots.

Local modifications 1: Adding back CALI filters.

These filters are not used any more from this point on. However, removing these from DAQ means that we cannot trend the data of these back without using NDS2 and specifying epoch, which is not a great thing to do in the middle of the run.

  1. Added back PSL-FSS_TEST1_ON_CALI and PSL_FSS_TEST2_ON_CALI filters to pslfss common model, but grounded all of them.
  2. Added back PSL-PMC_TF_IN_ON_CALI, PSL-PMC_LOCK_ON_CALI, RAMP_ON_CALI, BLANKING_CALI, BOOST_CALI filters to pslpmc common model, but grounded all of them.

See the first and second screen shot (red in the left panel).

Local modifications 2: Move NPRO_TEMP_OUT out of the common model and into the H1 model.

Dave originally added NPRO_TEMP_OUT channel to DAQ at 256Hz locally to the common FSS model in May 2023. However, he moved it to h1pslfss.

Local modifications 3: Don't change binary to DAC count and convert it back to binary

There was such a block in the common PMC model in the SVN (1st screen shot, right panel, green), which was eliminated in the local common model for the sake of simplicity.

Local modifications 4 (cosmetic): Define a constant representing DAC count that will produce +10V in the model.

Blue in the first two screen shots.

Dave thinks that this needs to be in the top level of local models (not in the common model) right before the signal goes to DAC in the future. That way, when we upgrade the DAC we can just change the constant.

MEDM changes:

Manually changed: ${userapps}/release/psl/common/medm/PSL_PMC.adl as the file on SVN still uses the old logic.

Pulled from SVN: ${userapps}/release/psl/common/medm/PSL_FSS.adl and ${userapps}/release/psl/common/medm/FSS/MAN.adl (and other things in FSS directory).

Guardian changes:

In isc_library.py,
L200    if ezca['PSL-PMC_LOCK_ON'] != -30000:
was changed to
L200    if ezca['PSL-PMC_LOCK_ON'] == 0:

In LASER_POWER.py,
L157            elif self.timer['wait_for_busy'] and ezca['PSL-ROTATIONSTAGE_STATE_BUSY'] == 0 and ezca['PSL-PMC_LOCK_ON'] == -30000:
L161            elif self.timer['wait_for_busy'] and ezca['PSL-ROTATIONSTAGE_STATE_BUSY'] == 1 and ezca['PSL-PMC_LOCK_ON'] == -30000:
were changed to
L157            elif self.timer['wait_for_busy'] and ezca['PSL-ROTATIONSTAGE_STATE_BUSY'] == 0 and ezca['PSL-PMC_LOCK_ON'] == 1:
L161            elif self.timer['wait_for_busy'] and ezca['PSL-ROTATIONSTAGE_STATE_BUSY'] == 1 and ezca['PSL-PMC_LOCK_ON'] == 1:
 

SDF changes:

See screen shots 3 and 4. (You can see that the old setpoints were float and the new setpoints are binary.)

It's not shown in the last screen shot but I accepted H1:PSL-FSS_AUTOLOCK_ON in the afternoon after RyanS locked the FSS again.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 14:54, Tuesday 22 April 2025 (84064)

Caution about trending logic channels I changed today.

H1:PSL-PMC_LOCK_ON, H1:PSL-PMC_TF_IN_ON, H1:PSL-PMC_RAMP_ONI, H1:PSL-PMC_ALIGNRAMP_ON, H1:PSL-PMC_BOOST, H1:PSL-PMC_BLANKING, H1:PSL-FSS_AUTOLOCK_ON, H1:PSL-FSS_TEST1_ON, H1:PSL-FSS_TEMP_LOOP_ON_REQUEST

For these channels, 0 (zero) means OFF, and non-zero means ON. This doesn't change. It's just that many numbers like -1 and 1 and -30000 used to be used as "non-zero" depending on who wrote what,  but from this point "non-zero" can only mean 1.

However, due to the change from float to integer, if you trend these channels, non-zero value for the data older than 10AM-ish Pacific on Apr/22/2025 is not displayed correctly. Fortunately zero is still zero (Jonathan confirmed), so if you trend the data to see if something was ON, check that the channel was not zero, i.e. H1:PMC-TF_IN_ON != 0 rather than H1:PMC-TF_IN_ON == -30000.

H1:PSL-FSS_TEST2_ON

Semantics of this signal changed. It used to be that ON=0 (zero) and OFF=1 to compensate the inverted logic in the hardware, but now ON=1, OFF=0 as the logic inversion is in the model.

The same caveat about float to integer applies. If you want to trend this channel, check H1:PSL-FSS_TEST2_ON ~=0 rather than H1:PSL-FSS_TEST2_ON == 1, and then you have to be aware that H1:PSL-FSS_TEST2_ON ~=0 means OFF for data older than 10AM-ish Pacific on Apr/22/2025, but the same thing means ON for newer data.

H1 ISC
daniel.sigg@LIGO.ORG - posted 15:05, Tuesday 22 April 2025 - last comment - 14:05, Wednesday 23 April 2025(84065)
Issue with ISC_RF25-B/3

Marc Daniel

One of the coax cables shows a discontinuity at the feedthrough, ISC_RF25-B/3. This is the coax for ASC-REFL_B 9MHz chn 4 (Q4 RF Low). This is feedthrough D1-1D1. We can see the signal going though the pig-tail but terminating at the feedthrough. This could be an issue of the in-air pig-tail or the in-vac cable at the  feedthrough side.


Typical In-vacuum RFPD ASC Wiring Chain for aLIGO: https://dcc.ligo.org/LIGO-D1300467
O5 ISC/SQZ Wiring Diagram: https://dcc.ligo.org/LIGO-D1900511

Comments related to this report
marc.pirello@LIGO.ORG - 15:36, Tuesday 22 April 2025 (84067)

TDR Plot of the cables analyzed.

Images attached to this comment
filiberto.clara@LIGO.ORG - 14:05, Wednesday 23 April 2025 (84091)

Found faulty pin on one of the Accu-Glass 5-way coaxial pigtails. Pin 3 seems to have been improperly crimped/seated/damaged. See attached picture. The Pigtail cable was replaced. Initial testing shows all pins are now correct lengths. The cable with issue was ISC-RF25-B/3.

Images attached to this comment
H1 PSL
ryan.short@LIGO.ORG - posted 14:48, Tuesday 22 April 2025 (84063)
PSL PMC and RefCav Alignment Tweaks

Now that we have restored PSL picomotor functionality by moving them to their own driver, I took the time this afternoon to touch up alignment into the PMC and RefCav as they had been declining. For the PMC, with the ISS off, my adjustments went as follows:

It's possible there's still more pitch adjustment that could be tried here as seen by the PMC REFL camera, but I was no longer seeing improvement while doing my adjustments.

After turning the ISS back on and ensuring it was diffracting about 4%, my RefCav adjustment followed:

Decent improvements all around. I've attached a snapshot of the quad display for reference after my alignment was complete.

Images attached to this report
LHO VE
jordan.vanosky@LIGO.ORG - posted 13:36, Tuesday 22 April 2025 (84061)
Morning Purge Air Checks 4-22-25

Morning dry air skid checks, water pump, kobelco, drying towers all nominal.

Dew point measurement at HAM1 , approx. -44C

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 13:21, Tuesday 22 April 2025 (84060)
PM1 suspension added the HAM1 Software Watchdog

WP12466

Dave:

A new h1iopsush2b model was installed which added a PM1 OSEM + DACKILL parts and AND'ed their output to those of RM1 and RM2 to form the HAM1 SWWD IPC.

Model changes and new MEDMs are shown below.

Note that this is the first instance of a 3-SUS SWWD, so a new common medm was needed.

Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 12:00, Tuesday 22 April 2025 (84055)
New JAC EPICS channels, will defer adding these to the DAQ

Daniel, Dave:

Daniel has added JAC channels to the ISC-CS slow controls Beckhoff PLC. H1EPICS_ECATISCCS.ini has new H1:JAC channels, these are listed below.

We have decided at this stage to not add these to the DAQ today, we will defer this until the next maintenance period.

+[H1:JAC-ERROR_CODE]
+[H1:JAC-ERROR_FLAG]
+[H1:JAC-REFL_A_DEMOD_DEMODULATORTYPE]
+[H1:JAC-REFL_A_DEMOD_ERROR_CODE]
+[H1:JAC-REFL_A_DEMOD_ERROR_FLAG]
+[H1:JAC-REFL_A_DEMOD_LOMON]
+[H1:JAC-REFL_A_DEMOD_LONOM]
+[H1:JAC-REFL_A_DEMOD_POWEROK]
+[H1:JAC-REFL_A_DEMOD_RFMAX]
+[H1:JAC-REFL_A_DEMOD_RFMON]
+[H1:JAC-REFL_A_DEMOD_SIGN]
+[H1:JAC-REFL_A_DEMOD_SIGNNOM]
+[H1:JAC-REFL_A_ERROR_CODE]
+[H1:JAC-REFL_A_ERROR_FLAG]
+[H1:JAC-REFL_A_PHASE_DELAYNS]
+[H1:JAC-REFL_A_PHASE_DELAYSTEP]
+[H1:JAC-REFL_A_PHASE_ERROR_CODE]
+[H1:JAC-REFL_A_PHASE_ERROR_FLAG]
+[H1:JAC-REFL_A_PHASE_FREQMHZ]
+[H1:JAC-REFL_A_PHASE_PHASEDEG]
 

LHO FMCS
eric.otterman@LIGO.ORG - posted 11:55, Tuesday 22 April 2025 (84054)
Air handler bearing lubrication and alternation
We lubricated the fan bearings in all the air handlers and switched the lead/lag units. 
H1 CDS (AOS)
david.barker@LIGO.ORG - posted 11:41, Tuesday 22 April 2025 (84052)
Stray light ETMX baffle photodetectors back online following 6th April power outage

WP12479 Fil, Dave:

Fil has fixed the missing slow controls Beckhoff terminals at EX which were lost after the site power outage Sun 6th April 2025 18:05 PDT.

Attached 18 day trend of the baffle PD signals show the loss and restoration of signal.

The CDS overview had been expecting only 125 of 127 terminals, and was displaying the degraded DEV4 in dark green, turning to red now all 127 terminals are back. I have removed this exception, DEV4 is now nominal green when new overviews are opened.

Tagging AOS.

Images attached to this report
H1 DAQ
daniel.sigg@LIGO.ORG - posted 11:35, Tuesday 22 April 2025 (84051)
Slow Controls Update

The TwinCAT slow controls software was updated to incorporate LSC-REFL_B. This includes controls and readbacks for a new demod chassis and a new delay line.

H1 AOS (SEI)
jason.oberling@LIGO.ORG - posted 11:29, Tuesday 22 April 2025 (84049)
Another Look at WHAM1 ISI Alignment

J. Oberling, J. Warner

After letting things settle overnight we took another look at the WHAM1 ISI alignment this morning.  Jim found that a few of the HEPI stops had become engaged (likely during the final moves yesterday afternoon), so he backed those off and I took a look at ISI alignment.  Again, the ISI position is reported as deviation from its nominal LHO global coordinates of [-22726.7, 0.0, -201.9] mm.

Jim said this was good enough to begin attaching HEPI actuators, so that work has begun.  We'll take another look at ISI alignment once the actuators are attached.

Data

Data for the above alignment deviations.  Method described in alog 84057.

X axis position and yaw:

Y axis position:

Z axis position and level:

 

H1 CDS
david.barker@LIGO.ORG - posted 11:24, Tuesday 22 April 2025 (84050)
Alarms configured to expect GV2 to be open

Gerardo, Dave:

GV2 was transitioned from closed to open. I have reconfigured alarms to expect this gatevalve to be fully open and alarm if not.

H1 ISC
camilla.compton@LIGO.ORG - posted 10:55, Tuesday 22 April 2025 - last comment - 15:33, Tuesday 22 April 2025(84048)
All ISC components ready to go back onto HAM1

Camilla, Jennie W

Finished getting all the ISC components ready to go back onto HAM1, previous alogs 839458387583858.

Last steps were to replace all remaining black glass v-shaped beam dumps with DLC coated SS (Alena sent us more D1800140-v1-01/02). This was 6 beamdumps: BD1, BD6a, BD11, BD13, BD14 and BD16. The glass was very tightly wedged into BD6a, so I removed the hole v-holder and swapped with a new one. 

Both the lower and upper periscope mirror were dusty, the LPM in particular (photo), so we pulled those out, top-gunned and first contacted. Both were labeled E1000425-v3.
When we went to replace them, we noticed v. small shards of black glass by the UPM. I decided to replace the black glass with the piece removed from M15 to avoid any shards dropping onto the LPM. When I removed the black glass beam dump you could see it was broken at the bottom with a piece still in the clip holder (photo), maybe from over-tightened metal screws.

Now everything is ready, on the rack in the HAM3 cleanroom.

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 15:33, Tuesday 22 April 2025 (84066)EPO

tagging EPO

H1 CDS
erik.vonreis@LIGO.ORG - posted 10:37, Tuesday 22 April 2025 - last comment - 12:07, Tuesday 22 April 2025(84047)
Bootserver puppet update to re-order models.

I ran the bootserver puppet on h1vmboot1 to reorder the models on h1seih16.  The puppet module was updated to the latest from gitlab.

Comments related to this report
david.barker@LIGO.ORG - 12:07, Tuesday 22 April 2025 (84056)

The model ordering for seih16 was inconsistent with seih23 and seih45. The the latter the order is both-HEPI followed by both-ISI. h1seih16 on the other hand was using a HAM1 (HEPI+ISI) followed by HAM6 (HEPI+ISI) scheme. These are both good schemes, but for consistency we have made h16 the same as the others.

Note that the order of the models on the CDS overview is the order in which the models are started when the front end is restarted. If you are interested, the order is defined in /opt/rtcds/lho/h1/cds/H1.yaml

Images attached to this comment
H1 CDS (PSL)
filiberto.clara@LIGO.ORG - posted 10:18, Tuesday 22 April 2025 - last comment - 13:53, Tuesday 22 April 2025(84045)
PSL Picomotors Controls

WP 12480
FRS 6499

The PSL picomotor controls have been moved from the ISC Driver to the PSL Driver installed in the PSL-R2 Rack (alog 63613, alog 62830). The new DB25 cable is routed from behind the PSL field rack into the enclosure. The old controls cable was pulled out of the enclosure and will be reused for HAM1/JAC. Ryan Short is testing picomotors are operational through MEDM.

F. Clara, R. McCarthy, R. Short

Comments related to this report
ryan.short@LIGO.ORG - 13:53, Tuesday 22 April 2025 (84062)PSL

I moved the picomotor breakout box (D1101691-v1) from its previous location on top of the water pipes between the PSL table and the north wall of the enclosure (first picture) to underneath the center of the table (second picture) to accommodate the new DB25 cable coming from the west wall out to the PSL racks. New cable was routed through the floor cable manager and DB9 cables up to the table were coiled under the table to account for extra length. Cable routing from the breakout box up to and on the PSL table are unchanged.

I also tested all eight picomotors (four for the two mirrors for PMC steering, four for the two mirrors for RefCav steering) and all are working well and as expected.

Images attached to this comment
H1 AOS
jason.oberling@LIGO.ORG - posted 17:49, Monday 21 April 2025 - last comment - 12:09, Tuesday 22 April 2025(84039)
IAS First Look at WHAM1 ISI

R. Crouch, J. Warner, J. Oberling

We took a first look at the alignment of the WHAM1 ISI today.  Quick alog with results, I'll add details as a comment tomorrow.

Nominal position of the WHAM1 ISI is, in LHO global coordinates, [-22726.7, 0.0, -201.9] mm.  I post the results as deviations from these nominal positions.

Initial:

After a few rounds of adjustments, the final measurements for the day:

Will let things settle overnight and take a full round of measurements in the morning, including another look at y-axis position (since we didn't get a final measurement on that).  Will do any further adjustments at that point.

The IAS survey equipment is still set up on the -Y side of WHAM1 (East if going by crane directions).  Please do not disturb this equipment!

Edit 4/22/2025: Had the wrong yaw direction for the final set of measurements, should be CCW.  Also had the wrong z-axis deviation for the final set of measurements, should be +0.69 mm.

Comments related to this report
jason.oberling@LIGO.ORG - 12:09, Tuesday 22 April 2025 (84057)

Details and Methodology

Since the FARO decided it needed a Florida vacation we have to use the same alignment method employed during aLIGO install.  This is done using a total station for measuring X and Y axis position and ISI yaw, and an autolevel for measuring ISI height and level.

X Axis Position and Yaw

2 sets of crossed scales are used with the total station to make the required measurements.  These scales are mounted in such a way that one edge of the vertical scale lines up with the y-axis centerline of the ISI; a second scale is mounted horizontally to give a reading of the x-axis position of that location.  The 2 sets of scales are mounted to the outermost holes on the +Y and -Y side of the ISI, see the attached picture for an example (the right-most edge of the vertical scales are in line with the ISI y-axis centerline).  The -Y scale mount also has a mounting hole for a corner cube retroreflector, which gives us the ability to used the total station's Electronic Distance Measurement (EDM) function to measure the distance between the total station and the outermost -Y holes of the ISI.

There is a brass monument on the floor to the East of WHAM1 that the total station is set over; this is monument LV25, coordinates [-22726.7, -3050.7] mm.  The total station the sights monument LV26 (cooridnates [-2133.6, -3050.7] mm), which is down by WHAM4, and this line sets our horizontal angle to zero.  The total station is then turned -90° to point at the center of WHAM1.  We then use the total station to read the horizontal scale of each set of crossed scales to get a measurement to calculate x-axis position deviation and ISI yaw; the distance between the outermost holes, 2082.8 mm (taken from the SolidWorks model of the ISI), gives us the needed info to calculate the yaw.  Using the numbers for the final measurements from the above main alog as an example, the calculation looks like this:

  • +Y scale reading: 0.0 mm
  • -Y scale reading: +0.5 mm
  • X axis position deviation: (0.5 + 0.0) / 2 = +0.25 mm
  • Yaw: (0.5 - 0.0) / 2082.8 = 240 µrad CCW

Y Axis Position

A corner cube retroreflector is mounted to the -Y scale mount, designed in such a way so the measurement point of the corner cube lines up with the outermost row of holes.  From the SolidWorks model of the ISI this outermost row of holes is 1041.4 mm from the center of the ISI.  The total station occupies monument LV25, which has a y-axis coordinate of -3050.7 mm.  Since the ISI should be at a y-axis coordinate of 0.0 mm, we then use the total station's EDM function to measure the distance from the total station to the corner cube.  The target distance is the y-axis coordinate of monument LV25 minus the y-axis coordinate of the outermost -Y holes of the ISI, or |-3050.7 - (-1041.4)| = 2009.3 mm.  Using the numbers from the Initial measurements (since we did not take a final look at y-axis position yesterday afternoon) in the above main alog as an example, the calculation is:

  • Total Station EDM: 2009.7 mm
  • Target Distance: 2009.3 mm
  • Y axis position deviation: 2009.7 - 2009.3 = +0.4 mm

Z Axis Position and Level

For the z-axis position deviation and ISI level we use an autolevel and a scale set at various points on the ISI.  The autolevel is set to +100.0 mm above the target ISI height using height mark 600 (on the East wall across from WHAM1).  From T1100187 the LHO local coordinate for this height mark is -249.7 mm.  We set a scale on this height mark, with 10.0 mm on the scale lining up with the height mark.  We can then calculate what scale reading required to set the autolevel at +100.0 mm above the target height of the ISI.  The LHO global z-axis coordinate for the WHAM1 ISI is -201.9 mm, but the height mark is in LHO local so we have to translate between the two coordinate systems.  This means we have to add 14.1 mm1 to the LHO global coordinate to get the LHO local coordinate for the WHAM1 ISI; doing this, the LHO local coordinate for the ISI is -187.8 mm.  Now the delta between the WHAM1 ISI z-axis position and height mark 600 is calculated, then add 100.0 mm to that to set the autolevel 100.0 mm above the target ISI height; we have to also add 10.0 mm since that's where the scale was set on the height mark: |-249.7 - (-187.8)| + 100.0 + 10.0 = 171.9 mm.  So sighting 171.9 mm on the scale we mounted on height mark 600 puts the autolevel 100.0 mm above the target z-axis position of the ISI.

With the autolevel set, we then place a scale at several points on the ISI and use the autolevel to read the scale at each point.  The scale we have for this is in inches, and has tic marks at every 0.01".  Since the autolevel is 100.0 mm above the target ISI height we should be reading 3.94" (100.0 / 25.4 = 3.94) on the scale if the ISI is at the correct height; reading a lower number on the scale means the ISI is too high, and reading a higher number on the scale means the ISI is too low.  The scale is placed at the 4 corners of the ISI, with a reading taken at each point.  These 4 readings are averaged to give the height of the ISI table.  For the table level, the delta between the highest and lowest scale reading is used.  Using the numbers from the final measurements from the above main alog, this calculation looks like:

  • -X/+Y scale reading: 3.905"
  • -X/-Y scale reading: 3.915"
  • +X/+Y scale reading: 3.915"
  • +X/-Y scale reading: 3.915"
  • Average: 3.913"
    • Z axis deviation: 3.94 - 3.913 = 0.027" => +0.69 mm
  • Level: 3.915 - 3.905 = 0.01" => 0.25 mm

1: The 14.1 mm correction comes from removing the global x-axis tilt of -619.5 µrad, done by multiplying the x-axis tilt by the x-axis position of the WHAM1 chamber: -22726.7 * -.0006195 = +14.1 mm.

Images attached to this comment
H1 SEI
jim.warner@LIGO.ORG - posted 17:49, Monday 21 April 2025 - last comment - 13:06, Tuesday 22 April 2025(84038)
HAM1 HEPI floating with most of the payload, progress on intial alignment

Jason, RyanC, Mitch, Randy, Jim

This morning Randy, Mitch and I put initial payload on the HAM1 ISI, 210kg of tabletop mass, stacks of 2 D091075 10kg masses. 3 of these stacks are suspended on viton for damping, these are spread across the table as much as I could, but the drawing I'm working from basically has them all in a row down the middle. This got the payload close enough that we could start thinking about initial alignment. 

After lunch, we went out and squeezed 4 more dial indicators on the north side of the chamber. This was pretty difficult getting 2 under the chamber and then attaching 2 more with magnetic bases to the HAM2 crossbeams. With that, we were able to start putting weight on the HEPI springs. We went to each corner, backed all of the stops off till they were barely touching the foot, except for the 3 stops holding the corner up. We then evenly loaded the springs on one pier until the bottom stops were free, while watching dial indicators to make sure nothing moved too much.

Once all 4 corners were floating on springs, we called Jason and Ryan out to set up and take position shots with the total station. All of us very much missed the Faro for the next 90 minutes. When they were set up and got a measurement, I went around and tweaked the springs until the ISI was within more or less +/- 1mm. Table is level to about 1/4 mm across the 4 points we measured. Table yaw I think was out about 250 urad, but hopefully Jason can put some numbers up later.

Tomorrow, the plan is to lock HEPI again, verify we haven't disturbed the position and start reattaching actuators. When that is done, ISC can start their reinstall.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 13:06, Tuesday 22 April 2025 (84059)EPO

Tagging for EPO photos.

H1 SUS
oli.patane@LIGO.ORG - posted 14:31, Monday 21 April 2025 - last comment - 11:31, Wednesday 23 April 2025(84031)
ITMY Health Checks In Vacuum

Took transfer functions for ITMY M0 and R0 now that we are in a good enough vacuum. The ones I had taken in air before doors were put on are here: 83876.

M0
Data (/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/)
2025-04-21_1700_H1SUSITMY_M0_Mono_WhiteNoise_{L,T,V,R,P,Y}_0p01to50Hz.xml
Results (/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Results/)
2025-04-21_1700_H1SUSITMY_M0_ALL_TFs.pdf
2025-04-21_1700_H1SUSITMY_M0_DTTTF.mat

Committed to svn as r12261 for both Data and Results

R0
Data
(/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/)
2025-04-21_1800_H1SUSITMY_R0_WhiteNoise_{L,T,V,R,P,Y}_0p01to50Hz.xml
Committed to svn as r12259
Results (/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Results/)
2025-04-21_1800_H1SUSITMY_R0_ALL_TFs.pdf
2025-04-21_1800_H1SUSITMY_R0_DTTTF.mat

Committed to svn as r12260

I wanted to compare these measurements with old ones, and on the first try I tried comparing these measurements to the last time that ITMY measurements in vac were taken, which was a measurements set from 2018-05-22_2119 and 2018-06-08_1608 for M0 and R0 respectively. However, comparing these two measurements to the ones I just took, there are multiple differences in some of the cross-coupling traces, so I then decided to also compare my measurements to the last full set that was taken (which was in air), 2021-08-10_2115 and 2021-08-11_2242 for M0 and R0. These measurements line up well with the current measurements, so ITMY is looking good!

Comparison between May/June 2018 In-Vac vs Aug 2021 In-Air vs April 2025 In-Vac (/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Data/)
allquads_InVacComparison_MayJun2018vAug2021vApr2025_ALLM0_TFs.pdf
allquads_InVacComparison_MayJun2018vAug2021vApr2025_ALLM0_ZOOMED_TFs.pdf
allquads_InVacComparison_MayJun2018vAug2021vApr2025_ALLR0_TFs.pdf
allquads_InVacComparison_MayJun2018vAug2021vApr2025_ALLR0_ZOOMED_TFs.pdf
allquads_InVacComparison_MayJun2018vAug2021vApr2025_ALL_TFs.pdf
allquads_InVacComparison_MayJun2018vAug2021vApr2025_ALL_ZOOMED_TFs.pdf

Committed to svn as r12263

Non-image files attached to this report
Comments related to this report
edgard.bonilla@LIGO.ORG - 13:06, Tuesday 22 April 2025 (84058)SUS

Adding a comment to talk about the L2P coupling in page 20. It appears as if we have a non-minimum phase zero that appears and dissappears between measurements [see page 20 of the original post above].

While I don't have a full explanation for this behavior, I remember seeing these shenanigans when I was testing the ISI feedforward many years ago. I was too young to make any coherent argument about it, but I remember seeing that the state of the ISI seemed correlated with the behavior. If the ISI is ISOLATED we have normal behavior, if it is DAMPED then we have the non-minimum phase behavior.

Here is a comparison between the last few years of successful ITMY  M0 to M0 transfer functions, with the ISI states retrieved from plotallquad_dtttfs.m. The color coding is selected to separate the situations with the ISI in 'ISO', and with the ISI in any other state. in pseudocode:

switch ISI-STATE
    case 'Isolated'
        color='blue';
    case 'Damped'
        color='red';
    case 'Locked'
        color='black';
    otherwise
        color='magenta';
end
 
I note that with this small sample size, we indeed see that all of the cases with the ISI in ISOLATED look the same, with the correct zero behavior that the MATLAB QUAD model would have as well. As for the DAMPED state, there is one outlier, and it is the measurement from 2017-12-20. The reason for the discrepancy is unclear to me. I will try to get a larger sample size by looking at other QUADs later. Stay tuned!
Images attached to this comment
edgard.bonilla@LIGO.ORG - 10:38, Wednesday 23 April 2025 (84068)

I got the same comparison done for ITMX and the ISI backreaction theory really does not seem to hold water.

There are two main regimes, same as ITMY. This time, the more recent ITMX TFs (after 2017-10-31) look more similar to the old (prior to 2021) ITMY TFs.

I am at a loss of what is making the change happen. Brian suggested it might be related to the vertical position of the suspension, maybe this is the next thing to test.

Images attached to this comment
oli.patane@LIGO.ORG - 11:31, Wednesday 23 April 2025 (84084)

To back up Edgard's conclusion, I took measurments with the ISI in Fully Isolated and we didn't get the extra zero back 84083

Displaying reports 1561-1580 of 83205.Go to page Start 75 76 77 78 79 80 81 82 83 End