Appears to have crashed Saturday on an invalid json value. Still 750 channels not connected. Seem to be end X Beckhoff channels. Can connect to at least one of them from zotws12 but not conlog-master.
CP4 pressure trend over 7 days. We will lose trending of PT-245 after the bake starts (later this week?). Will try to estimate water content from curve later.
TITLE: 02/20 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
ISI config is in Large EQ mode since Friday Feb 16th. I will leave it this way until Jim gets here. Work being done at both ends so BRS turned of seems like a good way to let it be fo now.
PSL is tripped
Actually the laser is off to facilitate work involving the 70W amplifier.
Jeff Kissel will make the log entry on the electric field meter. The calibration of the field meter is Volts/(Volts/meter) =2.1 x 10^-2 flat from 10Hz to 20KHz. The confusing results that Betsy, Sheila, Jeff and I got this afternoon may be due to the vibration and acoustic sensitivity of the electric field meter. Suggest further measurements with the worst acoustic and vibration sources turned off. Also the meter has a common mode sensitivity to the battery voltage. I never connected the battery box to the neutral (white terminal). It would be good to connect the battery box itself to the lead coming from the field meter that attaches at the white terminal with a clip lead. If there is not a significant change in the low frequency noise, suggest turning off the ISI and other instrumentation in the chamber. That is if you have the time to further investigate where the low frequency noise originates.
Kissel checked and confirmed that the Y-arm is passable this morning. As well, we see Mark baling along the X-arm. He are just now heading past the mid station and headed to the end. Thanks Mark!
Lots of people on site this morning.
We have measured the escape efficiency of our OPO by injecting 1064nm light into the input/output coupler to measure intracavity losses, we did this both before and after swapping the input coupler. Our final result for escape efficiency is 98.63+/- 0.03%, which means that we have 85+/- 36ppm of losses in addition to the transmission of M1+M2 in the cavity.
Set up
We set up a new optical path to couple 1064 into the OPO input/output coupler to make an escape efficiency measurement. On the optical table, we set up a Thorlabs fiber collimator F220FC-1064 (f=11.17mm), which has a waist of 437um at 1.13meters behind the collimator. The attached photo shows how we modified the squeezing output path and the green pump injection path to inject this. We left the -75mm ROC lens that was already placed and adjusted for the green mode matching in place, and added the ROC +150 lens for the translation stage temporarily at the edge of the platform to mode match this beam into the OPO. We had a different mode matching solution for the first set of measurements (taken before the M1 swap), but decided to try to improve the mode matching for the final measurements.
Measurements:
We scanned the cavity using the PZT on M2, and made a fit for the voltage applied to the PZT vs cavity length using the transmitted 00 peaks, in the same way we did for 40362 Both before and after swapping M1, we recorded data as the PZT scanned over 4 FSRs, so the results here are the mean and standard error of the 4 measurements. We estimated our mode matching using the peak heights (peak 00/(peak00+peak20)). The reflected power on resonance over off resonance is corrected to account for this mode mismatch assuming that there is a signal on the PD from order modes equal to V_{off resonance}*(1-mode matching) that contributes to the measured voltage both on and off resonance. This gives us an estimate of the round trip losses other than input coupler transmission, including the transmission of M2 who's reflectivity was measured to be 0.99818636 in E1800011. (Fabrice tells us that the mirrors installed in the H1 OPO before the M1 swap were serial numbers 37, 11, 6 , 8 for M1 to M4 respectively in E1800011).
The escape efficiency is given by ln(R_{m1})/ln(R_m1*R_loss) where Rloss includes all losses and transmissions other than R1. R_{m1}=0.87298077 before the swap, after. For reference I've also included the maximum possible escape efficiency before and after the swap, is the m2 transmission was the only contribution to Rloss.
mode matching | reflected power dip on resonance | estimated dip with mode mismatch corrected | round trip loss (other than M1 transmission) | intracavity loss (excluding M2+M1 transmissions) | escape efficiency | escape efficiency with no intracavity loss | |
Before swap of M1 |
90.4+/-0.1% |
94.8+/-0.1% | 94.2+/-0.1% | 2010+/-45 ppm | 201+/-45 ppm | 98.54+/-0.03% | 98.68% |
After swap of M1 | 96.3+/-0.1% | 94.8+/-0.1% | 94.6+/-0.1% | 1900+/-36 ppm | 85+/-36 ppm | 98.63+/-0.03% | 98.68% |
More on mode matching correction
We tried to check that the correction for higher order modes reliable by taking one set of data where we intentionally misaligned the input beam, and attempted to correct for both the mode mismatch and misalignment higher order modes. This gave us an inconsistent answer, which is why we were motivated to improve out mode matching for the final measurement. I don't understand what is wrong with the higher order mode correction, that requires some more thought.
In the end, our losses are dominated by the transmission of M2, so this measurement gives us rather large uncertainty on the other losses in the cavity. We can be confident that the escape efficiency is close to the best possible for the selected transmissions.
After finishing this Friday we restored the green injection path, and worked on some of the remaining items on the VIP platform. There is some remaining work to be done on the VIP before balancing it.
Kyle and I finished removing the GV12 annulus tubing (except for gate annulus, which is double-valved out under vacuum), installing blanks, cleaning up loose ends and preparing the area for Tuesday morning. Both of us are leaving the site now.
J. Kissel FRS Ticket 9683 WP 7358 As we gear up for a quick corner station vent to fix H1 SUS ITMY (LHO aLOG 40587), I post a template that we can use to assess whether all top mass OSEMs are bug-free within 30 seconds. The R0 RT problem (see details in, e.g. LHo aLOG 40555) is clearly visible (Red Trace in upper left corner, brown trace in lower right coner of plot 1; Middle Green trace in plot 2) -- noise floor is an order of magnitude above all other OSEMs, and has a ton of high frequency combs. Hopefully, once the short is fixed, this will disappear, and R0 RT will look like every other OSEM, with a flat noise floor from 10 to 1000 Hz, at a level of ~5e-11 [m/rtHz]. The template also lives here: /ligo/home/jeffrey.kissel/Templates/H1SUSITMY_M0R0_OSEM_ASDs.xml
This afternoon I tweaked up the DBB and took a round of measurements prior to the 70W amplifier install. Something appears to be not quite right with this NPRO laser. Both the frequency and pointing noise measurements show a very large peak between 100 Hz and 500 Hz, with the peak being somewhere in the neighborhood of 260ish Hz. This looks similar to the peak from Peter's NPRO measurements from this morning. We'll have to look into this first thing on Tuesday morning. Perhaps our decision to keep the old NPRO power supply installed was not a wise one, as there can sometimes be odd behavior when using a NPRO with a different power supply. Swapping in the new power supply is fairly painless, so this will be easy to check, although we will then lose the ability to remote start the NPRO laser, and therefore the PSL as well.
I dug up the acceptance test results for this laser (T1500521) and the same peak is present when the power supply that came with the laser was used. So it is not likely to be solely due to the different power supply.
We fixed a couple of issues resulting from the update of userapps to 1.8 today.
1. Several files were found to be not executable in the new userapps, but were in the old. Problem was that the files did not have the executable bit set in the repository. This was changed and the working directory updated.
2. Several data-like files were missing in the new userapps. These files were not in the repository. We made the decision that since in this case these files are small and critical we went ahead and added them to the repo and updated userapps to get them.
The first issue prompted me to write up a wiki on how svn handles file permissions
Corey Terry Nutsinee Daniel
We moved ISCT6 from the squeezer bay close to its final position next to HAM6. To allow for work in the chamber the table is positioned about 1m back from its final position and outside the clean room. All three rear panels have been replaced with temporary blanks. The panel on the left will have to be swapped back with panel 1 eventually to get the AISAIR beam path onto the table. Still to do: Drill mounting holes into two new blank rear panels.
TITLE: 02/16 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
It was decided the corner station will be vented on Tues. 7.5 Magnitude EQ from Mexico ended the shift. Sheila is still in the Optics Lab doing Squeezer measurements.
LOG:
In light of the error made in catching the short on 1 cable of the ITMY reaction chain suspension during chamber closeout last month (see Kissel's alog 40555), we are venting the corner volume for a very short period next TUES-WED (20-21st). Kyle and Gerardo will perform a slow vent and then Gerardo and I will attempt a fix at the feedthru, checking Kissel's spectra template for confirmation of fix. If that does not fix it, we are working through plans and preps to pull the door to the chamber and make the fix from the inside.
The large cleanroom in the biergarden has been turned on by Mark D in prep for this activity and will remain on during the weekend.
During this vent activity, please stand down on the following:
- HAM6 In-chamber work
- Transitioning to Laser Haz
WP7357
Chandra, Dave:
The cell phone alarms configuration was modified in order to:
remove CP4 discharge line pressure channel (and associated error channel)
decrease CP4 vacuum gauge upper alarm level from 5.0e-04 to 5.0-e06 Torr
I also took the opportunity to make some code changes related to running the code in the background under systemd control. The STDOUT verbose reporting is now directed to a time-stamped file. Issuing a SIGUSR1 signal to the code will cause it to open a new reporting file, permitting me to rotate these files and compress the old ones (yes, I know python has logging with rotation, I'm using that to write low level logging output already).
Configuration change for PT245:
H0:VAC-MY_Y4_PT245B_PRESS_TORR VE gauge, MY CP4, CC 9.713e-07 True 0 0 OK NO_ALARM 1.000e-10 5.000e-06
This should be a good configuration for the long weekend and maybe through next week.
The full set of TFs for the newly re-assembled ETMy has been taken, and all appears to be healthy and ready to be passed to the next teams that need to use it for in-chamber work. This is the first set of TFs of the reaction chain with the new AERM, so some of the peaks in the R0 TFs have shifted due to the new mass distribution of the chain (AERM is lighter than the old ERM and the PenRe has been made heavier to compensate). Kissel had a quick look at some of these TFs and agreed that the peak shifting seems reasonable, but noted that the dynamical model for these SUSes will need to be updated.
The TFs can be found in the usual place:
Main chain: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGM0/Data/2018-02-18_2037_H1SUSETMY_M0_Mono_WhiteNoise_*_tf.txt
Reaction chain: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGR0/Data/2018-02-18_2117_H1SUSETMY_R0_WhiteNoise_*_tf.txt
I attach a reaction chain Yaw TF screenshot as a sample of the peak shifting due to the AERM.
J. Kissel Stuart recently discovered that the SR3 optical lever got overlooked during the big SUS HAM 5-6 Computer swap to accomodate new suspensions related to the SQZ upgrade (see IIET ticket 9928). Daniel and I brainstormed several different possibilities after browsing through the HAM3-4 and HAM5-6 SUS wiring diagrams (D1000599 and D1002740, respectively): (1) Buy a whole new ADC card for SUS HAM 56 computer (and associated ADC Adapter Card, Cabling, and AA chassis) (2) Plug the signal -- no matter how icky it is in analog -- into some other suspension's spare spigot (a) The SUSHAM3-4 control chassis has a few spare DB9 ports (especially after the decommissioning of HAM table optical levers) (b) The SUSHAM5-6 monitor chassis has one spare DB9 port After discussing with the systems group, they suggest nixing (1) in favor of (2) for the time being (i.e. until A+). Having no preference for (2)(a) or (b), they suggested looking at the physical location of the cables and ports in the CER to break the tie. I attach pictures of the relevant racks. I had initially thought -- based on the pictures -- we should obviously go for (2)(b): plug the SR3 optical lever DB9 into the spare DB9 port of the SUS-C8-38 AA chassis, which feeds into channels 4,5,6, and 7 of ADC 2 of the monitor chassis. Once in the susauxh56 monitor model, we would then ship the signals over to the h1sussr3 control model via Dolphin PCIe inter process communication, as had already being done during O1/O2 via the h1sussrm model. HOWEVER -- I remember that the AUX monitor IO chassis / computers don't have a Dolphin PCIe cards installed, and Dave confirms this. He also confirms, however, that adding a new card to the IO chassis is a small expense -- but only if we're not short on Dolphin PCIe switch ports. The HAM3-4 racks are on the other side of the "hall" of racks, so it would be possible to connect in that control chassis (which does already have Dolphin PCIe capability) re-routing the cable over to that rack and into the appropriate chassis. So, again, both options in (2) are a toss-up requiring a bit more information to decide between the two. I'll update the ticket, file and ECR, and wait for further discussion with a few more people before making the decision.
Sheila, Nutsinee, Terry,
This is an update on the progress so far on the VIP. We have aligned and mode matched both the CLF/seed 1064 path and the 532 pump path to the OPO, and are ready to think about swapping M1 for the higher green reflectivity version.
Here's the green data (+PZT calibration). Note that the data hasn't been corrected for dark current.
I corrected the green data for dark current as Sheila suggested. The mode matching calculated from transmitted power is now 73.5%. The dips in reflected power are 78.8% of the power off resonance. Higher order modes has not been taken into account.