TITLE: 06/16 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: 14mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:

Tuesday!!

LVEA IS LASER HAZARD

J. Freed, J. Kissel, TJ. Shaffer, B. Weaver, M, Pirello

Continuing from 90581 (Notes are stored here).Today we completed all of the inside optical fiber install, Got our first light out of SPI, Managed to send it from one ham table and back again.  As well as align the reference interferometer to produce a beat note with decent efficiency (~75%).

We also connected the HAM2 wiring from HAM2 feedthrough to TIA to CDS system.

In order we did:

• Meas fibr and Ref fiber are installed including spools.
• connected the HAM2 wiring from HAM2 D4- F10 feedthrough to TIA Chassis to CDS system.
• Got laser light out on ISIK
• Realigned the SPI reference interferometer and got a beat note with an efficiency of ~75%
• Realigned the MEAS beam path and managed to get light on both of SPIs QPDs
• HAM2 was unlocked and light is still on the QPDs

SPI_QPD_HAM2_Unlock.png  Shows a screenshot of ndscope screens of the QPDs. Note the purple areas. The HAM2 unlock did show an effect on ISIK QPD (QPDB) but QPDA was insensitive to the Unlock. 

Ryan S, Madi, Camilla, TJ consult. 

After the new lens holder for the B:L2 aperture was added, today we unlocked the OPO SUS. It was hanging freely but the +X side looked very low so we spent some time rebalancing it. Attached photos are of current +X, +Y and -Y clearances [add later]. We moved one weight and the dog clamp being used as a weight and removed two very small weights from [add later]. 

However, after rebalancing the beam is not well aligned, it is the the -X of the ZM3 iris, not retroreflect well in yaw (<1mm off) and also off in yaw at the ZM4 iris. There is beam getting to the SQZT7 PD, but it is clipped on the OPO as the light level is oscillating on the IR PD. 

Plan going forward is to check OPO SUS TFs and then decide whether to repeat our alignment again. Alternative might be to rebalance again in a way that gives us a closer alignment. 

WP13294 h1susbs running BBSS model, restore h1suslo12

Erik, Oli, EJ, Jonathan, Dave:

h1susbs was returned, via puppet, to h1susb2h34's model list. Oli created a new h1susbs, with the old BSFM model replaced with the BBSS model which had been running on h1suslo12. This was not a straight move, changes were also made including restoring all the IPC channels.

h1suslo12 was returned to LO12 duties, restoring this model to what it was before it became the temporary BBSS model.

Because DAC channels were being swapped between models, and the DAQ needed to send a new model's data block, we decided to fence and reboot h1sush2h34 to make these changes.

Jonathan restarted the DAQ. Both broadcasters needed a BBSS to BS name change.

CDS is once again running with zero IPC errors.

With the work done in HAM2 done and the table rebalanced (alog90577), I unlocked the HAM2 ISI with Betsy's in the D,C,B,A order. The door cover on the -Y side was very tight and we had to loosen and wiggle it a bit to get enough slack for the arm and clip to hold. The +Y side was exactly the opposite and was billowing inches away, so we left the arm off.

Oli took the ISI to Damped and we'll see if that helps out the SPI team.

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

LVEA IS LASER HAZARD

HAM2 ISI has been unlocked and it is in DAMPED

LOG:                                                                                                                                                                                                                                                                                                                                                                                                                                                                

Tested the laser power through the fiber chain (90 ft out of vac fiber cable -->feedthrough-->in vac splitter) using a Ophir power meter. The measurements were taken by orienting the fiber to shine into the power meter.

Directly from laser: ~19.8-20mW, at max 21.5mW

After 90ft fiber:  ~17.5-18.2mW, at max 19.56mW

After the feedthrough: ~14.8mW, at max 15.7mW

After Splitter: ~5.6mW or 4.86mW depending on which side of spliter, at max 5.9mW

Note that the measurements taken after the splitter might be a bit low because the angle of the power meter wasn't the best, I'll re-measure it tomorrow. 

I've gotten the fiber mircoscope from Jeff, so I'll check the fiber core of the feedthrough and the splitter and post photos

Tomorrow I'll hook up the splitter to each of the HoQI and see if the fringe visability is the same when in the fiber chain as when getting light directly from the laser. 

Ryan S, Elenna, Camilla. Continued from 90609. 

Checked the SQZT7 iris, beam was nicely centered. Ryan then moved SRM/ZM6 to try to center AS_AIR camera and AS_, this did not work. Left as Friday settings. OMC was saturated, on e we cleared SUS e we cleared SUS histories, we lost light onAS_A and B. Ryan moved OM1 and OM2 back to their Friday locations using the sliders. Then turned on DC centering loops 3 and 4 until centered and then OMC ASC to center beams on al diodes, apart from AS_C. See attached for alignments and sliders. OMC was not saturating. 

For scan that worked well, we set up OMC PDs as Keita suggested (worked only with AW filters off), attached. Gerardo turned the whole corner purger air off. We decreased scan time to 100s. We left the OMC ASC running.  Attached is what the main and mode mismatch peaks looked like. We have <2% mode mismatch. I expect we should be happy with this as in O4 we measured only >2%. We could later repeat with different ZM4/5 PSAMS settings to try to improve.

Saved to /opt/rtcds/userapps/release/sqz/h1/Templates/dtt/OMC_SCANS/June15_PurgeOff_2026_OMC_scan.xml

*calculated with TEM02 / (TEM00 + TEM02) 

h1susbs is now fully running the BBSS and everything that was previously on the h1suslo12 model was moved over. The channels that were previously called SUS-BBSS are now called SUS-BS. Old SUS-BBSS data can still be grabbed by using nds2.

I unpaused the BS guardian and took the suspension to DAMPED. It is damping.

/opt/rtcds/userapps/release/cds/h1/medm/SITEMAP.adl
r35324
- Removed BBSS(temp) and updated link for BS

/opt/rtcds/userapps/release/sus/h1/medm/susbs_overview_macro.txt
r35325
- Copied over susbbss_over_macro.txt and updated optic name and dcuids

/opt/rtcds/userapps/release/sus/common/medm/bbss/SUS_CUST_BBSS_QOSEM_OVERVIEW.adl
/opt/rtcds/userapps/release/sus/common/medm/bbss/SUS_CUST_BBSS_M3_OPLEV.adl
r35327
- Removed temporary 'lo12' filled in optic names and replaced with $(optic)

/opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSLO12.txt
/opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSBS.txt
r35326
- Copied over previous BBSS filter files into H1SUSBS (with name change from BBSS -> BS)
- Committed updated H1SUSLO12 filter file (which has no filters loaded, which is correct)

/opt/rtcds/userapps/release/sus/h1/burtfiles/h1susbs_down.snap
r35329
- Copied opt/rtcds/lho/h1/target/h1suslo12/h1suslo12epics/burt/safe.snap over to /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susbs_down.snap, which due to symlinks gets linked over to opt/rtcds/lho/h1/target/h1susbs/h1susbsepics/burt/safe.snap
- Loaded BS sdf from safe.snap and 'reverted' changes to get the model to put in the correct settings

Test fit the baffles on the CRS in the H2-PSL (photo of one on CRS below). There aren't any type 06 dog clamps (D1100640) which are called for in the assembly (D2600161), so we are using type 05 and type 09 instead. These were also tested to make sure they could be used to attach the CRS to the table. 

The plan for today is to test the fiber chain in the H2-PSL to make sure enough power gets through the HoQIs when in chamber

TITLE: 06/15 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: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s 
QUICK SUMMARY:

Dust counts high in optics lab even though wind is low

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 59515. The 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.

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.

TITLE: 06/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
CRS Team spent some time working in the H2 PSL. 
I beleave some OMC work was done near HAM 6.
The SQZr team did some quick SQZr work before Begum left.
VAC team started heating up the RGA , and has put up some caution tape. 

LOG:

[Begum, Sheila]

Alignment: After the preliminary alignment work yesterday, see Camilla log 90593, we proceeded to attack the OMC scan problem step by step, starting with alignment. We aligned ZM4 and ZM5 using the two irises on SQT7 table as references. ZM4 was used for the first iris just past the periscope, ZM5 for the further iris. We reverted ZM6 and SRC alignment to O4 slider settings.  Then we used ZM6 and SRC to align the beam on AS-AIR camera and AS_C QPD. 
Then we turned on AS_A/B DC centering servos (actuators: OM1 & OM2), and OMC QPD DC centering servos (acutators: OM3 & OMC). This saturated the OMC_M1 T2&T3 outputs. AS_A/B servos align the input beam to the right pos/ang on OM3 and QPD servos should be able to align this beam to the OMC without saturating. While HAM6 is isolated and HAM7 is locked, HAM5 isn't isolated. Aligning the beam to the SQZT7 irises should condition the beam out of HAM7 well, so perhaps the issue is the HAM5 nonaligned state. (I did try to reset the watchdog, it immediately went back to tripped state.) 
Then we tried turning on only the OMC QPD DC centering loops, without the AS_A/B loops, and this worked! OMC sus is no longer saturating, and the mode scans look more reasonable, see attached preliminary scan. The beam is also bouncing a lot less on OMC QPDs compared to when the AS_A/B centering loops are on. 

Setting the scan: Conducting OMC scans in air is no easy feat. The PZT scan should be quick enough to not inherit the beam jitter, but also slow enough to properly sample the maxima of peaks, without running into anti whitening problems. During new HAM6 installation at LLO, this meant turning of HAM6 and corner purge as well as cleanrooms nearby (vertex cleanroom was okay to leave off, although vertex purge needed to be turned off). Keita suggested installing a PD in the OMC trans camera can, and using such a (non-whitened) PD for the OMC scans. 
Screenshot of the sliders for the preliminary scan we took today, plot showing the magnitude of the second order mode, and the fundamental mode, with these awggui pzt scan settings. Once a reliable measurement flow is achieved, we would like to automate ZM4/5 psam scan + OMC scan to estimate the achievable SQZ-OMC & SQZ-IFO mode matching limits. 
 

The ETMY BRS seems to be continuously ringing up. I've tried to make the changes to the thresholds which was the previous fix outlined in 87634 for the same BRS, and will check back in on it later to see if just increasing the thresholds helped at all.

Changed thresholds:

H1:ISI-GND_BRS_ETMY_LOWTHRESHOLD 800-->2000

H1:ISI-GND_BRS_ETMY_HIGHTHRESHOLD 2000-->4000 Changed

Additonally I changed the ETMX BRS drift control to 6.00V and the ETMY BRS to 2.00V to try and better center them

WP13311 Check production first 20bit-DACs

FRS38169

For the five production front ends which have a 20bit-DAC sharing A1 with an updated time card, we have either verified that there is no problem seen (h1susb2h23, h1iscex) or we identified and fixed the problem by either shifting the ADC/DAC cards (h1sush7, h1oaf0) or downgraded the timing card (h1cdsh8).

Attached is a snap shot of our working spredsheet. This will be cleaned up and put into DCC.

TITLE: 06/12 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: 13mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:

It was requested that I try to trend the Oplevs this morning, but the BS SUS screen is full of white boxes that claim their channels don't exit when NDscoped. Tagging CDS. 

I did however find the Input Pointing Trends button which gave me the following: 
IMs 
BSCs (No motion on the BS channels here though which is some SUS-picious BS)
MCs
PRMs

 

J. Freed, J. Kissel, J. Wright, T. Sadecki, TJ, Shaffer,

Continuing from 90558 (Notes are stored here).Today we completed all of the outside optical fiber install, Feedthrough install, as well as BnK Hammer of ISIK. 

We also had some trouble connecting to the picomotors through CDS but Fil and Co. seems to have fixed the issue.

In order we did:

• BnK Hammered the assembly to confirm secure to ISI and resonances are sufficiently high (~200Hz)
• Finished last PD and Pico bus cable connections to D6 feedthru
• Installed D4 feedthrough pannels
• Installed in chamber fibers but still need to be routed and respooled
• Checked and installed the fiber optic chain from PSL through SPI prep to the HAM 3 D4 feedthrough. This includes
  • SPI Prep mointor channel checks.
  • Optical network power budget (will be added to a separate alog).