Search criteria
Section: H2
Task: INS
B. Weaver, J. Kissel WP 12109 Betsy, myself, and several others are looking to propose redlines to the WHAM3 flange cable layout (D1002874) in prep for O5 (see T2400150 for DCN and discussion there-of). However, in doing so, we discovered that the flange layout may have double-counted the shared cable for the MC2/PR2 M1 (top) RTSD / T1T2 OSEMs. Other drawings (e.g. the Cable Routing D1101463 and the wiring diagrams D1000599) indicate "yes, there's an extra 'SUS-TRIPLE' entry somewhere between the D6 and D3 allocation," but we wanted to be sure. As such, Betsy went out to HAM3 today and confirmed that YES the MC2/PR2 M1 (top) RTSD / T1T2 cable, labeled "SUS_HAM3_002" in the wiring diagram or "SUS-HAM3-2" in real life, does come out of D3-1C1 and *not* out of any D6 port, and thus we validate that D6's list of 4x DB25s to support the 'SUS-TRIPLE' (i.e. MC2) in D1002874 is incorrect. Pictures attached show the D3 flange, and highlight the SUS-HAM3-2 cable at the flange going to D3-1C1, and then the other end of that cable, clearly going into the MC2-TOP/PR2-TOP satamp box in the SUS-R2 field rack (S1301887).
J. Kissel, S. Koehlenbeck, M. Robinson, J. Warner The LHO install team (Jim, Mitch) -- who has experience installing in-chamber fiber optic systems -- have reviewed the two options put forth by the SPI team for optical fiber routing from some feedthrus to the future location of the SPI follower breadboard on the -X side wall of the HAM3 ISI using Eddie's mock-ups in D2400103. Both options (WHAM-D8 or WHAM-D5) are "evil" in several (but different) ways but we think the lesser of the two is running the fibers from D5 (the currently blank flange underneath the input arm beam tube on the -X side of HAM3; see D1002874). In support of this path forward, one of the primary evils with D5 is that access to it is *very* crowded with HEPI hydraulics piping, cable trays, and various other stuff. Here I post some pictures of the situation. Images 5645, 5646, 5647, 5648, 5649, 5650, 5651 show various views looking at HAM3 D5. Images 5652, 5653, 5654 show the HAM2 optical lever (oplev) transceiver, which is a part of the officially defunct HAM Table Oplev system which -- if removed -- would help clear a major access interference point.
Some details.
Grounding.
I and Jim checked the ground loop for everything on A6 flange (ISC) again. I disconnected in-air cables from the feedthrough, put a DB25 breakout board on the feedthrough and tested the connection between pin13 (in-chamber shield) and the chamber ground.
The only genuine problem we found and fixed was a ground loop for ASC-AS_C QPD cable. Jim rerouted that cable that was bunched up under the ISI and it was fixed.
Also, when testing ground check for F1(OMC DCPD)/F2(OMC PZT)/F3(OMC QPD), disconnecting these three isn't enough. Don't forget to disconnect 3MHz cables (D4-2B1 and D4-2B2), otherwise there's this path which gives you anything from a few hundred kOhm to 4MOhm. We wasted some time because of this.
F1 in-chamber shield <-> DCPD preamp signal ground <-> RF cable SMA shield <-> SMA Rack ground -> chamber ground.
After disconnecting RF cables, don't forget to torque them using a dedicated torque wrench for SMA.
As of now, in-air cables on D6 are as follows.
D6 feedthrough number |
In-air Cable | Description |
F1 | ISC-307 | OMC DCPD |
F2 | ISC-409 | OMC PZT HV |
F3 | ISC-404 | OMC QPDs |
F4 | ISC-232 | OMCR DCPD |
F5 | ISC-233 | ASC-AS_C QPD |
F6 |
None |
Used to be OMCR pico, old ISC-235 cable was removed. No cable in chamber either. |
F7 | ISC-234 | AS_C pico |
F8 | ISC-317 | ASAIR Beam Diverter |
F9 | T-SAMS | OM2 heater |
F10 | ISC-236 | OM1 BOSEM |
F11 | ISC-237 | OM2 BOSEM |
F12 | ISC-238 | OM3 BOSEM |
AS_AIR beam position check
TJ and Tony installed viewport simulator on the +X door after adjusting the hoop positions on the real door.
From the picture I previously took (ASAIR_beampos.jpg), I know that the ASAIR beam position is about the radius of the BDV optic toward -Y direction at the BDV when it's open.
So I placed the camera so that the lens is co-axial with the line connecting the center of the ASAIR beam position by the BDV and the center of the ASAIR-AS_C splitter as good as I can (ASAIR_likely.jpg). Green cross is where I think the beam will be by BDV. Cyan line is the center line for ASAIR-AS_C BS. (Red line is the center line of the lens just so you know how big the parallax could be.)
Anyway, as far as the centering on the BS is not terrible, the beam will come out w/o any problem.
I also repositioned the camera to assess the worst case scenario (the beam will be very close to the left edge of the BS and therefore comes closest to the right edge of the viewport given the fixed position of the ASAIR beam by the BDV), and the beam will still come out of the viewport.
OMC TRANS beam check
We haven't done anything as there's no reason for a big change except that we changed how OMC ISC cables are routed inside OMCS, and that we removed OMCS suspension offsets. Just took one picture through the +Y hoop of the viewport simulator.
Table layout pictures
For posterity.
Couldn't take a good DCPD picture
I tried to take a good picture of at least one of the OMC DCPDs through the space between OMC shroud panels and through the OMC breadboard itself but I couldn't. The view is there but lighting is not (DCPD.jpg).
HAM7:
HAM6:
What's yet to be done.
Following up on Keita and Koji's converation, Sheila and I took a closer look at the OMCR DCPD in HAM6 to see if there are any cracks. We could not positively identify anything resembling a crack on the DCPD (images attached). We could also not see where the DCPD was hole punched. What is the typical size and placement for these holes? More images here. The DCPD is definitely quite dirty. We compared against some DCPDs of a similar design in HAM7 and can confirm that the OMCR DCPD is visibly much dirtier than those.
We also inspected the OMCR shroud input aperture for signs of pitting and other damage. There is no damage to report. We spent some time looking at the output aperture because we saw some potential damage along the aperture edge. After taking photos at various different angles to rule out reflections, we determined that apertures are fine, save for the occasional speckle on the shroud and the rouge edges likely left behind by the machining process. Images attached. More images here.
Today I took pictures and it really seems that the glass was cracked.
1st attachment is a cellphone picture, you can see something at the right edge. That thing never goes away regardless of your eye position and lighting.
2nd is a close up view from the side using a dedicated camera.
It seems to me that the front and the back surface of the glass each developed a scallop-shaped crack. I couldn't picture the hole in the can, not sure if this was actually punched or not, but I think the cracks are real.
You cannot see anything like this on the left edge of the PD (3rd attachment).
Sheila noticed that the two dots inside the PD can where the PD cables attach on this PD are vertically aligned. In the HAM7 SQZ PDs the dots are horizontal, e.g G:PD1, H:PD1, F:PD1. Is this fine?
Hi Camilla,
Not 100% certain that I know what you mean by "dots." I am assuming you are referring to the leads that penetrate the diode can. Either way, these are not quadrant photodiodes, so the rotational alignment of the photodetector element should not matter. It could be that you are comparing this device to other devices that use different models of photodiode, but again, the rotation of a single element diode will not matter.
Spare PD looks similar.
During installation I thought that we didn't have a spare OMCR DCPD, I somehow mis-remembered that everything we didn't use was sent to LLO but that wasn't true. So I took pictures of the spare too, and things look about the same.
1st picture was shot with a cellphone and an LED flashlight. It's not particularly difficult to take this kind of picture but note that the flashlight should be much brighter than the ambient light, and you should place flashlight as well as the camera such that reflection from the glass/metal/pd won't come into camera's view. You also avoid reflection of bright/white background coming into camera's view. You need to experiment.
2nd and 3rd picture shot with a stand-alone camera and a macro lens show some particulates are closer to the sensor plane (2nd picture) but more are on the glass plate (3rd picture). Cleaning the outer surface didn't change things so I assume these are mostly on the inside surface.
4th and 5th picture show the structure that looks similar to what we observed for the one in HAM6. Again this might be crack, but an alternative explanation that came to my mind is that a hole was successfully punched, which made protrusion of jagged metal edge of the hole into the can, and we're seeing that through a non-flat glass (it's apparent that the glass is not particularly flat around the edge, look at the last picture).
For inventory purpose:
PD-cable-enclosure assy |
Component: PD-cable |
Component: enclosure | Status |
D2100381-V2-S2200257 | D1600079-V3-SN1 | Spare | |
D2100381-V2-S2200258 | D1600079-V3-SN2 | WHAM6 |
(I'm 100% sure which component is in WHAM6. I couldn't find any record of which PD-cable-enclosure assy comprises which component, I just assume that younger components belong to younger assy.)
We calibrated OMCR DCPD using Pcal integrating sphere. Numbers are to follow. (But note that Koji is worried that maybe the cover glass for that PD was cracked when they punched a vent hole on the diode case.)
We fixed the beam dump that was too high.
After that, we investigated the DCPD signal ground (alog 65081) and we think we know the cause of the problem but we don't have an easy fix. We'll leave it as is.
It seems that one of the cables (either PZT or QPD) that goes to the OMC breadboard was touching the OMC shroud panel. We'll revisit that in the morning, adjust that, then confirm that the laser is still hitting the OMC QPDs. If not we'll realign.
It seems that we have ground loop problem (PZT shield is connected to the chamber). We'll revisit that at some time, maybe in the morning, or maybe after we're done with the injection from HAM7 to HAM6.
This is a belated followup of OMCR DCPD calibration. Following channels were calibrated.
Channel | meaning | Where | Caveat |
H1:OMC-REFL_A_LF_OUT_DQ | Power upstream of 99:1 splitter [mW] | Frontend |
gain=1, FM4/5/6/9 always ON. FM7/8 should be the inverse of H1:OMC-REFL_A_DC_GAINSETTING (e.g. enable "-20dB" if the gain is 20dB). If you set the whitening gain to anything other than 0dB, use FM10 to define an appropriate compensation gain. |
H1:OMC-REFL_A_DC_POWERMON | Power upstream of 99:1 splitter [mW] | Beckhoff | |
H1:OMC-REFL_A_DC_POWER | Power actually falling on the OMCR PD [mW] | Beckhoff |
I made the following changes for H1:OMC-REFL_A_LF filters, and coefficients were loaded to H1OMC.
Old | New | |
FM4 ("cts2V"), supposed to be 40/(2**16) |
gain(0.0006105) |
gain(0.00061035) (doesn't matter much) |
FM6 ("W/A"), supposed to be 1/responsivity. |
gain(6.5) | gain(17.15) |
FM9 ("inv(99:1)"), new filter, supposed to be the inverse of the transmissivity of 99:1 |
NA |
gain(104.17) |
Following is a table of parameters for Beckhoff:
old | new | |
H1:OMC-REFL_A_DC_OFFSET | -0.0025 | -0.0025 |
H1:OMC-REFL_A_DC_GAINSETTING | 20dB | 20dB |
H1:OMC-REFL_A_DC_RESPONSIVITY | 0.16 A/W | 0.058 A/W |
H1:OMC-REFL_A_DC_TRANSIMPEDANCE | 2000 Ohm | 2000 Ohm |
H1:OMC-REFL_A_DC_SPLITTERR | 100 % | 0.960 % |
Some details:
All components that are supposed to be installed in HAM6 in this vent were installed. I decided that the centering of the aux laser beam on the 1st iris was not great after all (1mm or so in YAW), so I realigned the laser to two irises carefully. This didn't have a huge impact on the downstream alignment, but it had some impact. Anyway, ASC-AS_C, WFS, OMC itself and OMCR path were readjusted.
See layout1, layout2 and layout3.jpg for the relevant paths including (but not limited to) things that were installed.
There are some caveats, namely,
Also, this is not a caveat, but there are three ghost beams generated by the OMCR DCPD because the glass isn't removed from the PD case.
Tomorrow we'll attack the above caveats in the morning and hopefully move on to OMC DCPD and PZT grounding investigation.
Hi Keita,
Is the OMCR DCPD punched from the side for venting? The glass cap gets cracked by the punch if the hole is too close to the window. The PD photos may be showing something white like a crack at the right side of the element. I had that problem for the DCQPDs in the past.
All of these are puched at Caltech, I believe. It's hard to interpret white things because it could easily be the lighting. We'll look closely.
(Weaver, Kissel)
In HAM1, today we:
Next up:
I went to the staging building to fetch a 50:50 P-pol IR splitter and saw Betsy and Srinath baking FC cavity tubes. Here are some pictures.
1st: They can bake two sets at a time and each set comprises two sections connected together. There are 48 sections (i.e. 24 sets), they need to be baked at 110+ Celcius for ~3 days, so this has been a long laborious process which is still ongoing.
2nd: All sets are pumped down before and while baking.
3rd: They already wrapped the heater element around the tube and they're ready to put the insulation material on.
4th: Insulation material is all velcro-ed up (except that it's not, Betsy won't be ready to turn the heater on until the joint in the middle is also covered up by a narrower insulation strip).
J. Kissel Following the measurement & fitting (LHO:61313), and subsequent modeling of systematic error impact of various levels of compensation accuracy (LHO:61729), I've installed the updated compensation (in the ETMX_L2_COILOUTF filter bank) for the analog frequency response change to the H1SUSETMX PUM (or "L2") driver (described in E2100204, installed in Dec 2021). While the modeling effort (LHO:61729) only discussed State 3 for brevity, and "only" the analog low-pass filter in State 3 changed, I also installed updates to the compensation for the Acquire ON and Acquire OFF response as well, because previous measuring / fitting attempts (47166) were flawed: the measurement was done with the AOSEMs still engaged, leaving the AOSEM inductance zero in play which confused the fitting routine. Let's be serious, I really just didn't know what I was doing and I was rushed. Now I'm far more confident in my results because I understand the system much better, and I had the time to calmly measure all the pieces of the puzzle independently. The differences to State 1 and State 2 are small, but now *any* state we choose to run in during observation will be supremely compensated (at the 0.1% / 0.1 deg level, at least below 1 kHz), rather than just "OK" compensated (at the 1% / 1 deg) level. In addition, all the switchable compensation filters (the "Sim"s in FMs 1-3 and "Anti"s FMs 5-7) have all been converted from "Zero History" input and "Immediately" output to having their input "Always ON" and output set to "Zero Crossing." This feature of the coil driver switching had been lost in the sands of time: having recently re-explained "how the switching and compensation works and why" to Brad, I remembered a slide from a 2009 presentation of mine, G0900112 Slide 9 (be sure to download the .pptx as the animations are critical to the point), and the last bullet on there covers that, under this "SimDW," "AntiDW," and "DW" "dance of the de-whitening plum fairies" model of compensation, the switching should be done on a Zero Crossing in order to minimize glitching that may result from the large, high frequency, gain changes between State 2 and State 3 when we run "LOW NOISE COIL DRIVERS" after achieving full IFO lock/resonance on our way to NOMINAL LOW NOISE. Finally, for the first time ever, and motivated by the modeling work, I've included an AntiAOSEM filter, which compensates for the non-negligible ~855 Hz zero that arises from the coil's inductance. This filter remains ON at all times, regardless of the state of the coil driver. As such, because there's no intent to ever switch this filter on the fly, I left the input and output filter switch settings as "Zero History" and "Immediately." Note: I've left the L2_COILOUTF gains as is, bu these will need to be retuned, since (a) the measurement method (LHO:11392 and LHO:9453). involves driving a line a ~3 or 4 Hz, and there was significant frequency-dependent systematic error in the compensation around that frequency which was unrelated to the actual overall gain imbalance, and (b) there're brand new R and C electrical components in the State 3 path, so I anticipate some ~1% level change in the over all gain (and the coil balancing method claims to achieve 0.1% level accuracy in compensating for gain imbalance). Attached is a screenshot of how the new filter bank looks when the BIO_REQUEST for L2 is set to State 2. Also attached is a screenshot of me accepting the turning ON of FM9, which is where I've chosen to house the AntiAOSEM compensation. Also, also attached is a new version of the State Machine Diagram, conveying which state has which analog response, and corresponding the compensation scheme. Finally attached is a list comparing old vs. new filter poles and zeros.
I used a flashlight (through the OMC breadboard) to aim at the DCPD in reflection of the 50:50 BS as best as I can , and DCPD_B showed much stronger signal.
This means that:
See cartoon, this is a top view looking through the glass OMC breadboard (optical components are under the breadboard).
Wiring diagram is here D1900511-v7 with ISC-R5 on pg 21.
The O3 DCPD chain is documented here, D1300502, which also shows A in transmission and B in reflection.
Maybe this isn't the best place to share this, but life can be frustrating as a deuteranope. Matplotlib has an easy to use colorblind friendly style built in. It can be invoked by adding the line plt.style.use('tableau-colorblind10') before starting to setup your plot (if you've used the usual import matplotlib.pyplot as plt). Maybe this is common knowledge, but I just found it while working on a script.
The first plot is one of the plots produced for the weekly CPS noise monitoring famis for ITMX. The second plt is the same one, but I added the colorblind style to the script. For me, on the first image the H3 and V1 sensors on both subplots are almost the same color. It's especially difficult to go between the legend and the traces on the first plot. Reading these plots on a backlit monitor make this even harder. More than a 4-6 traces, I have a really hard time telling which line is which.
On the second figure, it's much easier. Add in some different linestyles and thicknesses, and everybody's pretty plots can be appreciated by more people.
Nice one! Tagging all the groups, so some folks get emails about this dueteranope-approved color palate. Now we just need the equivalent for matlab!
VOPO relocation was very smooth overall.
VOPO spacer (picture 1) was put in place in HAM7. The spacer didn't have any of the helicoils for 1/4-20, so we had to put them in place.
VOPO platform was moved to a lift cart, wrapped in C3 cover (2nd picture), moved to a big clean roon in the LVEA and unwrapped (3rd pic).
4th pic shows the VOPO attached to the installation arm with the tooling. (Note the aluminum spacer between the VOPO and the lift cart. This is the same spacer that was used when we uninstalled VOPO from HAM6.) We had to remove two balance weight bars at the side to lift the VOPO high enough.
After it was placed on the spacer, three persons needed to push and pull it a bit to set the yaw angle right while the VOPO base plate still contacts with two alignment pins on the spacer.
Georgia went in to HAM7 and used dog clamps for +Y and +X sides (5th pic) , I did -Y and -X sides. Two balance weight bars were reattached at this point.
6th and 7th pic show the newly installed VOPO in HAM7.
We pinched one long in-vac cable between the installation arm and the -Y side door flange while trying to move the installation arm out of the way. Externally, the insulation sheath looks somewhat deformed (8th pic) but it's not clear if there's internal damage. There's another cable in the 8th picture next to this cable, it shows similar deformed-looking sheath at similar location but that one wasn't pinched.
DCC and SN of this are D1000225-230" #1, S1104241 (pic 9 and 10).
Travis also took a lot of pictures.
More baby pics for Zucker et al.
Bonus picture: I happened to walk up to the crowd of successful installers right as they were finishing up. From left to right (including in chamber!): Camilla, Scott, TJ, Keita, and Georgia (in chamber). Travis was standing next to me -- but the pictures above show that!
Beautiful! Congrats!
Retroactively tagging EPO.
[JenneD, SudarshanK]
We lowered the ASC DHARD Pitch Gain to see if we can actually stay locked with smaller gain. We lowered the gain by a factor of 3 (from -30 to -10). The interferometer happily stayed locked but we didnot notice any significant change in the DARM spectrum (Attachment 1). During this time, the purge air/Kobelco was turned on as part of Tuesday maintenance, which might elevate the DARM noise floor but should be similar throughout our study.
We also made noise injections at these two configurations via DHARD_P_EXC. The sensor corrections was turned off during one of those injections but we didnot see much difference between the two.
At next comissioning opportunity, we will probably try to measure sensing function at the lower gain value because we expect the sensing function to change (move towards "normal") with lower gain.
Evan G., Keita K., Jamie R., Dave B., We tested the transient hardware injection infrastructure to make sure that we could still run transient hardware injections. While the IFO was not in low noise, we successfully made a DetChar set of injections. These were injected starting at 1233537100. We saw the injection on the TRANSIENT filter bank and on the PCALX RX PD. The STATUS did change from 3 to 40 and back to 3. The value was displayed weirdly by DTT, ndscope and dataviewer, possibly because it is a uint32 data type, but we believe it is doing the right thing. The obs_channel_name variable in INJ_TRANS.py had to be updated to "GRD-IFO_INTENT".
Since some of this work involved redefining the directory structure on h1hwinj1, I have recreated the RELEASE sym link to point to preO3_H1 and have restarted the CW injections to verify things still work, which they seem to do (see attachment).
We connected the 5-way coax to TNC adapter that Fil has made to the chamber. 5-way coax cable assignment is in D1300466.
cable 1 | cable 2 | cable 3 | cable 4 | cable 5 |
Single ended DC | Test in | Test out | RF LOW (9MHz) | RF HI (45MHz) |
We measured the TF from cable 2 to cable 4 while cable 5 was terminated (attachment 1), then from cable 2 to cable 4 while cable 4 was terminated (attachment 2) and both made sense.
The problem of this configuration is that shells of TNCs are touching with each other (attachment 3, note that cable 2 and cable 5 are terminated). We put cable 1, 2, 3 and 5 inside different fingers in a glove to insulate things from each other (attachment 4).
For the moment 9MHz connector is exposed but it's not touching any surrounding metals.
For a short while we locked MC with 200mW and measured the coherence between REFL_A and REFL_B 9MHz, and it also made sense (see Georgia's comments).
After ground loop checks we will isolate these with heat shrink.
I'm attaching the power spectra of, and coherences between, LSC-REFL_A_RF9_I, LSC-REFL_A_RF9_Q, LSC-REFL_B_RF9_I, and LSC-REFL_B_RF9_Q, with and without light on the photodiodes.
Blue, red, green, and brown traces are with the IMC offline.
In the top plot cyan and pink are REFL_A_RF9 with the IMC locked with 200 mW, orange and black are REFL_B_RF9. Signal is seen on both photodiodes, there is a gain difference between them.
Bottom left plot shows REFL_B_RF9_I and Q coherence with REFL_A_RF9_I; bottom right plot shows REFL_B_RF9_I and Q coherence with REFL_A_RF9_Q. Higher coherence is seen with REFL_A_RF9_I, not surprising since REFL_B has not been phased.
Keita, Craig We checked all the LSC PDs while locked in nominal low noise with normal modulation depth settings. Remember that we multiply the scope output by 14 to get the actual demodulated signal, since the demod board picks off -23 dB for the RF monitor. REFL9pp ~ 560 mV POP9pp ~ 280 mV REFL45pp ~ 1120 mV (!) POP45pp ~ 70 mV REFL45 seems to be slewing at ~ 100 V/us, seems pretty fast.
"normal" means RF9 not reduced.
(We've looked at REFL45 though it's not used for LSC as when the RF opamp for 45 is going crazy it could affect the input side.)
We will repeat this with the reduced RF9.
Nominal modulation index for 9.1MHz: Γ~0.191
Nominal modulation index for 45.5MHz: Γ~0.251
For the above measurement the modulation index for 45.5MHz was reduced by 3dB to Γ~0.177.
Side-by-side numbers for H1 and L1 are posted in LLO log entry 41547
RF slider settings during this measurement.
Betsy, Sebastien, Slawek Work on installation of AMDs on ITMx and ITMy has been completed. Each test mass has now 4 AMDs glued to the suspension flats. All AMDs on ITMy are glued slightly lower than the nominal AMD height position. It appears that quad suspension of ITMy is ~5 mm longer than the ITMx quad. We have noticed it after AMD installation. This new AMD position should not cause any AMD performance degradation neither increase thermal noise according to our simulation. Additionally, due to the scratches on the test masses flats we decided to move AMD 4 on ITMx and AMD 4 on ITMy. The exact gluing locations are shown in the attached drawing. The curing dynamic test of the epoxy EPOTEK 302-3M of all batches was passed, see attached picture. The bond between AMD and TM looks good for each AMD (see the back face image of the AMDs). We can call this installation 100% successful.
The list of the different AMD modes are listed in the DCC document 'AMD_modes.pdf':