Displaying reports 101-120 of 88272.Go to page Start 2 3 4 5 6 7 8 9 10 End
Reports until 17:37, Sunday 28 June 2026
H1 AOS
robert.schofield@LIGO.ORG - posted 17:37, Sunday 28 June 2026 - last comment - 12:14, Monday 29 June 2026(90787)
Baffles on +X side of HAM3 aligned, next step is alignment on -X side and mitigation of SPI baffle retroreflections

Mitchell, Disha, Robert

On Friday we finished alignment of the baffles on the +X side of HAM3. This took extra time because we didn’t expect 12 point flange bolts on the PR2 dog clamps that we were moving. Beam spot photos from the BBS showed that we had mitigated retroreflections from the dog clamps and other retro-reflectors that we were worried about, but the brackets for two of the SPI baffles formed strong 2-D corner reflectors with the table top (see figure). We need to hide them with something that is the same height but not normal to the BBS-PR3 beam, and we need to finish aligning the baffles on the –X side.  We may also need to treat two of the table baffle brackets on the +X side of HAM3 if they produce retroreflections in PR3 beam spot photos.

Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 12:14, Monday 29 June 2026 (90801)SEI, SPI, SYS, VE
Here's some pictures to aide the conversation about "which brackets are SPI bracket retro-reflectors?"

These were taken on 2026-06-18 when TJ and I were installing these baffles for the first time (see LHO:90676). Two versions of each photo, one annotated and one not.

2026-06-18_H1SPIH23_ISIK_Baffles_BigPicture_ANNOTATED.jpg shows "looking in the +X direction" big-picture view of the beam splitter from inside the HAM23 mode cleaner tube, and highlights in red which baffles' brackets are the problem.

2026-06-18_H1SPIH23_MinusYSide_Baffles_TopDown_IsometricView_ANNOTATED.png shows a top-down / isometric, "looking in the +X / +Y / -Z direction"  view of the -X / -Y corner of the optical table, again calling out the problematic baffle brackets.

Saying it out loud -- it's not one baffle's brackets, its both 
    - the -Y bracket of the middle upper panel baffle, and 
    - the +Y bracket of the -Y upper panel baffle.
of the ISIK shroud assembly D2400106

Also -- just saying it out loud. Robert shows how shiny these brackets are in the -X view of HAM3 from the beam splitter. "Why aren't these an issue for the -Y view of HAM4 from the beam splitter?" Because HAM4 doesn't have any of these HAM table baffles on its -Y side -- the HAM3 baffles exist because we had to remove the lower panel of the HAM2-HAM3 *mode cleaner tube* baffle on the HAM3 end of the tube (LHO:90138 and LHO:90162) in order to support SPI. But the equivalent panel on the HAM4 end of the HAM4-HAM4 tube baffle is still in place, so these HAM table baffles are not needed.
Images attached to this comment
H1 SQZ
sheila.dwyer@LIGO.ORG - posted 17:11, Friday 26 June 2026 - last comment - 09:09, Wednesday 01 July 2026(90783)
OMC scans and beam profile measurements for different psams

Eric, Ryan S, Camilla, Sheila

All week we have been working on getting a set of OMC scans and beam profile measurements for different psams.  We have both sets of data now, with plots and scripts coming soon next week.  

OMC scans

We started with a script that Begum gave us from HAM6 work at LLO.  We set up ASC loops to go from ASA and AS B DC signals to ZM4 and ZM5 (as described in 90742).  We struggled a while to lock the OMC on the seed beam in air, hampered by 90754.  With that noisy OMC lock, yesterday Camilla manually aligned OM3 and the OMC suspension carefully to maximize the 00 transmission.  We then added offsets to H1:OMC-ASC_QPD_{A,B}_{PIT,YAW}_OFFSET, which is not the usual location for OMC QPD offsets.  We will need to get rid of these offsets before we go back to locking. 

OMC A offset: PIT 0.088 YAW: 0.133  OMCB offset: PIT 0.27 YAW: -0.22

We found that we were able to move the psams, whih misaligns the OMC terribly, run the centering loops to the ZMs, then run the OMC QPD loops to bring the 1st order peaks back down to a couple % of the 00 peak repeatedly.  We spent some time modifying and then debugging the script that Begum shared with us.  

It takes in a list of ZM4 and ZM5 strain gauge values, moves the psams servos target to that point and waits 30 seconds with the ZM centering loops on (it doesn't check the acutal value of the strain gauge, perhaps this would be a good thing to add next time).  It then turns on the OMC QPD loops for 20 seconds.  It then takes a 100 second ramp of the OMC PZT, and saves the times and ZM strain gauge targets into a yaml file.  

There is a template you can use to watch all this at userapps/sqz/h1/Templates/ndscope/OMC_psams_scans_monitor.yml  The script that runs these sweeps is at sqzutils, or /ligo/gitcommon/squeezing/sqzutils/omc_scans_sweep_psams.py  There is also a script there that loads the data, identifies the peaks and estimates mode mismatch and misalignment there, analyze_psam_omc_sweeps.py.  A preliminary plot is attached (apologies for the color choices and linear y scale here).  

M2 profile measurements

Eric and Ryan S took a series of M2 profiler measurements of the beam on SQZT 7 today, doing the alignment procedure at each strain gauage setting (they didn't adjust ZM alignments).  Their data is in here, we will post some plots of this next week.

Note about ZM5 strain guage

While Eric and Ryan were making beam profile measurements, they ran into a situation where ZM5 would not go the strain guage setting of 2.  I was able to get it to go to 2 manually, but noticed that there were times when the strain gauge voltage dropped to zero, similar to a problem seen at LLO HAM6 recently.  We should follow up on this next week.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 13:58, Monday 29 June 2026 (90802)

More on the ZM5 strain gauge issues -

While Eric and I were taking beam profiles and moving to the last step for the ZM5 PSAM (requesting 2V), the strain gauge readback voltage fell to -2.8V and got stuck, shown at the T-cursor in the first attached ndscope. Changing the requested voltage away from 2V did not affect the strain gauge's behavior or the voltage sent to the PZT, which looked to be railed close to 200V. Eventually Sheila was able to unstick the voltage and get the strain gauge back to 2V by stopping the servo and clearing its history.

This is reminiscent of behavior seen at LLO with one of their new HAM6 PSAMS, OMA2, where after scanning the PZT to the edge of its range, the strain gauge would show open loop for a few seconds, then return to normal (LLO:alog80740 and FRS 37456). We haven't run the repeated scans with ZM5 like LLO did with their OMA2, but we looked for other times recently when the ZM5 PSAM showed weird behavior and found a time earlier that day during one the the OMC scans; see the second ndscope. It's possible that when this happened to Eric and I on Friday, the strain gauge would have fixed itself after a few seconds like in LLO's case, but the integrators in the servo kept the voltage railed.

LLO's solution for this was to fully swap out the optic and its attached PZT/strain gauge assembly, so while we think about this, we are assessing what spares exist that could potentially be swapped in.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 07:13, Tuesday 30 June 2026 (90804)

ome information about these data:

  • Charachterizing the astigmatism by calculating the overlap between the horizontal and vertical q's, the range we have is 0.3%-1%
  • By propagating these measured qs through the Finesse-ligo model to the OMC, the predicted mode mismatches range from 1%-8.4%
  • M^2 ranges from 1.16 to 1.35
  • The measured mismatch measured from the OMC scans ranges from 1.75% to 13.5%

The first attachment shows the beam parameters measured on SQZT7 propagated to the AR side of SRM (after reflecting off SRM), this can be compared to the second attachment to 90345.  These results are different from what we had back in May while the chamber was under vacuum and before our realignment.  

THe next two plots show the measured OMC scans, with the same data as plotted above.  In the scans with ZM5 strain gauge at -4.5V the 4th order mode is large, so I've also identified it for those scans where it is above 0.005 mA.I'm estimating the mismatch as ( mean height of 2nd order + mean height of 4th order)/(sum of mean heights of 0, 1, 2, 4 orders) in the legend in this second plot, which makes the mode mismatch worse for the ZM5 -4.5 V plots than what is  listed above. 

The last attachment is an attempt to summarize this data.  The bottom two panels show the same data as in the stem plot.  The the left panel shows the M^2 value as a function of strain gauge, this does seem to have a dependence on ZM5, which visually looks correlated with the values for which the propagation model is underestimating the mode mismatch for ZM5.  Eric will add some thughts about M^2 and the OMC scans.  The top right panel shows the overlap between the vertical and horizontal measured qs. Our worst astigmatisms are in the same region of psams settings as the best mode matchings.  If this is 1%, and the overlap in one direction is perfect the overall mode matching would be 100*(1-sqrt(1*0.99))=0.5%.  

Images attached to this comment
camilla.compton@LIGO.ORG - 09:09, Wednesday 01 July 2026 (90823)

During this PSAMS strangeness, at two times when the ZM5 strain gauge was reading -2V, the applied PSAMS voltage was 88V and 184V, see attached. This seems to be too big of a difference in applied voltage to be only caused by hysteritis. We are not the sure -2V strain gauge reading while there was 184V applied is reliable. This happened twice, the second time the strain gauge read -2.7 while the applied voltage was 194V, attached

We then did some ramps: 0-200V over 30s, 200V to 0V over 50s and then 0V to 100V over 50s. In each of these ramps, the ZM5 PSAMS strain gauge seemed to behavior strangely, sometimes in the center of the range. See attached 

Images attached to this comment
H1 SEI
jim.warner@LIGO.ORG - posted 16:38, Friday 26 June 2026 (90782)
BSC2 HEPI actuators reattached.

After getting IAS sign off from Keita, Betsy and Jason yesterday, Mitch and I went to BSC2 to start reattaching the actuators. We finished that this afternoon, according to dial indicators on the chamber we haven't moved from the locked position, but stops are still engaged. Actuators are valved in,  and I have set the alignment targets for HEPI to the current value. IPS readouts should be meaningful again for trends, just remember that they have been disconnected basically since the cartridge was pulled from the chamber, so doing alignment comparisons between before that time and now are pretty pointless. On Monday, I plan to unlock, look at lock/unlock offsets, then use the loops to servo to this locked position. If locked to unlocked shift is large, it may mean we will want to do another round of spring adjustments, but I should be able to do those from above, using the IPSs. 

LHO General
corey.gray@LIGO.ORG - posted 16:30, Friday 26 June 2026 (90771)
Fri Ops DAY Shift Summary

TITLE: 06/26 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Main activities today were: SQZ measurements in lvea + control room, connecting actuators for BSC2 hepi, ham3 baffling...
LOG:

LHO VE (VE)
jordan.vanosky@LIGO.ORG - posted 16:29, Friday 26 June 2026 (90780)
Removal of Viewports on HAM2

Jordan, Jake Z, Owen H

Per FRS Ticket 38164, two viewports were removed off of HAM2 and replaced with Class A 10" CF blanks.

On the East Door, port A2F2 was an uncoated ZV-800 (SN 66), and on the West door A1F1 was a ZV-800 Coated SN (R009). These two viewports will be inspected on the bench and put into spares inventory if all looks okay and passes inspection criteria.

These two blank flanges will be added to the list for leak checking during pumpdown.

Images attached to this report
H1 OpsInfo (OpsInfo, SEI)
corey.gray@LIGO.ORG - posted 16:27, Friday 26 June 2026 (90779)
Verbal Alarm Edit

After this week's HAM3 CPS work, had been hearing "HAM3 CPS Glitch" verbal alarms every few seconds, so volume reduced on Verbal.  To allow us to hear Verbal, RyanS made an edit to the tests.py file to remove the alarm for HAM3's CPS Glitches (he commented this change in the file). 

This specific alarm will need to be restored--after the CPS work is complete.

H1 SEI (SEI)
shoshana.apple@LIGO.ORG - posted 15:38, Friday 26 June 2026 - last comment - 15:11, Monday 29 June 2026(90778)
Updating medm for HAM2&HAM3 blends

I updated the some of the medms for the blends for HAM2&HAM3 to include the SPI and CRS, added INERT_MID

Blend of four sensors: /opt/rtcds/userapps/release/isi/common/medm/hamisi/ISI_CUST_BLEND_SUPSENS_FOUR.adl

Made new block for a blend with four sensors: opt/rtcds/userapps/release/isi/common/medm/hamisi/new_FADER_4PART.adl

The blocks for 2 sensors and 3 sensors (new_FADER_PART.adl, new_FADER_3PART.adl) currently have T240 labeled instead of SPI, I didn't want to mess with those blocks, as they are used for other chambers and it's still labeled T240 in the model, but for the 4PART I did switch T240 to SPI

Made new blend fade medm screen for HAM2 & HAM3: opt/rtcds/userapps/release/isi/common/medm/hamisi/ISI_CUST_H23_BLEND.adl

Made overview screen for HAM2&HAM3:opt/rtcds/userapps/release/isi/common/medm/hamisi/ISI_CUST_H23_FADE_OVERVIEW.adl

The only thing changed was to switch which screen the ST1 BLEND FADE button takes you to the new medm.

I added and commited all these to the SVN and updated the sitemap to link the them for HAM2 and HAM3

Images attached to this report
Comments related to this report
shoshana.apple@LIGO.ORG - 15:11, Monday 29 June 2026 (90807)

Continued working on HAM2&3 medm screens

Updated the input filters in opt/rtcds/userapps/release/isi/common/medm/hamisi/ISI_CUST_H23_FADE_OVERVIEW to include input filters for the SPIINF, SPI_FF, and CRSINF, and link to the SPI and CRS overview screens. The buttons link to the userapps/release version of the overview screens.

I made a few new input filter screens: 

/opt/rtcds/userapps/release/isi/common/medm/hamisi/ISI_CUST_CHAMBER_SPIINF_ALL.adl

/opt/rtcds/userapps/release/isi/common/medm/hamisi/ISI_CUST_CHAMBER_SPI_FF_ALL.adl

/opt/rtcds/userapps/release/isi/common/medm/hamisi/ISI_CUST_CHAMBER_CRSINF_ALL.adl

and set up the a link to an ndscope of the BLRMS channel (like the CPS), but that can be easily gotten rid of.

I've commited all of the to the svn

LHO General
corey.gray@LIGO.ORG - posted 07:58, Friday 26 June 2026 - last comment - 12:29, Friday 26 June 2026(90770)
Fri Ops Day Transition

TITLE: 06/26 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 17mph Gusts, 12mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:

Comments related to this report
betsy.weaver@LIGO.ORG - 12:29, Friday 26 June 2026 (90777)

Coming down to the final weeks of closeout on this vent window.

Images attached to this comment
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 22:52, Thursday 25 June 2026 (90769)
HAM1and HAM2 Annulus System Update

(Jordan, Owen, Jake, Gerardo)

The annulus sytem for HAM1 and HAM2, shared volume, was pumped down initially with a single aux cart (Hi cube), then to speed thing up a second aux cart (another Hi cube) was added via the HAM2 AIP port.  After a couple of days the ion pump controllers appears to be able to keep up with the pressure, see attached trend plot.

 

Images attached to this report
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 22:30, Thursday 25 June 2026 - last comment - 16:59, Monday 29 June 2026(90768)
CP1 Cooldown Update

(Jordan, Owen, Jake, Gerardo)

The cryotrap cooldown continues, we continue to pump on the cryotrap volume with a turbo pump, the turbo is backed with a SS500 aux cart.

Small changes were the removal of the calibrated leak from the RGA tree, along with the removal of other components in preparation to install an incoming small ion pump next week.

Current pressure in the cryotrap volume is 7.38X10-10 Torr.

 

Images attached to this report
Comments related to this report
jordan.vanosky@LIGO.ORG - 16:59, Monday 29 June 2026 (90814)VE

Jordan, Jake, Owen

The RGA tree was removed and replaced with the dedicated 75 l/s Starcell ion pump and a pumpdown port for the pump tree.

All flanges were helium leak tested, no He signal above the leak detector background were found. (~1.5E-10 Torr-l/s)

Volume is currently being pumped by a small aux cart, and the ion pump will be powered on tomorrow. The volume will then be introduced to the cryopump volume once the pump pressure reaches ~E-9 Torr on ion pump alone.

 

 

Images attached to this comment
H1 SEI
arnaud.pele@LIGO.ORG - posted 22:27, Thursday 25 June 2026 (90763)
HAM3 CPS card setting

Shoshana, Jim, Arnaud

The x6 HAM3 new CPS boards have been set to the following configuration (as per E2200455): 

  board SN probe SN Location
H1 29536 22777 Slot 1 in crate +Y side
V1 38690 22781 Slot 2 in crate +Y side
H3 12563 22779 Slot 3 in crate +Y side
V3 38494 22775 Slot 4 in crate +Y side
H2 23370 22778 Slot 1 in crate -Y side
V2 11950 22780 Slot 2 in crate -Y side

There was some glitching noticed on the channels that were in range prior to this work, which was fixed after this setting change (see attached). Two of the cards were set to Master before and Jim is confident this would have created problems. 

Left to do : 

1- Label the cards at the front of the boards with module SN and corner #
2- Disconnect the grounding to the chamber of the crate on the +Y side 
3- Label the in-air lemo cables with H1, V1, H2 ...
4- Update ICS with the new boards SN
5- Gather the cards that were removed from WHAM3 to send back to microsense for recalibration with a new set of sensors (RMA)

The tracking spreadsheet for this ECR was updated here: E2500184 

Images attached to this report
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 19:13, Thursday 25 June 2026 - last comment - 16:50, Thursday 02 July 2026(90767)
HAM2 West Side Door VPs Inspection

(Jordan, Gerardo)

We inspected the 5 viewports on the west door of HAM2.

We found on viewport A1F4 the typical smudge or print left by first contact the print appears to be on the inside, but not the vacuum side (this VP has two windwos).  We also noted a scratch on the outside window (not under vacuum), around 1 O'clock and about 3/4" away from the edge, we contacted Keita who was walking by the area and we asked him if the location of the smude/scratch were on the path of beam, no they are not.  BTW, VP4 is a high quality wedged viewport, a double window, type D1101714.

Then on A1F2 ZV-800 viewport we noted some scratches, something was dancing on the window, since it appears as a single scratch with multiple turns.  This viewport was removed and replaced with a spare ZV-800 type.  SN of new unit is 0098, old scratched and full of particulate viewport serial number 63.

All other viewports nothing to report, A1F1, A1F3, A1F5.

Images attached to this report
Comments related to this report
gerardo.moreno@LIGO.ORG - 16:34, Thursday 02 July 2026 (90887)VE

(Jordan, Gerardo)

Both viewports were removed to get a closer look on the bench, both have several scratches on both surfaces (vacuum side and air side), we are trying to quantify the defects.  More on the inspection on the next couple of days.  Locations of viewports are A2F1 and A2F4.  The rest of the ports have blanks.

jordan.vanosky@LIGO.ORG - 16:50, Thursday 02 July 2026 (90888)

Pictures of the A2F1 (ZV800 SN 80 Uncoated) and A2F4 (ZV-800 SN81 Uncoated) viewports on HAM2 for reference. Full inspection report will be made and posted to the DCC now that the viewports are removed. We are evaluating potential replacements.

Images attached to this comment
H1 SUS
oli.patane@LIGO.ORG - posted 18:10, Thursday 25 June 2026 - last comment - 09:26, Friday 26 June 2026(90765)
BBSS P to Y as compared to BSFM

Arnaud, Marie, Jeff, Oli

Compared to the BSFM, the cross coupling in the BBSS from P to Y is mught higher (This plot shows ~ 2 orders of magnitude, but I don't want to confirm that yet since the data fudge for the BSFM might be incorrect).

I made a comparison of the last few BBSS P to Y measurements and compared them to an old BSFM P to Y measurement.

We found that the P to Y cross coupling looks a lot like just Y to Y (bright blue), so there is much more Y than there should be.

There is still some more work to be done to absolutely confirm this, but current in progress results can be found in /ligo/svncommon/SusSVN/sus/trunk/BBSS/Common/Results/comparetripleparams/2026-06-25_BBSSvsBSFM, r13050.

Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:26, Friday 26 June 2026 (90775)
A minor grain of salt: though the "(BBSS Teststand BOSEMs * 0.35587 | P to Y)" BOSEM data set seems to report *equal* if not *worse* P to Y magnitude as Y to Y magnitude, the data quality is garbage -- likely incoherent at all-but-on-resonance frequencies. 
H1 SUS
oli.patane@LIGO.ORG - posted 12:27, Thursday 25 June 2026 - last comment - 09:07, Friday 26 June 2026(90758)
BBSS Satamp to Coil Driver Checks

Jeff, Arnaud, Betsy, Oli

Yesterday we checked the coil response for the BBSS QOSEMs. We did this at the BBSS M1 QOSEM satamp. Everything is looking good and as we expected.

We did this by putting the BBSS in SAFE, then unplugging the db15's that go to the coil drivers. In their place Jeff plugged in a fancy breakout board that separated out each of the 4 channel pins. The resistance of each of the reading device channels is listed below:

Coil Voltage (Satamp to Coil Driver)
Resistance of reading device
(no uncertainty to 0.1 Ohm)
Used to measure
Breakout (B/O) Channel 1 24.3 Ohm CH1 (F1), CH5 (LF)
Breakout (B/O) Channel 2 20.9 Ohm CH2 (F2), CH6 (RT)
Breakout (B/O) Channel 3 23.1 Ohm CH3 (F3)
Breakout (B/O) Channel 4 23.4 Ohm CH4 (SD)

 With this channel breakout board we then went channel by channel to measure voltage. We turned the master switch ON so counts can head out from the COILOUTF filter bank. For each channel, we noted the COILOUTF filter bank gain sign, and if there was any voltage read out when no offsets were put in. Then we put an OFFSET in the COILOUTF filter bank and noted the voltage that we were reading. We did this for multiple OFFSETs for each channel. After testing each channel, with an offset still on, we would check the other channels to see if anyone else was seeing anything more than their default reading with no offsets, which they never saw anything different from that. Here is that data:

Cable SUS_BS_85 SUS_BS_87
Channel CH1 CH2 CH3 CH4 CH5 CH6
OSEM F1 F2 F3 SD LF RT
COILOUTF gain -1 -1 1 1 -1 1
  COILOUTF OFFSET Voltage (V)
(+/- 0.5 mV)
COILOUTF OFFSET Voltage (V)
(+/- 0.5 mV)
COILOUTF OFFSET Voltage (V)
(+/- 0.5 mV)
COILOUTF OFFSET Voltage (V)
(+/- 0.5 mV)
COILOUTF OFFSET Voltage (V)
(+/- 0.5 mV)
COILOUTF OFFSET Voltage (V)
(+/- 0.5 mV)
  20,000 -2.825 20,000 -2.837V 20,000 2.848 20,000 2.839 20,000 -2.826 20,000 2.836
  10,000 -1.413 10,000 -1.419 10,000 1.424 10,000 1.419 10,000 -1.413 10,000 1.418
  0 0 0 -1.00E-03 0 0 0 0 0 -1.00E-03 0 0
  -10,000 1.412 -10,000 1.416 -10,000 -1.424 -10,000 -1.42 -10,000 1.412 -10,000 -1.418
  -20,000 2.825 -20,000 2.83 -20,000 -2.849 -20,000 -2.839 -20,000 2.825 -20,000 -2.837
  With OFFSET of -20,000 (in V): With OFFSET of -20,000 (in V): With OFFSET of -20,000 (in V): With OFFSET of -20,000 (in V): With OFFSET of -20,000 (in V): With OFFSET of -20,000 (in V):
  CH1 (B/O Ch1) -- CH1 (B/O Ch1) 0 CH1 (B/O Ch1) 0 CH1 (B/O Ch1) 0 CH5 (B/O Ch1) -- CH5 (B/O Ch1) -1.00E-03
  CH2 (B/O Ch2) -1.00E-03 CH2 (B/O Ch2) -- CH2 (B/O Ch2) -1.00E-03 CH2 (B/O Ch2) -1.00E-03 CH6 (B/O Ch2) 0 CH6 (B/O Ch2) --
  CH3 (B/O Ch3) 0 CH3 (B/O Ch3) 0 CH3 (B/O Ch3) -- CH3 (B/O Ch3) 0        
  CH4 (B/O Ch4) 0 CH4 (B/O Ch4) 0 CH4 (B/O Ch4) 0 CH4 (B/O Ch4) --        

You can see that the voltage signs are all consistant with the sign of the OFFSET * COILOUTF gain, and the values are all pretty consistant as well.

After we were done reading out the voltages for SUS_BS_85, we put offsets of -20,000 in F1, F2, and F3 and checked the voltages on all three channels. All three channels read the same voltage as they had when we had tested them individually at -20,000 counts. That table is below.

OFFSET of -20,000 for F1, F2, F3 (in V)
CH1 (F1) 2.825 V
CH2 (F2) 2.831 V
CH3 (F3) -2.849 V
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:07, Friday 26 June 2026 (90772)
Some pictures of the "DAC Voltage to Coils" setup that gathered the above data.

2026-06-24_QOSEM_CoilDriveDACVoltage_BigPicture.jpg
    Zoomed out photo of SUS_BS_85 cable disconnected from the Coil Driver 1-4 channel input to the QOSEM satamp chassis in SUS-R2, and connected to the dummy OSEM system (what Oli calls the "fancy breakout board"), with a DVM reading out the voltage across the resistors. In the pictured case, we're using the DVM (placed in the rack for convenience) reading out the voltage across the Channel 1 resistor of the dummy OSEM which is connects across the + and - legs of the Channel 1 output of the cable (i.e. F1).

2026-06-24_QOSEM_CoilDriveDACVoltage_Zoom_DummyCoilResistor.jpg
    Zoomed in photo of the clip leads hooked across the resistor. Since the sign of the voltage is critical, I made sure to find a dummy OSEM that had the + and - legs clearly called out, ensuring the positive, red, signal lead for the BNC connection was connected to the + leg of the drive signal, and black to the -, return, leg. 

2026-06-24_QOSEM_CoilDriveDACVoltage_Zoom_DVM.jpg
    Zoom in photo of an example of the DVM read-out voltage during the given offset (in this case, it was the CH1, F1, 10,000 [ct] offset -- multipled by the -1 COILOUTF gain -- to read -1.413 [V]_DC). Note -- again because signs are under question in this investigation -- careful attention was paid to ensure the orientation of the BNC to banana adapter into the DVM; connecting in the standard "nub is negative" configuration i.e. the shield of the BNC cable, connected to the black clip lead on the other end, is connected to the black COM input of the DVM.

2026-06-24_QOSEM_CoilDriveDACVoltage_DisconnectedSatampCable.jpg
    Zoom in photo of where the SUS_BS_85 DAC drive cable connects into the QOSEM satamp.
Images attached to this comment
H1 SUS
oli.patane@LIGO.ORG - posted 09:59, Thursday 25 June 2026 - last comment - 19:50, Monday 29 June 2026(90747)
QOSEM SatAmp to QOSEM Cable Resistance

Jeff, Betsy, Arnaud, Oli

Yesterday afternoon we went to the BBSS QOSEM satamp and checked the coil resistance. We did this by putting the BBSS in SAFE and then unplugging the Satamp to Duopus cables one by one. Each of these three cables have the pins for two QOSEMs, split as CH1 + CH2, CH3 + CH4, and CH5 + CH6. Each cable was unplugged and then the pins for each coil probed. Below are the results. These values are all pretty similar.

Coil Resistance (Satamp to Duopus)
  CH1-2 (SUS_BS_81) CH3-4 (SUS_BS_82) CH5-6 (SUS_BS_83)
Channel CH1 CH2 CH3 CH4 CH5 CH6
CH Coil Pins 23 -> 10 18 -> 5 23 -> 10 18 -> 5 23 -> 10 18 -> 5
OSEM Mapping F1 F2 F3 SD LF RT
Coil Resistance 39.1 +/- 0.1 Ohm 40.0 +/- 0.2 Ohm 39.0 +/- 0.2 Ohm 39.7 +/- 0.2 Ohm 40.0 +/- 1.5 Ohm 40.5 +/- 0.5 Ohm
Notes         Larger than normal variation  
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:22, Friday 26 June 2026 (90773)
Picture of the setup: (in this instance) the QOSEM CH 3-4 (i.e. F3 and SD) SUS_BS_82 cable is disconnected at the QOSEM satamp in SUS-R2, and its "to chamber" end is connected to a standard D25 breakout board. Clip leads are connected across the pins as described above to gather the coil resistance.

These results are as expected: the QOSEMs are up-cycle bodies and coils from BOSEMs, which are known to have resistance of ~40 [Ohm], in this case 40 +/- 2.5%.

Note, this is markedly different than the 35 +/- 10% [Ohm] -- 31.5 to 38.5 [Ohm] -- assumed in LHO:90743. Maybe Tom is assuming that this is the coil resistance if measured directly at the coil flexi-circuit terminals, and the "extra" resistance is from the long cable run to the chamber which is what we typically measure.

However, the 2.5% spread in coil resistance values between F1, F2, and F3, is NOT enough of an imbalance to explain the worrisome P to Y cross-coupling seen at DC (LHO:90728 and LHO:90739) and in the M1 to M1 transfer functions (LHO:90765).
Images attached to this comment
thomas.roocke@LIGO.ORG - 19:50, Monday 29 June 2026 (90817)

Indeed, the ~35ohm nominal coil resistance I quoted in LHO:90743 is measured at the QOSEM uDB9, so not including cable or feedthrough resistance.

After assembly I measured the coil reistance of these LHO BBSS QOSEMs to be:

QOSEM SN LHO BBSS Channel Coil Resistance at uDB9
S2600012 F1 / CH1

34.6

S2600009 F2 / CH2

35.6

S2600013 F3 / CH3

35.1

S2600008 LF / CH5

35.7

S2600011 RT / CH6

36.4

S2600010 SD / CH4

35.6

 

LHO VE (VE)
travis.sadecki@LIGO.ORG - posted 16:26, Thursday 18 June 2026 - last comment - 18:19, Thursday 25 June 2026(90673)
Unused HAM ISI Oplev viewports removed

Today Gerardo and I removed the unused HAM ISI Oplev viewports from the VP7 ports of both the -X input manifold and the +Y output manifold.  The ports were blanked off with 10" CF blanks.  I noted a series of 3 scratches on the angled flat of the flange, but the knife edge itself wasn't noticeably deformed.  See pics.  

Note to VAC: These will need to be leak checked during pumpdown.

Images attached to this report
Comments related to this report
gerardo.moreno@LIGO.ORG - 18:19, Thursday 25 June 2026 (90766)VE

The rest of the unused HAM ISI Oplev viewports were removed.from the VP5 position, they were unused ISI Oplev at +X input manifold and the -Y output manifold. The ports were blanked off with CF blanks.  The 7.8" aperture MDC viewports, part number 9722012 appear to be in good shape.  The chamber flange on the output manifold had a gross scratch that I resorted to "stoning" it to remove the scratch.

One small optical lever pier was removed from the VP5 position on the input manifold +X side, near HAM3.  No issues to report.  Some of the internal components were placed in a cabinet on the south bay area, per Jason's request.

Images attached to this comment
H1 SQZ
begum.kabagoz@LIGO.ORG - posted 17:36, Sunday 14 June 2026 - last comment - 11:55, Thursday 02 July 2026(90613)
HAM7 - FC path mode matching projections from beam profile data

Below is the analysis for data taken on the FC path: between ZM1 and ZM2 and between ZM2 and ZM3, with Nanoscan, see Camilla's log 90573. As a reminder, ZM1 are flat optics, ZM2 is a PSAM with variable curvature, FC1 HR side is flat, AR side is curved with RoC ~1m. 

The data suggest that the OPO mode is slightly different from O4 OPO, and also strongly suggest a new optimal ZM2 PSAM voltage can be found within the range. 

We measured the beam profile at 5 different points after ZM1 with A:L2 lens at its nominal 0 position (sled that the lens lives on is flush to its translation stage on both front and back edges). At the last point with A:L2 at 0, we realized it would be pertinent to measure beam profiles for the two extremities of the A:L2 translation stage: -13 mm, which is closer to ZM1 by 13 mm and +17 mm, which is 17 mm further from ZM1. We then proceeded to take 5 measurements (again downstream from ZM1) for each of these lens positions. The nanoscan screenshots for each measurement are attached in the .zip folder. 

The attached gif shows the beam waist position estimation extracted from the beam profile scans downstream ZM1, for all three A:L2 positions. The "target" and "O4 x/y" come from Keita's log 59515The overlap plot attached shows the field overlap in percentage for all three A:L2 positions, with target and O4 beam parameters. With A:L2@0, the overlaps are above 99%, which bodes well for the FC mode matching prospects. There could potentially be a better mode matching solution to the "target" or "O4" for A:L2 between 0 pos and -13mm pos. However, the following measurements betwen ZM2 and ZM3 suggest fine-tuning of A:L2 position will not be necessary. 

We also measured beam profile between ZM2 and ZM3 for three different points, setting ZM2 PSAM voltage to 4 different values at each point. The "nominal" O4 strain gauge (S.G.) for ZM2 has been 3.15 V, which corresponds to ~ 60 or 90 V pzt supply voltage depending on which direction one scans from. The edges of the psam range are 0 V and 196 V, which corresponds to ~1.2-1.3 V and ~6.04 V S.G. respectively. In the interest of more uniform sampling of the available psam curvatures, we also chose to sample 4.5 V S.G. (~120 V or 150 V). 

This table shows experimental data mapped to radii of curvature of the ZM2 mirror, using Camille's E2100298. The exact PZT strain gauge/ PZT supply voltage that gives a certain RoC is affected by the hysteresis curve i.e. sweep direction.

Strain Gauge (V) PZT Supply Voltage (V) RoC (m) with increasing scan RoC (m) with decreasing scan
1.3 V 0 0.8211 0.82202
6.0x V 196 0.8911 0.89114
3.1x V 60 (d) or 90 (i) V 0.8523 0.85025
4.4x V 120 or 150 V 0.87534 0.87242

Attached gif for propagation between FC1 and ZM2 show esimated beam parameters for all four SG cases: 1.3, 3.1x, 4.4x and 6.0x V. The exact values for the strain gauge varied from one beam profile position to the next, however it should be good enough to tell if we have enough range on ZM2 or not.

The gif switches between different SG values once every 2 second, the lefthand plot is useful in looking at the beam divergence near FC1 while the righthand plot is a zoom-in around the beam waist. Looking at the estimated beam waist position for 1.3 V and 3.1x V cases switching across the "FC x/y waist", "VOPO target waist", ''O4 x/y waist", we can guess there could be a better mode matching solution between these two SG values. "FC x/y waist" comes from the Finesse eigenmode solution for the FC path (thanks Kevin Kuns!), target and O4 values are the same from the above-mentioned Keita log, assuming ZM2 curvature to be 0.85025 m (3.15V SG), and the following distances between the optics: A:M3 --> ZM1: 158.2 mm, ZM1--> ZM2: 1498.625 mm, ZM2 --> ZM3: 1821.497 mm, ZM3--> FC1: 1000.261 mm. Camilla extracted these distance values from D1900365-v1.

Knowing the applied PZT voltage and the corresponding RoC, we can use the measurements at 3.1x V and 1.3 V to estimate the mode matching we would obtain if we swept the RoC between that of these strain gauge values. The attached FC mode matching projection plot is computed by taking beam parameter estimated from the beam size measurements for 3.1x V, propagates the beam back to ZM2, unapplies the estimated RoC (decreasing RoC value was used informed by data, indicated in bold in the above table), then reapplies the RoC between these two values, after the overlap with the FC eigenmode is calculated. This projection suggests that mode-matching points with >99% overlap for both x and y axes are accessible. Clearly, there is varying astigmatism with strain gauge setting, see beam profile plots where 3.1x and 6.0x V shows beams with smaller astig. than the other two points. Since the PSAM characterization data gives only a single RoC number rather than separate x/y effective curvatures, the projection should be interpreted as approximate. In practice, the final optimization should be done empirically.

The effect of the astigmatism is also apparent in this defocus vs beam size at FC1 plot that shows mode matching contours. The calculation is made at the FC1.p2.o plane in Finesse.

 

Images attached to this report
Non-image files attached to this report
Comments related to this report
begum.kabagoz@LIGO.ORG - 14:06, Wednesday 24 June 2026 (90744)

The beam width data kindly tabulated by Camilla, the R(V) data from Camille's dcc E2100298, and the analysis code .py are attached, in the .zip. Fair warning, the analysis code also makes a bunch of plots I find useful to look at but another user may find irritating :)

Non-image files attached to this comment
begum.kabagoz@LIGO.ORG - 16:03, Wednesday 24 June 2026 (90746)

Code for the data points upstream of ZM2 attached. The measured beam widths and their corresponding position are listed in the script. The real raw data with the screenshots from the beam profiler UI is attached to the main log. 

Non-image files attached to this comment
eric.oelker@LIGO.ORG - 16:48, Friday 26 June 2026 (90781)

I wanted to try to get an idea of what sort of astigmatism we're seeing on the FC path.  I was able to get good fits of Begum's data right after ZM1.  This indicates that the astigmatism coming right off of the VIP looks quite good ( 99.9 +/- 0.1% overlap between X and Y).  Plots of the fits are attached for each lens position.

 

I wasn't able to get particularly convincing fits of the data after ZM2.  The points are several Rayliegh ranges away from the waist and I found that the fits were quite sensitive.  I could get answers anywhere between 98%-100% mode overlap between X and Y depending on what parameters I used in a la mode for the seed waist.  Someone might be able to do a more sophistocated fit of the data, but I think one would want to measure closer to the waist to better constrain the fit and get a more precise estimate of the astigmatism added by ZM2.  

Images attached to this comment
Non-image files attached to this comment
eric.oelker@LIGO.ORG - 12:09, Wednesday 01 July 2026 (90853)

I've been reading through the design document about the FC path and ZM2.  One thing imay be important to note when making projections about the correct strain gauge setting for ZM2:  According to the design document the mode matching is quite sensitive to the exact value of the FC1 AR surface ROC.  One might find that, if we change our assumption about the ROC for S2 of FC1, our target strain gauge setting for ZM2 changes significantly.  In fact, the discussion makes it sound like most of the point of having ZM2 be adjustable was to compensate for our uncertainty in the ROC of S2 for FC1. 

 

See LIGO-T1900649 and the discussion on Page 18 as well as Figure 10.

begum.kabagoz@LIGO.ORG - 11:55, Thursday 02 July 2026 (90879)

A note on the FC1 ROC sensitivity question: a scalar FC1 ROC sweep alone would be only partially informative, because the projection also depends on the FC-path distances and the voltage-dependent x/y astigmatism of ZM2 (see plots for the mode space and projected overlap with eigenmode from the original log). This is why the original log interpreted the projection as approximate and stated that the final optimization should be done empirically.

The more meaningful check right now is therefore a return-beam measurement between ZM1 and ZM2 while stepping the ZM2 strain-gauge setting. This can be done by placing a beam splitter between ZM1 and ZM2 and matching the return beam to the input beam by varying ZM2 curvature. 

The modeling exercise could be a nice little real life vs model analysis later on. 

H1 SPI
jeffrey.kissel@LIGO.ORG - posted 16:27, Friday 15 May 2026 - last comment - 11:26, Friday 26 June 2026(90253)
SPI Pathfinder ISIK Transceiver Status
J. Kissel

Quick summary of status and things done before the weekend:
    2026-05-14 
       - Secured new D2400143-v6 breadboard to 1"Dx6"L posts
       - w/ J. Freed Helicoiled most holes
  
    2026-05-15
       - Finished helicoiling and confirmed all holes have helicoils.
       - Brought out IXM100 mounts that are to replace CVM100 mounts, confirmed left vs. right-handed assignment
       - Fit-checked (success!), then installed new version of 45 deg periscope adapters to M_M4 and M_M5 mounts. 
       - Aligned periscope adapters as best possible by eye
       - Migrated over and re-cabled up all photodiodes per wiring diagram and cable routing defined in LHO:90228.
       - Migrated R_F1 and M_F1 fiber collimators, confirming and adjusting alignment of slow-axis w/ vertical flat.
       - Re-connected optical fiber input to each collimator.
       - Re-introduced beam on to breadboard confirming that NPRO and Laser Prep Chassis still work as good as we left it. 
       - Measured raw power from R_F1 and M_F1 fiber collimator output using S121C power meter.
       - Aligned R_F1 and M_F1 fiber collimator output using 
           - D2500080 alignment iris target assemblies
           - D2400143-v6 holes 89 + 101 for R_F1 and 101 + 80 for M_F1 and 
           - S121C behind the "far" iris, maximizing power throughput.
       - Migrated R_P1 and M_P1 thin-film polarizers.
       - Measured P-pol (TRANS) and S-pol (REFL). 
       - Migrated D_R_P1 and D_M_P1 beam dumps.

Optical power going into the mock PSL input fiber is ~195 [mW] as we left it, and internal laser prep chassis reads 7.8 [V] implying that input power to the chassis is the same 173 [mW] we set it to, to match the real PSL input (see LHO:89693).

RF power on power monitors from prep chassis are as expected, in the 750 +/- 10 [mV] range.

Measuring power with our trusty S121C with ThorLabs PM100-D readout (confirmed to be measuring at 1064 [nm] wavelength):
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 16:28, Friday 15 May 2026 (90254)EPO, SPI
Josh and I hard at work doing helicoil science. Photo credit: Ryan Short.
Images attached to this comment
jeffrey.kissel@LIGO.ORG - 11:26, Friday 26 June 2026 (90776)
A belated photo from the day that both D2400143-v4 and D2400143-v6 were side-by-side, right before the helicoiling and transfer of components began.
Images attached to this comment
Displaying reports 101-120 of 88272.Go to page Start 2 3 4 5 6 7 8 9 10 End