Hang, Dan Brown
Only EY was down from this dolphin crash so this recovery was quicker than some of the others.
Initial alignment went fine except for PRC align. It seems the PRC1 filter changes made the other day (46151) made it unstable for initial alignment, probably too much gain. In PREP_PRC_ALIGN Guardian we switched off all the filters apart from FM1 (-20dB), it converged slowly and with FM1 off it still works.
Only one ALS lockloss during LOCKING_ALS, DRMI locked in about 20s.
Took about 2 hours until we were up again - although most of that was checking CO2Y table for leaks and figuring out what was up with PRX initial alignment rather than the Dolphin crash itself.
I expect to me hear for ~90 minutes or so and will make a comment to this entry when I am leaving.
Corner Station update -> I'm done inspecting the Corner Station and am off to do the other buildings. Note that I had to add 850 ml of water to the TCSY chiller. I walked the entire run of piping from the chiller to the table and found no evidence of a leak. Additionally, there is no evidedence of water spilling of off the table (did not open doors). For now, I've notified Dan Brown. He said that he checked the table earlier today but found no leaks. I suggested that he check the table again and also the TCSX table in case the chillers have been switched or mislabeled.
I checked TCS X and Y tables and couldn't see any water on the table.
Finished with the site inspection. Here are the highlights:
1) Had to add 850 ml of water to the TCSY chiller to bring it up from the, as found, 7.6 cm to 10.0 cm indication.
2) HAM7 AIP is off scale high -> we will deal with this after the new year.
3) Double doors (to HVAC computer room) between the auditorium and rear entrance of the LSB won't close completely and had to be blocked closed.
4) The exterior-most doors of the LSB main entrance were found to be locked -> At one time, these were going to be left unlocked and the interior main entrance doors were going to be locked instead so that people could get in from out of the cold? -> I left these as found.
5) Could not enter into the LDAS area adjacent to the VPW -> won't take my key or RFID "thingy".
6) Warehouse (dirty side) was unlocked -> I locked it.
7) Y-end chiller bypass valves (both) are open. The CS chillers are bypassed as well but all of the other out buildings have at least one of two valves closed -> I left as found as I am out-of-date as to what is normal these days.
8) Chilled water pressures are below the old nominal value of 30 psig in most buildings but I did not add glycol solution as this could be the result of the "new-since-my-era" Variable Speed drive units running below 60 Hz and I am likely out-of-date as to what is normal these days.
9) I could not investigate the X2-8 gauge/charger/etc. as they have changed the ocks on the BT doors and the gate code didn't work to unlock them -> I trended this gauge and it is on again, off again over the past day or so. I noted that the solar panels are "squeeky" clean and not obstructed.
1605 hrs. local -> Leaving site now
The pressure gauge at X2-8 location near X-end is reading high and might have failed in a new way due to lack of solar power. Adjacent pressures are normal so the control room can ignore this alarm. VAC team will investigate when on site.
X2-8 gauge back on again - I'm heading to the site to do an inspection and just noticed that his gauge is back on scale again. Hmmmm...
Added 350 mL water to TCSY to bring level from 8.6 cm up to 10.1 cm today. This appears to be a higher-than normal drop over the last couple of days, with the caveat that the previous reading was without optimal eyeglasses. At a minimum, it seems wise to keep an eye on the readings. Also, topped off Wallace with 50 mL.
Did a visual inspection of the CO2Y table for leaks, I checked on the table and around the back near the periscope. I couldn't see any obvious leaks or water anywhere.
Added another 1900 mL water to TCSY chiller at 10:20 am on Dec 31, 2018.
Unfortunately our 25 day streak of no Dolphin crashes came to an end at: Dec 25 2018 08:56:14 PST
I've captured all the Dolphin and system logs. I'll work on restarting the models soon.
If anyone is in the control room today, please call my cell phone and we can complete the recovery.
This is new - no action needed at this time.
During the power up, there is some variation of the DRMI optical gains. This can lead to loop instability and lockloss. This could be mitigated by:
I have made a new low pass filter to give some more margin. Its more stable with no noise penalty, so it is now loaded by default.
Plots:
Looking through the elogs, the most exciting LSC input matrix element seems to be POP_9_I -> SRCL. It gets the most attention.
Over the past couple of weeks, I've been measuring it every couple days. It moves around with the thermal state, sometimes changing sign.
Today I measured and minimized the coupling from a PRM excitation to SRCL_IN1 at 85 and 250 Hz. The matrix coefficient I found is the same as Gabriele and Sheila found on Oct29, but not what Stefan set it to on Nov5. I guess Stefan had a semi-warm measurement.
Putting the element back to 0.038 from 0.024 reduces the PRCL 2 SRCL coupling by a factor of 10. With the element set to 0.024, at PRM motion actually shows up 2x stronger in SRCL (in terms of meters) than in PRCL. This was measured at thermalized 23 W, so could change at 30 W.
Rana, Hang
After adding the res G's at 0.47 Hz our ASC loops appeared to be quite and stable at 25 W for more than 20 mins. However, as we tried to power up to 28 W, our dithering loops, especially the yaw ones started to drift away. This then triggered the ~ 0.5 Hz oscillation in CHARD YAW and then in other ASC loops. In the second attempt we tried to increase the dithering loops gain as we power up. However this did not kept the dithering loops stable. While the error signal still crosses zero, the oscillation seemed to be growing. The further the soft dithering loops' error signal deviated from 0, the more sever the 0.5 Hz oscillation in CHARD YAW. Or it might be the other way around, as the CHARD YAW RMS increases, the spot motion naturally made the dithering loops oscillates more.
============================================================
In addition to power up, we also tried to go to LOWNOISE at 20 W.
In the lownoise asc state, we reduced the CHARD YAW dc gain to 0.7, giving it roughly 3 Hz UGF. Then we could re-engage the ELP10 (FM2) filter to reduce its noise.
However, we kept losing lock at LOWNOISE_ESD_ETMX, specifically when we tried to transition ETMX to ITMX+ETMY. The ITMX part seemed fine. The ETMY ESDOUTF_DC_OUTPUT was zero before the transition, which seemed weird. In the guardian there also seemed to be no explicit commands setting up ETMY ESD in that state.
About the ETMY transition: we haven’t been using that ESD since it has a non working quadrant, so the bias shouldn’t matter. I’m not sure what else could be wrong.
Rana, Hang
Yesterday we saw the 0.47 Hz oscillation showing up in basically all the PIT ASC loops at 23 W and became unstable at 25 W.
We thus measured DSOFT P OLTF and the result was attached to this entry. The cyan/pink traces were some old measurements done back in October at 2 W. The OLTF measured today at 20 W was the blue/red traces (We have good measurement in the 0.3-0.6 Hz region yet below 0.1 Hz we could not get good). In both measurements we saw a pair of zeros at 0.47 Hz, which was the freq we saw the oscillations.
To compensate for this feature, we put resgains at 0.47 Hz with Q of 3 and height of 12 dB in DSOFT P (FM9), DHARD P (added to the boost10W FM5), and CHARD P (added to boost10W FM5). The same filter was also created for CSOFT P yet it didn't seem necessary to engage it for now. After these changes the 0.47 Hz feature was basically removed from the PIT loops at 23 W.
An oscillation at similar frequency also appeared in CHARD YAW, and it was mitigated if we turned off the FM4 boost10W filter in CHARD YAW.
With those modifications we did not see oscillations at 23 W any more.
====================================================
In addition, we also improved our DSOPT/DHARD PIT decoupling for the B path (AC coupled; for damping the dPdTheta)
The new matrix we used for DSFOT P B path input was
| TRX_A | TRX_B | TRY_A | TRY_B | |
| -0.0193 | 0.0176 | 0.00335 | -0.08375 | DSOFT_P B |
In the second attached plot we compared the performance of this new input matrix to the old one (routed to DC5). The DHARD dither was at 23.3 Hz and the DSOFT dither at 21.1 Hz.
The new input matrix not only rejects hard mode much better, but also has a significantly improved SNR.
most of the ASC filter banks have a lot of junk loaded in that's the dregs of history. Many of the filters have a name like '2.3t' which mean nothing. Some of the low pass filters have extra notches placed to handle suspension resonances rather than as a real low pass.
We're starting a cleanup with PRC1. I deleted several unused filters. PRC1 pit and yaw now use the same filters. Since we only use this for sub-Hz control, there's no need to put little notch tweaks at ~3 Hz any more. The subtle ELF filters have been replaced with elliptic low pass.
In the attached plot, the CYAN + BROWN + MAGENTA were the old filters. In the new loop, magneta is gone and Brown has been replaced w/ Orange. Works fine like this.
The new FM5 is a 0.1 Hz AC coupling filter. We turn it on once we turn on the dither loops so that PRM is used to center the beam on ITM, and we just use POP QPD for AC control of PRM.
Just FYI, here are the hard/soft control signals after Hang added the RG to compensate the 0.5 Hz zero. These are driving the PUM (and TOP below 0.1 Hz) so you may multiple by 1/f^4 above a few Hz to convert to angle.
the interferometer locked by itself after we left this morning. It stayed locked for 10 hours (until the 6.4 EQ in Tonga a couple hours ago).
Some troubles re-locking:
Rana, Hang
Over the last 4 hours, the ALS DIFF turn on broke the lock dozens of times; we've modified the DARM loop to compensate.
We looked at the time series to diagnose the problem. There was a ~2 Hz oscillation in DARM at the turn on. At this point, according to my old log entry (and confirmed by sweeps today), the L1/L3 xover is ~1.2 Hz and the bottom of the DARM-DIFF phase bubble is 2 Hz. So it seems like when the alignment is bad (i.e. DIFF beatnote is ~3 dB low) we get a 2 Hz transient when the DARM gain is ramped on.
In the script there was a 20 dB filter ramping over 5 seconds and the filter module gain ramping over 2 seconds; both were happening simultaneously. We have now commented out the filter and just ramp the gain. WE increased the gain in this step by 3 dB so that it is more resistant to high wind, useism, EQ, etc. Also changed the 2 Hz integrator in DARM2 into a 0.2:1 boost to get more phase at 2 Hz; there is already an integrator in the SUS-M0 stage so don't need one in DARM.
Tested several times so far so good.
In the future would be better to:
The guardian often gives the error "unhappy with inconsistent use of tabs and spaces in interferometer", as seen in the logs whenever we reload ISC_LOCK.py.
This is because python sadly doesn't know what to do if you give it an extra space here or there in the code. Today I used emacs 'M-x untabify' to heal the whole file.
Errors are gone. Commited to SVN before and after.
** however, not sure if my SVN commits are getting recorded. The latest commit I did has #18435, but svn log only shows commits up to #18336 on Dec-13
Two points Guardian related here:
"inconsistent use of tabs and spaces" - Thank you Rana for doing this. Unfortunately, as long as control room users continue to use improper setting on their text editor (most often gedit), this will continue. To all users that edit Guardian code, please make sure that your editor is set to use a tab with of 4 and make tabs into spaces. If anyone needs help with this, please let me know and I can gladly show you where this setting is.
Lastly, for the svn commits, to see the most recent logs from the command line, one must do a "svn update" on that directory. If you had already done this, then we have some issues to figure out...
Contrast Defect Ratio at 2 W = 8.4 +- 0.2 ppm Contrast Defect is as follows:The electric fields associated with this equation are shown in the fourth attachment. When DARM is locked on RF at 2 watts and the OMC is locked, we get about 11.8 mA, or 14.0 mW of power on the OMC DCDPs. This means the DARM offset is around 29 pm according to this plot. During this measurement, we move the DARM offset from 29 to -29 pm and see what happens. Procedure: 1) Lock OMC while DARM is locked on RF 2) Zero the QPD offsets for OMC ASC by switching to OMC dither alignment, zeroing, and moving back to QPD control 3) Zero the OMC LSC dither control signal by offloading to PZT2, then stop the feedback, parking the OMC on the carrier fringe 4) Change DARM1 TRAMP to 120 seconds 5) Move DARM1 OFFSET through zero (in this case from 9e-5 cts to -9e-5 cts) 6) Re-engage OMC LSC by stopping input, clearing history, unholding output, and restarting input. This will find the fringe again quickly for the next measurement. Parameters during measurement:
Input Power = 1.89 W PRG at 0 pm Offset = 46.8 +- 0.1 DCPD Responsivity = 0.858 A/W DCPD Quantum Efficiency = 0.98 OMC DCPD Dark Offset = 7.2e-5 +- 3e-5 mW (Found at the last time the IMC was OFFLINE) OMC DCPD NULL/SUM = 0.0060 +- 0.0015 Measurement GPS Time = 1229475480Differences between 0 and 29 pm DARM offset:Value 29 pm 0 pm 29 pm/0 pm ------------------------------------------ PRG 46.5 47.0 0.99 TRX [cts] 1502. 1518. 0.99 TRY [cts] 1555. 1572. 0.99Assumed to be one:- IMC Transmission - Input Faraday Transmission - Output Faraday Transmission - OMC Transmission - Mode MatchingNot yet considered:- RF45 Transmission through the OMC - Source of contrast (differential lens)Dark Port alogs: 45753 DARM offset calibration 45734 OMC DCPD Sum/Null Matrix
I've created FRS12051 to cover this crash. The ticket has been closed with an estimated 1.0 hours lost commissioning time.