kyle.ryan@LIGO.ORG - posted 01:07, Wednesday 25 November 2015 (23721)
0030 - 0100 hrs. local -> Back and forth to X2-8 to refuel diesel generator
Ops Day Shift: Nov 23rd 2015 0:00-8:00UTC
State of H1: unlocked, wind and microseism making locking difficult
Assisstance today: Jenne, Evan, Jeff
Summary:
An earthquake early on kept us from locking, then winds and microseism. Currently ALS won't stay locked, finding IR is barely possible. I've tried several permutations of ISI configurations, but nothing has helped much. Currently running 90mhz blends everywhere, as that was the best until about 20 minutes ago.
So far no locking tonight. First part of the shift we were waiting for an earthquake to ring-down. Now winds in the 30-40 mph range and moderate microseism are making locking difficult. Jenne is attempting to do some stuff by hand, but the environment doesn't show any signs of settling down.
DCS replaced the main samfs filesever today during maintenance. This took longer than expected, with restarts of Disk2Disk, rds and aggregegated hoft generation occuring around 2 pm PST, and all services restored by 5 pm PST. All DCS services seem to be running fine now. However, the detchar summary pages have not caught up yet and I've emailed Duncan Macleod about this.
J. Kissel Regular Teusday measurements. All 5 measurements complete for both test masses, but I had had a bunch of trouble with NDS returning data gaps that broke the multi-nested set of functions that analyze the data in ways that varied with measurement and even within the data gathering of one measurement. As such, I was only able to process 1 ETMX measurement and 3 ETMY measurements. However, even with that little of measurements, we can still see that the charge continues to trend as expected. The effective bias voltage for ETMY has just crossed zero, on its way to more negative, and continuing to at at rate that is consistent with us needing to flip the bias again in late December. Will work with Stuart and the NDS crowd to try and make data gathering more robust.
there have been 3 testpoints open on PSL PMC for many days, I have just cleared them.
I have compiled and installed all the SUS IOP models against RCG-2.9.7. The next time these models are restarted, they will run with 2.9.7 code which latches any DAC errors and delays the triggering of DACKILLs by DAC errors by one second. Only the SUS IOP models which control 18bit DACs have been built against 2.9.7. The default build area continues to be 2.9.6.
Ops Day Shift: 16:00-00:00UTC (08:00-16:00PT)
State of H1: unlocked, recovering from an earthquake, not yet able to lock, IMC and IFO set to Down
Assisstance today: Jenne, Kiwamu, Jeff, Ed, Hugh
Summary:
Relevant alogs:
Next fill ~ 0030 hrs. tonight
Dave, Jim We modified the /etc/init.d/psinject script on h1hwinj1 to ramp the gain on the H1:CAL-PINJX_CW filter from 0 to 1 over a 10 second interval when starting psinject. Similarly, there is a ramp down of the gain from 1 to 0 over a 10 second interval when stopping psinject. Although this does not prevent a transient if psinject dies unexpectedly, it does help when Monit restarts the process. Since the /etc/init.d/psinject takes longer to finish execution, we also changed the /etc/monit.d/psinject file to include longer timeouts. Modified files are included as attachments. We tested the revised setup by starting and stopping the psinject using Monit and /etc/init.d/psinject, and while under control of Monit, we tested killing the psinject process to ensure that Monit would restart it. Since the scripts now set the gain and ramp time of the filter, we also changed the SDF file to no longer monitor the channels to avoid problems from SDF differences. We left the CW injection running.
I have modified the CDS O1 overview MEDM to make calex a hardware injection system and made the calcs a standard, non-hardware injection system. This means that calex is green when the CW injection is running, and calcs is green when no injections are running.
Guardian will still permit excitations in either calex or calcs and keep the IFO in observation mode. If we are to no longer run any hardware injections to calcs, we may want to remove it from the exception list.
Earthquake data:
Time: Tue Nov 24 22:45:37 UTC 2015
Location: 173km WNW of Iberia, Peru; LAT: -10.6, LON: -71.0
Magnitude: 7.5
Activities during maintenance:
- Bubba and Chirs clearing roads and walkways
- PSL REF CAV alignment, Peter, Ed, Jason
- Sprague, checking traps all buildings
- MikeL called, watch for SNEWs alert at 9:00 and G-wave alert at 9:05
- US Linen delivery
- Jodi in LVEA, 3IFO
- Gerardo, in LVEA, 3IFO
- charge measurements on ETMs, JeffK
- Hugh, HEPI checks all buildings, and in CER
- Filiberto in LVEA, checking racks
- Sprague, ChrisS escorted to LVEA
- 18:10UTC, I put all IMs in Safe Mode, free swinging
- 18:53UTC realigned and damped, except IM1, as noted in my Update Log
- paradice water
- wifi off, Hugh out of the LVEA
- Hugh to EY hepi, ISI tripped
- Hugh to EX, STS rezero
- Chris Biwer, done with CW injection changes
- cleared CDS CRC error
- LVEA sweep - all clear
Title: Ops Day Shift - Mid-shift Update, 22:22UTC
State of H1: lock in DRMI when I started my alog, now in Low Noise
Assistance: Kiwamu, Jenne, Ed
Summary: Y arm alignment has been very sensitive to ETMY alignment, and has needed special attention a couple times today.
Details:
In locking the arms in green, after maintenance, I was able to get Y arm to 0.85 in power, but that alignment was not good for green WFS, so killed the arm.
I chased the changing alignment every time WFS engaged even briefly.
Kiwamu and Jenne diagnosed this as a WFS issue, and driving the WFS issue is was a misalignment in ETMY.
I was able to get the power in the Y arm up to 0.85, however that was optomized for a beam path in the Y arm that wasn't what the WFS wants.
After the Y arm green alignment / locking was corrected and WFS engaged, I offloaded the green WFS and started an initial alignment.
After the initial alignment was complete, the Y arm was again an issue, locking at 0.4.
Again Kiwamu alighned the Y arm, and this time using only ETMY, and arm powers and WFS centering were good.
OMC needed it's WFS cleared.
ISS Second Loop needed to be engaged by hand.
I continued the locking, and currently the IFO is in Low Noise.
- IM1 was found to be not damped, aligned but not damped, and the damping was re-engaged while in Low Noise and the lock survived.
This was a error state that occured after I had all IMs undamped earlier today. Not sure why Guardian didn't re-engage the damping. I only used Guardian to control the IMs, so it seems possible that there's an issue with commands for IM1. This should be tested.
- 22:58UTC, Low Noise lock loss - IFO was oscillating and JeffK tried to intervene, however an earthquake arrived and broke the lock.
WP #5618 Rezero ETMY STS2
Jim noted in the LHO alog 23610 that blend switching is smooth for most BSC platforms except ETMY. BTLantz noted that the ETMY STS2 was not well centered and Jim thought this may contribute to the blend switch glitch, hence the work permit. Enter me.
At the EndY, I ramped down the sensor correction and then got distracted with something shiny and started looking at the front panel UVW monitors. Toggling the UVW/XYZ selector on the STS2 does not impact the signal going into the STSINF but when I toggled the T240 selector, the ISI tripped. Karen was around cleaning at the time but I suspect it was me. So with DVM I checked the T240 monitors and saw a few of the 9 (three t240 x U V & W) reading as high as 6+V. Some were mvolt level. Now I rezero'd all the T240 with selector in UVW position. Now all read < ~200mvolt. Toggle back to XYZ position.
Sensor correction ramped back on and ISI reisolated. Yes, did you note the glaring ommission? Yes I never did rezero the STS2, rats ankles!
Attached is the T240 X Y Z INMONs where the ISI trip and the zeroing are evident on this 1 hour long trend plot.
The second attachment is the T240 U V W monitors. Again very evident is the ISI trip and the rezero. Yes, very interesting...
The X Y Z signals all return to about where they started. I did zoom into them all and they are a little different but pretty much zero before zero after. The U V W trends though show a much different story. Six of the nine channels show a large step toward zero with the reset. The other three basically return to where they started after the rezero action. Still at least now, the six channels that were many thousands are now all under 1000 and only one channel of the nine remains above 1000. Maybe the blend switching will be smoother now. Maybe this rezeroing needs to be repeated to encourage the remaining to get closer to zero.
J. Oberling, P. King, E. Merilh
Over the weekend the FSS RefCav TPD dropped from ~1.4V to ~1.0V, so we went in to realign it. This was all done with the ISS off. Results:
The alignment was recovered entirely with a pitch adjustment of the RefCav input periscope mirrors. This completes LHO work permit #5622.
Title: 11/23 Eve Shift 24:00-8:00 UTC (8:00-16:00 PST). All times in UTC.
State of H1: Observing
Shift Summary: EX ISI is causing troubles again, but some changes to ASC seem to be keeping things under control for now
Onsite Support: Evan, Jeff, Jenne
Activity log:
IFO was unlocked when I arrived. Evan and Jeff were trying to diagnose EX.
1:00 I start initial alignment, this is hampered by AlignIFO and IMC nodes not cooperating. IMC node seemed to hang and refuse to lock occasionally, I had to re-request Lock. Lock X-arm IR was also uncooperative.
2:40 Finally to NLN. Except for EX slowly ringing up and then down, all's quiet.
A few details on the Xarm locking, in case it's helpful for someone else in the future:
We had the XARM gain turned up to 0.15 (which many people have been doing lately, when the Xarm is being fussy (nominal is 0.05)), however when it would catch lock, it would oscillate significantly. I think this was because the optical gain was too low (highest flashes and average transmission were about 0.8), and so we couldn't afford the 2 integrators that come on immediately after the lock is acquired. I had Jim disable the filter module triggering (by setting FM1 and FM2 of the XARM to "Man" rather than "Trig"), and we were easily able to acquire a smooth lock. After a few seconds the ASC brought the arm power to just above 1.0, and we switched the triggering settings back to normal. Alternatively, we probably could have turned the XARM gain up even higher, to make sure we weren't so close to the low edge of the phase bubble, but there didn't seem to be a reason to explore this more thoroughly.
J. Kissel While trying to characterize problems with HEPI / TIDAL / ISI / ASC (LHO aLOGs 23676 and 23676), I tried taking a swept-sine transfer function with three data points between 0.001 and 0.005 to charaterize the HEPI / UIM cross-over frequency (recall that the TIDAL crossover frequencies were never calibrated beyond "roughly," LHO aLOG 16255). However, upon starting the excitation, DTT gave the IFO a good kick on lots of ASC and LSC DOFs. It did *not* break the lock, but it certaintly came close, and any higher an excitation amplitude would have certaintly lost it. From a look at the time serious, it looks like DTT *tried* to ramp the signal, but chose a much faster ramp than is necessary for such a waveform. Attached are the start of the waveform, a zoom in on the ramp, and then a screenshot of the DTT params.
LLO had called and said they would be down for awhile. I'm going to finish doing a swept-sine through the INJ_HARDWARE filterbank from 5-500Hz. Previously I had only finished 500-2000Hz. The IFO intent mode has been turned off. This is WP#5595.
Previous swept-sine measurement was: aLog 23307 The following was done: * psinject turned off at 5:20 UTC * swept sine measurement started at 5:21 UTC * swept sine measurement ended at 5:48 UTC * psinject turned on at 5:49 UTC I've attached a plot of the transfer function and coherence between INJ_CW and DELTAL_EXTERNAL_DQ. WP#5955 is now complete.
Attached are results of computing a transfer function from H1:CAL-INJ_CW_OUT to H1:GDS-CALIB_STRAIN, using the same method used for the higher-frequency swept sine on Nov 11. The transfer function is generally flat and well behaved below 500 Hz and above ~35 Hz. The feature at 167 Hz appears to be an artifact of the swept sine measurement at that point being artificially split into several points. Figure 1 - Spectogram of H1:CAL-INJ_CW_OUT during swept sine Figure 2 - Spectogram of H1:GDS-CALIB_STRAIN during swept sine Figure 3 - Transfer function and coherence More detailed results can be found here.
The DTT template for doing the 5 to 500Hz swept-sine measurement is in the SVN here: template_cw_inj_sweptsine_5to500_20151121.xml The DTT template for doing the 500 to 2000Hz swept-sine measurement is in the SVN here: template_cw_inj_sweptsine_500to2000_20151111.xml
