Was it reported by Terramon, USGS? Yes, No
TITLE: 02/10 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Lockloss in the last 15 minutes of the shift likely due to wind. Started IA and am handing off to Jim.
LOG: See previous aLogs.
Appears to be due to wind. Gusts approaching 50 mph at EY. That BRS sure would be handy.
Observing for 16 hours. GRB alert at 2:48 UTC.
DQ Shift Feb 6th 00:00 UTC - Feb 8th 23:59 UTC
Pat Meyers
I've taken a look at 18k PI modes after they've had some problematic times over the past few weeks.
1. There are actually 4 modes in the 18035 - 18062 Hz region that are all aliased down from 47kHz, two on ETMY and two on ETMX. See peaks in first attachment. We currently have only two damping modes set up for this range (MODES 27, 28), both driving ETMY and have been mistaking ETMX modes for 'shifting' ETMY modes. Thus, two new damping modes need to be set up to cover the ETMX modes so we do not confuse the peaks. I can do this remotely but am waiting until some down time since this would take us out of Observe.
For reference, the modes in this group are roughly as follows: 18038 Hz ETMY (currently MODE 27), 18041 Hz ETMX, 18056 Hz ETMY (currently MODE 28), 18061 Hz ETMX.
I've looked back through months of alogs and have only found a few times where the ETMX-corresponding 18kHz frequencies have gone unstable. ETMY seems to hold the problematic frequencies, and usually the problem arises when we mistakingly put the damping filters around the ETMX frequencies thinking the peaks shifted.
2. These 18kHz modes shift in frequency roughly twice as much as their respective test mass' drumhead modes. I've looked at the ratio of df/f[18kHz] / df/f[8kHz] over about a dozen long locks; df/f of the two 18kHz modes on ETMX is an average of 1.7x df/f of ETMX 8kHz mode and an average of 2x for ETMY. ETMY has greater variance. The settling time to these values is 6 - 8 hours. For comparison, 15kHz modes shift ~0.7x the 8kHz shift. For example, in one 18 hour lock the 8kHz Drumhead of ETMX shifted 0.08 Hz while the 18061 Hz shifted 0.33 Hz. Thus, long locks and variable temp changes will more greatly change the 18kHz modes' frequencies and hence the additional phase aquired in the static damping bandpass, aka require damping changes. Note that 18kHz modes shift the opposite direction of 8kHz and 15kHz modes since they're aliased.
3. We've already guessed this, but PI problems over the past few months have primarily occured after the previous bad lock saw above average frequency shifts; in numbers, 'bad locks' seem to see df/f of 18kHz modes > 30ppm. This correlates to larger temp shifts as seen by the PEM temp sensors on the chambers - H1:PEM_CS/EX/EY_TEMPERATURE_BSC#_
_ _ _
We're currently working on a way to automate these larger frequency shifts, but obviously trying to commission some new things now is limited. For prevention going forward, I suggest watching the above PEM channels and regularly stopping at DC READOUT to check mode peak frequencies against BP filters. Both BP filter and PLL Set Frequency need to be shifted accordingly. Most of the PI problems like those we've seen the past months could be prevented with frequency pre checks and some sort of chamber temp monitor/alert system.
I've attached several examples of good and bad locks. Top plots show df/f of 8kHz drumheads, 15kHz, and 18kHz modes. Middle plots show df/f of either 15 or 18kHz mode over df/f of 8kHz mode. Bottom plots show PEM temp sensors on the outside of the optic chambers (with bogus units). 2nd (lock with very little temp change) and 3rd (lock with larger temp change) attachments are good, 4th and 5th are bad. By 'bad' I mean that lock had PI ring up at the end of it or the lock immediately after broke due to PI. 'Good' means we lost lock for unPI reasons and had no problem with the next lock.
TITLE: 02/10 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.33 μm/s
QUICK SUMMARY: Observing for 12+ hours. No issues were reported.
Shift Summary: Ran the A2L DTT script. The Yaw signal was a bit rung up around 20 Hz. Ran the A2L script while LLO was down.
Reviewed current work permits and next weeks planned activities at 13:00 meeting.
It has been a quiet shift with the IFO in Observing, (except for 8 minutes when I ran the A2L script), for the past 11.75 hours. Environmental conditions remain favorable.
Yesterday/Today there were periods of steady wind from 12 to 18mph with very occassional gusts to 25 and later calm conditions. Richard has got the wind sensors all set so as I'm looking at STS performance, why not. The wind tends to be from the SE to E (-X to edit [-]X-Y) edit [these are the variable wind from directions; the winds are travelling toward the NW/W] during this wind; the winter winds don't always follow our SW typical direction.
The four attached plots show ASDs for the four operational STSs during the windy period, ~2100utc 8 Feb for about an hour (thinck pale reference traces;) and, during the calm, ~0800utc 9 Feb (thin dark current traces.) I will only comment on the low frequencies below the secondary useism, 0.16Hz.
During the calm, the pronouced bump at 60mHz is very evident; I was going to call this the Primary useism but isn't that 0.085Hz? Anyway, with even this relatively moderate breeze (for LHO,) the affect on the seismometers is dramatic: Except for the fortunate ITMY, this 60mHz bump is buried on the X Y signals.
For the Z DoF, all the sensors show similar amplitudes and are unaffected by the wind, except ETMY, departing from the calm spectra below 55mHz and increasing by an order of magnitude at 10mHz. Is this real? The wind at EndY is more directly from the SE (-X) where the other buildings are hit more with an E wind. At EndX the wind is a steady 18mph compared to the EndY 12mph and edit[ ETMX] does not see theis Z channel affect. Could it actually be the building edit [or] ground conditions?
Also at EndY, the X DoF wind affect is much larger than all the other locations departing from the calm ASD at nearly the useism bump. At 10mHz, it is nearly an order of magnitude above the next lowest DoF (ETMY_Y) and nearly 2 above ITMY. Does this, combined with the response of the Z channel implicate the health of the ETMY instrument? Little speculative to compare given the relative locations but could the HAM2 instrument be better than the ETMY? I really don't want to think that as so many past examinations have implicated HAM2's health.
Ran ISI CPS sensor noise check. No apparent problems observed. Plots are posted below. Closed the FAMIS task.
model restarts logged for Wed 08/Feb/2017 - Mon 06/Feb/2017 No restarts reported
Ran the A2L DTT script. The Yaw signal was a bit rung up around 20 Hz. Ran the A2L script while LLO was down. Was out of Observing from 19:03 (11:03) until 19:11 (11:11).
Work Permit | Date | Description | alog/status |
6471.html | 2017-02-07 12:00 | Stop data acquisition and backup databases on conlog-test-master and conlog-test-replica. |
33970 33975 33983 |
6470.html | 2017-02-06 15:59 | DARM open loop gain transfer function measurement, Pcal to DARM transfer function measurement | 33942 |
6469.html | 2017-02-06 13:07 | ReCenter Beam return image: Take BRS and Sensor Correction out of loop, open igloo, center beam, wait, reinclude SC/BRS in loop. | 33976 |
6468.html | 2017-02-06 09:29 | Enter PSL enclosure and evaluate the position of the Input Beam on an IO beam dump steering mirror, related to alog 33915, where I show that images suggest beam has moved and possibly far enough to be clipping. No change in beam, just pictures (if possible) or description of beam on the steering mirror. |
33915 33977 33991 |
6467.html | 2017-02-06 09:14 | Place a dust monitor with an on-board pump in the closet next to the PSL enclosure where the makeup air is drawn into the PSL. This will record the particulate being drawn into the PSL enclosure. The dust monitor will be removed two days later (Thursday). | |
6466.html | 2017-02-03 13:28 | Troubleshoot PEM STS: access VEA when IFO state permits, read voltages, center masses, power cycle--Limit Time in VEA to 5 minutes. | 33999 |
6465.html | 2017-02-02 12:47 | Before the holiday break the timing fanout in the EE-Lab was directly connected to the MSR master. We will re-route this timing signal to come from the DTS fanout in the H2-building. Will require access to 3IFO area in H1 bld, and MSR underfloor. |
33974 33983 |
Previous W.P. | |||
6460.html | 2017-01-30 09:07 | Set the addresses on the beckhoff terminals installed at the tables. |
33782, 33971 |
TITLE: 02/09 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: One lockloss that I though may have been an unattended PI, but I talked to Terra and she thinks something else was going on. Had a few issues getting the OMC locked, but it eventually figured itself out after I fiddled for a while. Snow plowing since 13:03UTC killing our range and most likely data.
LOG:
I had to flip the noise eater, run an initial alignment, wait longer than usual for a well-aligned DRMI to lock (~12min), lose lock at SWITCH_TO_QPDS, struggle getting the OMC ready for handoff, and then good.
Did you get a VERBAL alarm or DIAG_MAIN message about the Noise Eater? Just curious. (Or should operators know to look for the Noise Eater when the IMC isn't locking.)
DIAG_MAIN will notify if the Noise Eater needs to be flipped.
This lockloss may have been caused by PI mode 27? It rang up 06:57UTC and was missed by Travis, but seemed to have turned itself around and began to slowly damp itself down. When I got on shift I also missed this mode somehow and it stayed at around 200counts for about 3 hours. I can't imagine that this was healthy.
18037 Hz ETMY mode; It shifted down in frequency (since its really an aliased down mode) during the long lock by ~1/2 Hz. BP filter should be double checked - there's about 2 Hz leeway above and below before you hit another mechanical mode, so BP could be widened. In attached plot, black is beginning of lock, red is during the ring up (27 hrs into lock). Peak at 18040 ish Hz is ETMX mode.
This was damping and below the usual break-lock amplitude when we lost lock, so likely wasn't the cause. I don't see the usual coupling down into DARM frequency bands that usually occur before a PI-induced lock loss.
Clued by TJ's comment in aLog 34018 about having to toggle the Noise Eater after this lockloss, I was curious as the possiblity of this lockloss being due to PSL FSS PZT oscillation. I have seen several locklosses at earlier steps in lock acquisition due to the PZT oscillation earlier in the week. In the attached plot, you can see that the FSS PZT oscillations and Noise Eater issues occur simultaneousely at 10:14:45 UTC. It seems more likely that this caused the lockloss than the 'below-lockloss-threshold' PI mode.
I turned CP5 heat lamps off at lunch today. I didn't reset the heat tape circuit breaker.
Turned it back on yesterday after snow/rain fall.