I made a calibration of the IM4trans and MC2trans SUM channels into uW.
The conversion from W incident on the PDs to counts registered on IMC-IM4_TRANS_SUM_OUTMON is as follows:
[counts/W] = responsivity [0.16 A/W] x transimpedance gain [1000V/A] x differential to single input gain [2V/V] x whitening gain [36dB=63.1 V/V] x ADC gain [1.6384x10^3 cts/V].
This is actually the same for both MC2trans QPD and IM4trans QPDs: 2.087x10^9 [counts/W]
I used this calibration factor to calculate the power on IM4trans and MC2trans currently:
IM4trans counts ~= 57890 counts, which converts to 1.75mW. Comparing this with the expected power on IM4trans:
8.73W into IMC * 0.85 IO throughput * 2400ppm IM4 transmission * 0.1 transmission of BS between IM4 and IM4trans QPD = 1.78mW
MC2trans counts ~= 2.17x10^4 counts, which converts to 655uW. Comparing this with the expected power on MC2trans:
8.73W into IMC * (IMC gain = IMC Finesse/pi = 166 ) * 5.1x10^-6 MC2 transmission * 0.1 transmission of BS between MC2 and MC2trans QPD = 740uW.
Both these estimates for the power incident on each PD agree pretty well so I'll go ahead and add a new filter called "cts2uW" in the SUM_OUTMON paths to give the outputs in uW incident on the PDs.
It is now using the file /ligo/lho/data/conlog/h1/pvlist_1391196748 (attached). There are 99,264 channels in this list. 5,755 are currently unmonitored.
There are 62,966,023 rows in the database.
Suspension has been stopped and Pre-installation plate installed. Work completed!
Work completed
We fixed Daniel's channel naming problem with the ALS addition to the ASC, actually the problem went away. So I restarted the new h1asc model at 12:41 and restarted the DAQ at 12:44 to install the new model and DAQ channels associated with it.
Noticed some fluid in the bottom of the SW SEI Pier at the BS. Cleaned up the mess in the Pier yesterday and this morning found fresh fluid. Climbed up to Housing and found the Vertical Actuator Fluid Catch overflowing. I can see drips coming off the Parker Valve. Can't tell if it is coming out of the Valve itself or just the Valve/Manifold seal. It looks like it could be the former. I'd like to clean up the catch and tighten the valve to manifold screws and see what it looks like in a couple days.
This may require a valve change which would briefly glitch the fluid pressures twice and in between have the BS HEPI uncontrolled for a few hours as we bleed after the valve change.
I cleaned up the Catch Pan and checked the Valve to Manifold screws. They were plenty tight. When I look again (Monday, tomorrow?) I'll be pretty confident about from whence the leak comes but I fairly sure now that is is from the Valve itself.
"Noisy" scroll pump located outside of building near LN2 dewar
Going to HAM 4 to prepare SR2 Pre-installation Plate (Cookie cutter) and hardware– Jeff B.
Starting Stiffener rings and o ring protectors installation on HAM4 - Apollo
Work completed!
(Alexa, Daniel, Keita)
After changing the RF frequency to 24.389319 MHz and adjusting the delay line phase to 257 steps, we took open loop transfer functions of the PDH loop.
PLL Board Settings:
PDH Board Settings (Nominal):
EX_PDH_OpenLoopTF_phase/mag_Nom.txt corresponds to the data collected with the above nominal settings.
EX_PDH_OpenLoopTF_phase/mah_Boost2On.txt corresponds to the data collected wiith the above settings with the addition of Boost 2 ON
EX_PDH_OpenLoopTF_phase/mag_6dBFast.txt corresponds to the data collected with the same as the nominal settings with the addition of 6dB gain in the fast path
Heading into the LVEA to check a dust monitor (location #9) which has lost communication - Patrick
Work completed!
Moving, cleaning, and organizing elements for SR2 installation (HAM4 LVEA) - Jeff.B/Jodi
Disconnected temporary cabling that were used for testing of SR2 next to HAM4. Connected permanent cables to satellite units in SUS H1-R3. Permanent cabling were already pulled and connected at chamber side: Cables were connected at chamber side according to D1101814. D6-1C1: Cable SUS_HAM4-32 SR2 BOTTOM D6-1C2: Cable SUS_HAM4-31 SR2 MIDDLE D6-2C1: Cable SUS_HAM4-10 SR2 TOP D6-2C2: Cable SUS_HAM4-11 SR2 RIGHT/LEFT Filiberto Clara
Work completed!
Aidan, Thomas, Eric G.
We installed the TCS HWS HAM4 optics this afternoon per D1201098. We've finished using that area and the chamber is covered again.
Full details tomorrow.
Here are the full details ...
We had to place ten optics/opto-mechanics assemblies. The D1201098 installation kit (cookie cuters) parts were placed to facilitate placement and alignment of optic assemblies. The assemblies were then bolted into position, summarized below:
Photos are attached below. Complete set is on ResourceSpace
We plan on installing the 4x 2" lens mounts and optics during the alignment of these optics or earlier.
I have been silently checking the signal chain of the REFLAIR and POPAIR RFPDs using the AM laser (a.k.a. PD calibrator) to make sure that they are functional expectedly.
Summary
The RF frequency of the AM modulation was adjusted in each measurement such that the demodulated IF signal was below 50 Hz.
Calibration of the amplitude modulation depth
We recalibrated the AM laser.
The current setting of the laser was changed recently because we opened up the current driver when we thought the laser diode had been dead in the early December. Then the laser head and its current driver were sent to Rich at Caltech for his extensive testing although the laser magically fixed itself and he didn't find anything wrong. So this was the first time for us to use the AM laser which had been fixed. Because of that mysterious event, I wanted to recalibrate the laser. First of all, Yuta and I measured the power to be 2 mW with an Ophir Vega without the attenuation filter. Then we measured the modulation depth for the amplitude modulation by using a Newfocus 1611 as a reference.
The new calibration for the amplitude modulation is:
P_am = 5.13 mW x (P_dc / 1 mW) * (1 V / V_drive)
where P_dc is the laser power at DC and V_drive is the drive voltage when it is driven by a 50 Ohm source. For example, if one puts this laser to a PD which then shows a DC laser power of say 2 mW, the AM coefficient is now 5.13 mW x ( 2 mW / 1 mW) /V_drive = 10.26 mW/V_drive.
REFLAIR_A_RF9 (S1203919)
Remarks:
The signal chain is OK. The PD response is smaller by 15% for some reason.
It seems as if the transimpedance is smaller by 15% than what had been measured at Caltech (LIGO-S1203919). The cable loss from the RFPD to the rack was measured to be 0.47 dB. Be aware that the demod gain is half of the quad I/Q demodulator because this is a dual channel demod (see E1100044). The demod conversion gain is assumed to be 10.9 according to LIGO-F1100004-v4.
REFLAIR_A_RF45 (S1203919)
Remarks:
The signal chain is healthy.
Found cable loss of about 1.5 dB. The measurements excellently agree with the loss-included expectation.
POPAIR_A_RF9 (S1300521)
Remarks:
The signal chain is healthy.
The measurement suggests that there is loss of 1 dB somewhere. I didn't measure the cable loss this time.
POPAIR_A_RF45 (S1300521)
Remarks:
The signal chain is OK. Though loss sounds a bit too high.
The measurement suggests a possible loss of 2.6 dB somewhere. I didn't measure the cable loss.
REFLAIR_B_RF27 (S1200234)
Remarks:
The signal gain is bigger than the expectation by a factor of 2.3.
REFLAIR_B_RF135 (S1200234)
Remarks:
The signal gain is bigger than the expectation by a factor of 1.5
POPAIR_B_RF18 (S1200236)
Remarks:
The signal gain is bigger than the expectation by a factor of 2.3
POPAIR_B_RF90 (S1200236)
Remarks:
The signal gain matches with the expected value, but I don't believe this.
There was a typo:
P_am = 5.13 mW x (P_dc / 1 mW) * (1 V / V_drive)
P_am = 5.13 mW x (P_dc / 1 mW) x (V_drive / 1 V)
For 27MHz and 136.5MHz, the RF gains are +19.8dB and +50.7dB, respectively. S1400079
The response of the BBPD isn't really flat over all frequencies. See D1002969.
The description in D1002969 is for the initial version. (The schematics seems up-to-date.)
The latest version has the rf performance as attached.
This is a follow up of the calibration measurements for REFLAIR_B and POPAIR_B.
I have updated the expected signal gain for these photo detector chains using more realistic gains which Koji gave (see his comments above). Now all the values make sense. Note I did not perform any new measurements.
In the following calculations, the quantity in red represent the updated parameters.
REFLAIR_B_RF27(S1200234)
Remarks:
The signal chain is healthy. There is loss of 0.92 dB somewhere.
REFLAIR_B_RF135(S1200234)
Remarks:
The signal chain is OK. There is loss of 3.9 dB somewhere.
POPAIR_B_RF18 (S1200236)
Remarks:
The signal chain is healthy. The signal was bigger by 9% than the expected.
POPAIR_B_RF90 (S1200236)
Remarks:
The signal chain is healthy. There is loss of 1.2 dB somewhere.
From these measurements, we can use POPAIR to infer the calibration for POP.
I looked at a recent lock acquisition while the interferometer was trying to engage the outer ISS loop. The LSC is relatively stable during this time, and the POP beam diverter is still open.
After undoing whitening gain and digital gain (2 ct/ct for POPAIR9/45, and 32 ct/ct for POP9/45), we find the following TFs:
This implies calibrations of 1.7×106 ct/W for POP9 and 1.8×106 ct/W for POP45.
There's a factor of 4 difference in power between POP and POPAIR (17 mW versus 68 mW with a PSL power of 23 W), so the values I gave above are off by a factor of 4. The demod gains should be 6.4×106 ct/W for POP9 and 7.2×106 ct/W for POP45.
We've observed some burn marks on the shielding of the ETMy ring heater cables which occured sometime during the 3 prior weld sessions (May 2012, Dec 2013, Jan 2014). The burns are on the lowest ring heater cable that laces around the test mass and makes a connection between the test mass and the PUM. There is a burn on the right segment and the left segment. I dug up a picture that shows that the burn on the "right" segment (as viewed from the back of the suspension) was there just after the May 2012 weld session, so that one is not new. However the "left" cable burn is new from the Dec or Jan welding. We did not see when this actually occured.
Filiberto tested the ring heater cable and found that all pins are operating as per spec, although he thinks pin 1 is shorting. We are tracking down what this means (did we test it correctly, when was it last tested, is it possible that the burn is contributing to the short, even though it does not look like it is, etc.).
This is the picture of the RH "right" cable taken in May 2012.
And here is the "left" RH segment burn which happened in the Dec or Jan weld.
For the ring heater cable, the following pins were tested. Pins 2,3,4, and 5 are tied together. Pins 14,15,16, and 17 are tied together. The resistance between these two sets is 47.5 ohms. Pins 8,9,10, and 11 are tied together. Pins 20, 21, 22, and 23 are tied together. The resistance between these two sets is 45.9 ohms. Pin 1 is tied to shield and shorted to ground. Filiberto Clara
The fact that the SUM output is used to normalize PITCH and YAW signals meant that adding the filter in front of just the SUM channel increased the gains on PITCH and YAW significantly, affecting the IMC ASC loops. I have now put the cts2uW filters in the input filter banks for each segment of both QPDs. It works fine now, so the MC2trans SUM and IM4trans SUM are calibrated in uW. If anyone changes the whitening gains on these PDs, please be sure to adjust the calibration factor accordingly. I may look into automatically factoring the whitening gain into the calibration to avoid this issue in future.
Just to be clear, the calibration from counts to uW for both IM4trans and MC2trans was 0.032 uW per count. The number 2.087x10^9 [counts/W] was in error: this number should have been 3.3080x10^7 [counts/W]. Although the number in the alog post was in error, the correct number was used in the filters which were applied.