Jeff B, Dave:
I have updated the check_dust_monitors_are_working script to scan all the LVEA dustmonitors, and added both 300nm and 500nm channels. I also modified the script to allow the user to specify the look-back time in hours (used to be days). This is needed as the script cannot transit a daq restart time.
Here is the output for the past 20 hours of dust data:
david.barker@zotws6: check_dust_monitors_are_working 20
H1:PEM-CS_DUST_LVEA2_300NM_PCF Channel Statistics: mean 9.43 max 280.00 std-dev 33.31 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA2_500NM_PCF Channel Statistics: mean 1.94 max 40.00 std-dev 6.41 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA3_300NM_PCF Channel Statistics: mean 114.62 max 10320.00 std-dev 1026.39 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA3_500NM_PCF Channel Statistics: mean 101.03 max 7970.00 std-dev 803.59 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA4_300NM_PCF Channel Statistics: mean 4.57 max 30.00 std-dev 6.38 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA4_500NM_PCF Channel Statistics: mean 0.00 max 0.00 std-dev 0.00 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA5_300NM_PCF Channel Statistics: mean 6.78 max 320.00 std-dev 31.90 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA5_500NM_PCF Channel Statistics: mean 7.40 max 740.00 std-dev 73.63 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA6_300NM_PCF Channel Statistics: mean 6.12 max 200.00 std-dev 20.86 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA6_500NM_PCF Channel Statistics: mean 3.16 max 250.00 std-dev 25.34 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA10_300NM_PCF Channel Statistics: mean 30.58 max 2590.00 std-dev 257.52 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA10_500NM_PCF Channel Statistics: mean 24.54 max 2130.00 std-dev 213.26 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA30_300NM_PCF Channel Statistics: mean 4.78 max 30.00 std-dev 6.08 (20 hour(s) minute trends)
H1:PEM-CS_DUST_LVEA30_500NM_PCF Channel Statistics: mean 1.45 max 70.00 std-dev 8.00 (20 hour(s) minute trends)
H1:PEM-CS_DUST_PSL101_300NM_PCF Channel Statistics: mean 0.68 max 15.00 std-dev 1.72 (20 hour(s) minute trends)
H1:PEM-CS_DUST_PSL101_500NM_PCF Channel Statistics: mean 0.31 max 24.00 std-dev 2.42 (20 hour(s) minute trends)
H1:PEM-CS_DUST_PSL102_300NM_PCF Channel Statistics: mean 4.32 max 50.00 std-dev 8.14 (20 hour(s) minute trends)
H1:PEM-CS_DUST_PSL102_500NM_PCF Channel Statistics: mean 0.10 max 10.00 std-dev 0.99 (20 hour(s) minute trends)
H1:PEM-EX_DUST_VEA1_300NM_PCF Channel Statistics: mean 13.76 max 150.00 std-dev 22.49 (20 hour(s) minute trends)
H1:PEM-EX_DUST_VEA1_500NM_PCF Channel Statistics: mean 5.99 max 60.00 std-dev 10.98 (20 hour(s) minute trends)
H1:PEM-EY_DUST_VEA1_300NM_PCF Channel Statistics: mean 675.02 max 4180.00 std-dev 1015.13 (20 hour(s) minute trends)
H1:PEM-EY_DUST_VEA1_500NM_PCF Channel Statistics: mean 22.69 max 160.00 std-dev 34.25 (20 hour(s) minute trends)
david.barker@zotws6:
J. Oberling, P. King
The swap of the NPRO is now complete. After needing the morning to figure out an AC problem in the PSL enclosure (as a result of Saturday's power outage), yesterday afternoon was spent trying to find better mode matching for the NPRO to the MOPA. Unfortunately, everything just made the beam profile worse. So this morning I returned to the configuration we had last Friday and we attempted to injection lock the HPO. The output power of the 35W FE was measured at 35.7 W.
We first checked the alignment through the HPO irises; some small vertical tweaks were necessary, we used mirrors M01 and M02 to preform the tweaks. The HPO was then brought online and we attempted to injection lock to the 35W FE. At first it didn't want to lock, so we looked at the PDH error signal. The error signal looked clean, so we realigned the beam onto the locking PD; this also did not help. Thinking we needed to improve the overlap between the FE and HPO beams, we performed slight tweaks to mirror M02 to improve the PDH error signal; this also didn't help. Peter happened to be messing with the RF summing box in the FE (for the 35.5 MHz RF for the PDH sidebands for injection and PMC locking), and we noticed the error signal got better. It still wouldn't lock, so Peter tried tightening the connectors on the summing box; lo and behold, it locked! We couldn't find any obvious issues with the cable or connector such as damage, so thinking that maybe we had a ground problem with the box Peter put a piece of Ameristat underneath the summing box. We then purposely broke the lock several times by tapping on the PSL table and the HPO box, and it relocked without issue every time.
Just to see where we were with the PMC, we opened the HPO external shutter and attempted to lock the PMC. It locked without issue, but definitely needs some tweaking; it's good that it locked so easily though. We left the PSL in this state to run overnight; the HPO was outputting 155.8 W. This completes the swap of the NPRO, now we need to recover the PSL subsystems. On the docket for tomorrow:
I'll update this alog with beam profile pictures tomorrow.
All Damping installed on the HAM2 ISI for Corners 2 & 3 as well as the Horizontal GS13 Can Damping on Corner1. Remainder is Corner1 Spring and Flexure dampers and the Vertical GS13 Can Damper. Working with PSL on the ISS cabling which complicates the Corner1 work on the blade spring.
TITLE: 09/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
LOG:
15:50 TVo and TJ to LVEA to look for cards
15:51 Richard to CER to look at power supplies
16:01 T&T out
16:10 TJ, TVo and PK to ends for HWS work
16:28 Jim back from EY
16:37 Betsy out to the floor
16:40 Corey out to squeezer bay
16:42 Dave B to reboot EY computers.
16:48 Travis heading into LVEA
16:56 Richard out of CER
18:12 Dave back from EY
18:25 Dave has restarted all FE at EY.
18:33 Jim recovering SEI at EY
18:45 Jeff B out to floor
18:46 TJ. TVo and Peter back from Ends
20:50 Jason back into the PSL
21:10 Peter and Jason back into the PSL
21:13 Dave B brought to my attention that the EY SWWD was still tripped. Untripped.
21:18 Corey back into the squeezer bay
21:53 Rick and Kantoro out to look at HAM2
22:48UTC
Jeff B, Patrick, Dave:
14:06 PDT: DAQ restart primarily to add LVEA dust monitors 3,4,5,30 to the frame (a new H1EDCU_DUST.ini). We also installed a new H0EDCU_SAFETY.ini in which channels named IOT2R were renamed SQZT6.
h1nds1 did not restart cleanly, monit reported it was not being monitored. I manually restarted it via monit.
I renamed the second trend files which contained the DAQ restart (H-H1_T-1189890000-600.gwf) so that second trends which span this time do not return invalid data.
It was just discovered and brought to my attention that this Oplev failed to recover after the glitch.
Interesting to note, some oplevs came back after the power glitch on Saturday (ITMY) but some didn't (ITMX and ETMY) and ETMX wasn't affected at all. The guardian for each optic seem to be in the aligned states according to the guardian and the slider bars aren't too different from when we were in the observing run (10's of urad) but the beams didn't come back even after I re-aligned to 24 days ago.
Today we vented the corner station which makes sense that the ITMX was a bit misaligned, but ETMX should be back to it's original position.
This morning, the door crew was at it early and had the doors off of HAM2 (E and W) by 9:30am. Hugh and Jeff B started the entry contamination control, Hugh locked the ISI, and I locked the 4 large SUS (PRM, PR3, MC1, MC3) in order to put the face caps on for protection over the first few days of ISI work. (The optics are the only masses locked, and somewhat lightly in order to just support the addition of the caps on.) WHile there, Hugh and I also removed the 2 MC free-standing arc baffles which are going to be replaced, and the OPLEV 2" mirror/mount which is going to be replaced.
Hugh started the HAM2 ISI damper work mid morning, which is expected to run the next couple of days with Jim.
Since they were all geared up and ahead of schedule, Bubba and crew went ahead and pulled the BSC3 W door in the biergarten.
attached is a striptool trend of dust monitor 300 (BSC3) 0.3um counts while the BSC3 door was removed.
The Y scale dotted lines are 200 and 400 counts, the max number is 435
We also turned off the PR3 OPLEV, hence why that SUM is near zero.
I also unplugged the power supply adapter box for HAM3 Optical Lever Transceiver to get an open power port to power the B&K setup. For pictures of today's work, check out 38716. I attach the two money shots I got here though, 'cause they're great. For future reference, it's Betsy and Hugh in garb.
Jim and Dave:
as part of EY BRS code issues, I power cycled the h1brsey computer. This was a full power down, using the rocker switch on the rear of the unit after the windows operating system had shut the machine down.
Fil and Dave:
We replaced the 12V DC power connector on the EY IRIG-B unit. The original connector had a bent locking screw which made powering the unit down difficult. The new connector has a thumb screw and does not need a screwdriver to disconnect.
All the models at EY were stopped for the duration of the repair, and restarted at 11:20 PDT. The front end computers were not power cycled.
An improved design would have an ON/OFF breaker on those units.
TITLE: 09/19 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: N/A
CURRENT ENVIRONMENT:
Wind: 20mph Gusts, 17mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.38 μm/s
QUICK SUMMARY:
Maintenance
Vent: East door removed from HAM2
The attached plot shows 10 days of the HAM2 Corner2 Horizontal CPS. There is about 24 hours of low noise condition after I power cycled the CPS section of the Interface Chassis. The Saturday power glitch is obvious as is the noise level after front end recovery. I'll do the power cycle again but it is weird to power cycle to correct a problem originating from by a power cycle.
Still appears quiet after...5 hours maybe it is has been since I power cycled the Interface Chassis.
On friday Thomas and I ran excitations on all 4 ESDs in order to measure the 4 coefficients in this equation for the force applied by the ESDs (G1600699) Equation 2:
F = α (V_b-V_s)2 +β (V_b+V_s)+ β _2(V_b-V_s)+γ (V_b+V_s)2
The first 2 excitations for each suspension were on the bias path with no signal voltage so that the linear response is:
F = [β+β_2+2(α+γ)V_b] δV_b
The bias path was excited twice, first with the normal bias of 380 V on and second with no bias. Then the script excited the signal path which gives a linear response of:
F = [β-β_2+2(α+γ)V_b+2(α-γ)V_s] δV_s
This path is excited 3 times, once with no DC offset on any electrodes, once with an offset of 7.6Volts on the signal electrodes, and once with the bias at its normal value of 380V.
The first 4 of these measurements allow us to make a complete measurement of all four coefficents, α, β β_2, and γ The fifth measurement is redundant and could be skipped, I used it as a sanity check. I am still worried that I have some signs wrong which are making these results confusing.
ETMX | ETMY | ITMX | ITMY | |
α (N/V^2) | 2.1e-10 | 2.0e-10 | 8e-11 | 5.5e-11 |
β(N/V) | -9.9e-10 | 2.0e-8 | 1.0e-8 | 5.6e-9 |
β_2 (N/V) | 2.8e-9 | 3.2e-8 | -4.2e-9 | -8.5e-9 |
γ | 1.5e-10 | 1.2e-10 | -4.0e-11 | -1.2e-11 |
V_eff = (beta-Beta2)/(2*(alpha-gamma)) | -31 V | -75 V | 60 V | 105 V |
All of the scripts needed for taking the measurement and getting the coefficents are in userppas/sus/common/quad/scripts/InLockChargeMeasurements/
The table above is wrong because of multiple minus signs (which are different between the ITM and ETM ESD drivers) being wrong. Here is a corrected table:
ETMX | ETMY | ITMX | ITMY | |
α (N/V^2) | 9.6e-11 | 8.7e-11 | 4.9e-11 | 5.8e-11 |
β(N/V) | -1e-9 | 2e-8 | -1e-8 | -5.6e-9 |
β_2 (N/V) | 2.8e-9 | 3.2e-8 | 4.2e-9 | 8.5e-9 |
γ | 2.6e-10 | 2.3e-10 | -9.2e-12 | -1.5e-11 |
V_eff = (beta-Beta2)/(2*(alpha-gamma)) | 12 | 38 | -124 | -97 |
The values in this table still had some calibration errors. New log coming soon.