The ISC Whitening chassis S1101631 mentioned in Kiwamu's log entry (14430) was removed from the X-End LVEA electrnoics rack. The -15VDC failed. I also removed a small snake from the computer cart all snuggled up to the warm monitor and keyboard.
I did not notice the snake!
It was the +15 rail, not the -15. My bad.
Found cdswiki completely unresponsive, rebooted. Access to work permits and the wiki is now functional.
Kiwamu, Alexa, Sheila
Tonight we have locked DRMI on 3F +the arms on ALS many times. We were able to sweep COMM from one side of the resonance to the other, and DRMI stayed locked.
Times: DRMI +arms off resonance , on 1F 00:23:54 UTC october 14th 2014. transitioned to 3F, 00:30:25 UTC
There was one time that we had difficulty locking DIFF, we disabled the LSC DARM offset and this might have helped.
H1:FEC-98_IPC_LSC_ETMX_L_SUSETMX_ER
H1:FEC-98_IPC_LSC_ETMY_L_SUSETMY_ER
Seems like these have been non-zero for like forever (why?), but the error counts jumped up on Sep/05/2014 and never came back down.
The same behavior is seen at LLO. The problem is that the LSC model and/or end-station SUS models are not always getting done soon enough in the real-time cycle to do all the GE FANUC RFM IPC calls. Solutions are 1) Simplify models (fewer filters) to reduce cycle time 2) Reduce the number of GE FANUC RFM IPCs. Rolf and LLO CDS (with help from Gerrit Kuehn at the AEI) have been trying to complete testing on faster hardware to replace the existing LSC0 front-ends. Cycle time does appear to be 30% less, which may be enough. Still need to test in a fully-loaded configuration, and to figure out proper boot method (new hardware needs new network drivers, etc.).
Not sure why reduction of IPC channels would help. There is only one latency critical channel from each iscex and iscey to lsc0, and two from lsc0 to sus/sei in ex and ey, respectively. All others could probably be processed after and then delayed by a full cycle without too much trouble.
A whitening chassis at EX seemed to have died on the last Tuesday. This should be fixed.
All four segments of both in-vac IR QPDs (ASC-X_TR_A and _B) had been reading some bogus values since approximately 7 pm of 7th of October in PDT. Dave and I looked at the reboot logs and confirmed that no software activities were performed since 3-ish pm in this particular day. We suspected some analog issue and therefore I went down to EX to check out the circuits. The AA chassis seemed to be working fine because the raw ADC counts had gone when I disconnected the signal cables. Tracking the signal lines further, I found a whitening chassis whose +15 V LEDs were all off. I power-cycled the chassis and this resulted in change in the level of the bogus signals, but this did not still give me realistic signals. The +15 V indicators are still off. We need to replace this unit.
The binary readback cable was disconnected from this chassis when I went to investigate. Do you know why? I'm going to reinstall as I found it. Be aware of this in the case that you should need it.
8:10 ISS Diffracted power adjusted to 9.5 % - Operator 9:26 Hanford Fire Department on site to work on RAFAR boxes at EndX/Y 9:27 Heading to EndY to work on Green WFS – Keita 9:47 SRM AA Chassis work in LVEA – Richard/Vern 9:56 3IFO Quad work in LVEA (West Bay) – Betsy/Travis 11:53 Returned from LVEA – Richard/Vern 12:40 Back from End Y – Keita 13:40 Heading back to work in the LVEA – Betsy/Travis 13:49 Going to the LVEA to check on a vacuum rack - Richard
This morning while the interferometer was tied up with other work, I took a quick look at the length to angle coupling of ETMX.
The bottom lines:
I had a look at the impulse response by applying a million counts offset in L3 INSINF and watching the oplev time series. The first plot shows the reponse of the three stages used in ALS DIFF (Mo, L1, and L3) with the filters set as they would be for DIFF, with the other stages turned off. You can see that L1 causes a large response in pitch, while M0 seems to be fine.
The next plot shows the response of the L1 stage alone. With the L2P decoupling off, we get less of a response in pitch, while turning off the L2Y filter doesn't make much of a difference. Based on this I have turned off the L2P on L1 for now.
The last plot shows the immpulse response of all the stages, with everything as nominal for ALS DIFF. In the red trace, the L1 L2P filter is off, in the blue trace it is on.
As a follow up to the measurments I ran on ETMY last week, I ran a similar measurement on ITMX this morning. To recap, all of the isolation loops were engaged on the ISI, blends swith to Start, and I drove in low frequency in Z on first the ISI, then a second round on HEPI. In the attached plots, the dotted references are the first measurement, the solid lines are the second. Pretty much the same story as last week, with some weird tilt-looking coupling when we drive on the ISI that seems to disappear when I drove HEPI. I included the L4C's this time around. Curious that the L4C's don't seem to see the coupling as much as the T240 do, but more than the cps's do (which I didn't get this time around).
I tried to measure the Flex modes (T240 over-constrained modes), but their cartesian component matrix elements are all zeroed, so I didn't get any data. I'm unsure of what those values should be, and they aren't defined in Fabrice's Sensor Location document, T1000388.
With the microseism being elevated over the weekend--looked at the floor seismo wrt the HEPI L4Cs. We'd really like to help with microseism noise but it is a tough problem. However, something just doesn't seem right.
Looked at coherence between the floor sts2 and BS HEPI X Y Z Blend inputs. Strong coherence with Z but X & Y pretty poor. Looking at the locally oriented sensors and whoa, strong coherence with the diagonally oriented HEPI L4Cs split between the X & Y... See attached.
The upper left panel has the coherence with the cartesian basis blend inputs. Strong in Z but oor in X & Y. The lower left panel has the local basis horizontals with the X ground signal: Strong in H1 and H3, the sensors oriented NE to SW (building crane basis.) The H2 & H4 sensors, oriented Nw to SE show little to no coherence. The upper right panel looks at the horizontal local sensors wrt the Y ground motion and the result is the opposite: strong signal with the H2 & H4 L4C but little to none in the H1 & H3 signals. The lower right shows the strong coherence in all the Z local L4C signals with the Z signal from the floor seismometer.
Since the Z signal has good coherence, I don't think there is any problem with the model path, maybe?
Since the Local to Cartesian transformation has equal magnitudes (the local sensors are oriented at 45 degrees to the LIGO referencef frame, I don't believe the matrices are to blame. These values are correct based on T1000388.
This leads me to conclude the the ground STS2 must be oriented incorrecty or its internal U V W transformation to X Y Z is messed up. This will certainly cause issues with sensor correction etc.
The STS2 was not oriented correctly. See log 14463 for details
Laser Status: SysStat: Warning “VP program online” is red Output power is 33.5 W (should be around 30 W) FRONTEND WATCH is active HPO WATCH is red PMC: It has been locked 5 days, 22 hr , and 54 minutes (should be days/weeks) Reflected power is 2.0 Watts and PowerSum = 25.7 Watts. (Reflected Power should be <= 10% of PowerSum) FSS: It has been locked for 1 d, 7 h, and 9 min (should be days/weeks) Threshold on transmitted photo-detector PD = 2.26 V (should be at least 0.9V) ISS: The diffracted power is around 9.5% (should be 8-10%) Last saturation event was 2 d, 19 h and 0 minutes ago (should be days/weeks NOTE: The ISS Diffracted Power was out of its range (8-10%) this morning. It was fixed by adjusting the ISS Reference Signal value.
model restarts logged for Sun 12/Oct/2014
2014_10_12 08:44 h1fw0
2014_10_12 18:27 h1fw1
2014_10_12 21:41 h1fw0
all restarts are unexpected
K. Venkateswara
As described by Sheila in 14416, high wind speeds were recorded at LHO on Saturday. BRS shows corresponding high ground tilts during this period.
The first plot shows the ASD of the GND STS, BRS RY and Stage 1 T240 X. There is excellent coherence between the GND seismometer and BRS RY below 60 mHz and the tilt-subtraction looks quite good - you can clearly make out the primary microseismic peak at 55-60 mHz. Also shown is the BRS reference mirror (~sensor noise). After Fridays calibration corrections, the fudge factor I had to use was smaller (0.79) to get the subtraction right.
Stage 1 shows slighlty better coherence with GND_STS and BRS, but it is still limited by some other source of noise below 0.1 Hz.
The second file shows a band-limited BRS RY (5-500 mHz) and wind speeds as measured by PEM anemometers and converted to X and Y directions using the 'direction' data. I might have the axes converted incorrectly, but visually it shows good correlation with the BRS data.
In looking for source of low-frequency noise in Stage 1, I found something interesting: The first file shows the X,Y,Z and RY motion measured by the T240s on Stage 1. The next file shows the coherence between X, Y and Z sensors and RY.
There is large coherence between Y and RY below ~50 mHz which wasn't too surprising to me. Small misalignments of sensor axes can produce that. However, there is large coherence between Z and RY at the microseism which is odd. To get coherence with Z, one needs sensor calibration mismatch or actuator alignment/strength mismatch. It is also surpsisingly large.
Jim said he'd help me look into this further. But it does explain one thing Jeff had noted in 14047 about why RY looks very similar to X but is not coherent at the microseism. Because RY is measuring Z at the microseism!
Attendees: Bubba, Ed, Doug, Vern, Jodi, Keita, Jeff B, Jim, Hugh, Richard, Michael, Travis, John, Aaron, etc … Today's Tasks: • SRM and Lab work – Richard/Aaron, Ed, etc • Hugh working on Guardian (Reboots). • 3IFO Quad Upper Structure work continues in LVEA – Travis/Betsy • Beam tube cleaning will continue today – Bubba and crew • TMS Optical Table assembly (3IFO) in staging building – Jeff B
The attached plot uses GMT on the horizontal axis. The plot shows 1 - 3 Hz seismic noise last week. Hanford contractors were hauling typical numbers of rubble loads on day shift and swing shift from Monday 10/6 through Thursday 10/9. ERDF, the rubble pit, operated on Friday 10/10 but the number of trucks running to ERDF was low during the day on Friday and nearly absent on swing. Commissioners can expect that the Monday-Thursday noise on this plot will continue through the fall. Fridays will vary from week to week. We're trying to learn the Friday haul estimates a day or two in advance. The big feature on the plot that shows during the weekend appears to be earthquake-related.
The ISS Diffracted Power was over 12% this morning. It is been adjusted to 9.5 %
J. Kissel I happened to have the H1 ISI ETMY overview screen open and noticed a blinking red light in the bottom corner alarming that the pod pressures are low, indicative of a potential leak. Jim informed me that Gerardo had noticed this earlier as well (both interactions verbal, no aLOG). Further investigations reveal that, though the sensors indicate a slow leak over the past 5 months on all three L4Cs; the leak rate is ~0.25e-6 [torr-Liter/sec] (see attached 2014-10-09_H1ISIETMY_L4CPod_LeakRate.pdf) -- a rate that is 1/4th of what has been deemed acceptable (see T0900192). Indeed, for further comfort -- though Brian's original guess (see G1000561, pg 15) says that the pod pressure sensors might only be able to sense 5e-6 [torr.Liter/sec] - level leaks -- it appears that we are indeed at least a factor of 8 more sensitive than that. Though I don't understand it well enough to make adjustments, the action item is to (a) adjust the threshold to represent 1e-6 [torr.Liter/sec] (if we're still OK with that number). and (b) have @DetChar or @Operators make a similar study on the rest of the chambers across the project to ensure that the rest of the pods aren't leaking any worse than these L4Cs. Note that this ETMY is the second oldest ISI (save the LASTI ISI) in the project, as it was installed just after ITMY for the H2 OAT. Details / Logical Path / Figures -------------------------------------- On the MEDM pod-pressure screen (accessible in the bottom right corner of the overview), Corner 1 L4C and Corner 2 and 3 T240 are blinking around 96-97, 100-101, and 100-100 [kPa] respectively, which directly correspond to the blinking alarm light. So, I trended them over the past 300 days. I quickly found that the signals have been non-flat, and in fact going down in pressure, indicative that the in-air pods were leaking air out to the in-vacuum chamber. I focused on the L4Cs, because they appeared to be the worst offender. After identifying that the major features in the 300-day minute trend time series: -- We begin to see data ~1/4 of the way into the time series, right when Hugh and Richard are cabling up the ISI ETMY, now moved into BSC10 on Feb 25 2014 (see 10360), -- The hump that starts at ~1/3 of the time axis is the beginning of the chamber closeout, where kyle turns on the roughing pumps on March 28 (see LHO aLOG 11076), and -- Shark-fin feature 3/4 through the time axis which corresponds to Rai's charge dissipation experiments on Aug 06 (see LHO aLOG LHO aLOG 13274, I believe that the sensors are indicating a real pressure signal, and not some electronics drift as Brian had worried in G1000561. Interestingly, the *differential* pressure does not show a trend, implying that all six L4C pods are leaking at roughly the same rate. To quantify the leak rate, I grabbed the average of one hour of minute-trend data on the first of every month over the linear ramp down the of the pressure for all three L4C pods (i.e. from May 01 2014 to Oct 01 2014): Pod 1 Pod 2 Pod 3 pressure_kPa = [97.423 98.956 98.86;... % May 97.358 98.910 98.771;... % Jun 97.288 98.820 98.710;... % Jul 97.199 98.734 98.573;... % Aug 97.110 98.665 98.526;... % Sep 97.026 98.568 98.369]; % Oct (At this point, I'm just *hoping* the pressure sensors are correctly calibrated, but we know that 1 [atm] = ~750 [torr] = ~ 100 [kPa], so it seems legit.) Taking the matrix of 6 months by 3 pods, I converted to torr, torr_per_kPa = 7.5; % [torr/kPa] pressure_torr = pressure_kPa * torr_per_kPa; % [torr] and assuming the volume enclosed in the pod is volume_L4C = 0.9 [Liter], as Brian assumed in G1000561, and taking time = 1 [month] = 2.62974e6 [sec], the leak rate over each month is leakRate(iMonth,iPod) = (pressure_torr(iMonth,iPod) - pressure_torr(iMonth+1,iPod))*volume_L4C/time; (manipulating the P1* V - L* T = P2 * V equation on pg 15 of G1000561). I attach the .m file to make the calculation, if the above isn't clear enough to write your own. It's a rather noisy calculation from month-to-month that could be refined, but it gets the message across -- the leak rate is roughly 0.25e-6 [torr.Liter/sec], a factor of 4 smaller than deemed acceptable. If one puts on your trusty pair of astronomy goggles, you could argue that the leak rate is increasing, but I would refine the quantification of the leaks before I made such claims. Finally, I checked the GS13s and T240s to make sure they're leaking less, and indeed they are. I also post a copy of the simulink bit logic that creates the warning bit -- it's gunna take me some time to verify it all -- but the goal will be to change the "ABS REF", "DEV REF", and "DEV REL" such that we don't alarm unnecessarily, as we've done here.
One can check if there are really leaks in the pods by looking at amu20 and amu22 on an RGA mounted on the chamber with the suspect pods. The pods are filled with neon. The peaks should be in the ratio of the isotopic abundance of the two neon isotopes.
Quoting T0900192, "We conclude that any leak is unacceptable from a contamination viewpoint..." This should be followed up.
I am skeptical.
We have many conflats and feedthrus installed on LIGO and the failure rate is extremely low once the initial leak test is passed.
I think it is more likely that there is an aging effect here with the sensors or possibly some gettering action of air in the pod (we do not know how much air remained in the pod when the neon was filled). The aging could be mechanical fatigue or permeation of gas into the "zero" side of the capactive sensor.
The kp125 sensors are "low cost" capacitive barometric sensors and a typical use would be in an automobile engine intake manifold. Long term drift of the sensor due to aging would not be a factor in this application because the manifold is routinely exposed to one atmosphere prior to startup - allowing for a calibration.
Depending on the air content in the pods a chemical reaction (slow oxidation??) could also be responsible for this drift. The L4C is the smallest unit and would therefore show the largest loss of gas if this were the case.(smaller reservoir)
Quote from the vendor spec sheet:
The table attached shows the pressure and "apparent leak rates" of the L4C pods for all BSC-ISI. For the calulations, I used a short period of data from the first data of each month. Results for ETMY are consistent with Jeff's numbers.
Results/Comments:
- Unlike ETMY, other units don't show a consitent trend. The pressure signal seems to go up and down, rather than consitently down.
- The sign and amplitude of the apparent leak rate is always very similar within the three pods of a given chamber.