The simple excuse might be that apparently not all the Isolation Gains were zero.
Okay, HEPI and ISI tripped from a HEPI Pump Station VFD OU3 fault. Upon trying to recover, operator was unable to untrip the WD. The T240 was riled up and touching the 32k limit and pressing the WD Reset button just tripped the platform again immediately with T240. Additionally, JeffK noticed that the H1:ISI-ETMX_ST1_WD_MON_CURRENTTRIG was not RED(on T240) even when the T240 was still banging on the rail [indicating the T240 was being ignored although I can't say I know that based on model.]
Checking the model as a refresher, if all the ISO gains are zero, the ST1 ISO STATUS is zero and the T240 is ignored (text read, not my understanding of the model logic at this time although I believe it to be true from experience.)
So looking at ISO gains & WD signals, first plot, 10 minutes: You see the three attempts where the WD_MON_STATE goes to 1 and immediately tripping back to damp only (state3) and the first trigger remains 2 (T240.) So even though the ISO GAINs are zero and the ISO STATUS remains zero, attempts to clear the WD trips it back blaming the T240s.
The fourth attempt to clear the watchdog state succeeds but shows a situation I do not understand. You see all the ISO gains going to 0.1 with the ISO status switching to 1 and then back to zero when the gains go back to zero, as expected. Did the Guardian do this? The first step of the ISO gain ramp up is to 0.01, not 0.1; you can see this on the gains toward the end of the traces.
My second plot shows the 6 horizontal T240 signals (the verts never hit 32k) and I checked overlying the curves that no attempt to clear the WD was made when none of the signals were at 32k. The last attempt to clear the WD was after all the T240s are off the rail and while the weird brief gain switch to 0.1 occurred, the WD state remained 1 and recovery succeeded.
So why did the gains step up to 0.1? That may be an aside study. And, why did the WD fail to clear while the T240s were hitting the rail even though the T240 should have been out of the 'loop?'
I'll keep looking. Is it related to the HEPI tripping? That was kinda why the T240 MON was developed. In this case, HEPI was reset and had completed its isolation steps. Was the WD circuit not getting the ignore the T240 signal? Work ongoing, guess I should do an FRS.
FRS 8823
TITLE: 08/22 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:
Most of Maintenance was complete around noon. Around 1pm started on an InitialAlignment, & unfortunately, the Y-arm was a bit off and this took me a long time to get back (but Sheila helped out). Finally after getting ALSy back, the
Had several tours today.
HEPI Pump Controllers died. Hugh & I brought them back (he had to drive to both end stations).
TCSx flow rate trippped TCSx laser. Rebooted interlock box & reset the servo relock the laser. (Peter & Thomas)
Made a pseudo LVEA Sweep post-Maintenance Day (Turned OFF lights and confirmed WAP was OFF).
H1 to NLN at 23:22utc & Sheila is currently running a quick measurement.
LOG:
Maintenance Activities:
here is a 12 hour, minute trend plot of the outside temperatures at LHO in degF. The time axis is centered around the time of the eclipse.
I have compiled the results of in-air measurements during installation and in-vacuum measurements from the alogs; 14231 LLO (including corrections mentioned in alogs 21652 and 27901) and 17610 at LHO (including corrections mentioned on the comments).
In the case when a frequency split is shown on in-vacuum measurements we have taken the average of both frequencies. I have grouped these numbers per front and back fibres, then per test mass and then per detector, finally I obtained the difference as (in-vacuum – in-air) including the sign:
We notice that in most cases the frequency difference is always positive, so frequency increases when moving the suspension to in-vacuum.
The increase in frequency is always a few hundred mHz (mean of 0.3Hz and median of 0.4Hz), with a clear outlier on LLO_ITMY_FL (which as explained here seems to be involved with uncertainty in the identification).
There is not clear difference in frequency variation between front and back fibres (especially no sign difference) which would indicate pitch effect.
However, notice that as per the Technical document T1700399 the expected increase in frequency due to buoyancy is of 0.14Hz, and the variation in frequency due to pitch angles of 2mHz is of 0.33Hz (although that would be an opposite sign change between front and back fibres). Therefore while the observed changes cannot be explained through pitch and buoyancy alone, they are of the same order.
Further discussions on the results presented here has led to realize that the in-air measurements of the violin modes fundamental frequencies have a potential error of about 0.25Hz (as an example here are measurement results for LHO ITMX suspension). In base of this and to better understand the actual differences between in-air and in-vacuum measurements, now that we have very accurate measurements in-vacuum, it would be informative to measure in-air values once the suspensions are taken out.
The in-air measurements have so far been done by acoustically driving the violin mode resonances. During this measurements the frequency of the driving acoustic signal is changed as a sweep sine. Because the in-air Q of the violin modes is considerably less than the in-vacuum values of 1 billion, if the sweep sine drive is not done with suitable slow pace then the observed a violin mode excitation at a frequency on the sweep sine which actually correspond to a previous frequency of the sweep but took some time to ring up. Under this assumption, if the sweep sines were driven down (from high frequencies to lower frequencies) then there would be a consistent error on the measured in-air frequencies with values being lower than in-vacuum ones.
A way to improve the acoustic excitation could be by building a tower of speakers so that they could inject more energy into the violin modes of the fibres. Also be sure to drive the sweep sine at enough low pace or inject random noise excitation instead. Finally a lot of information could be gained by in-air measurements of higher order harmonics, this would help on characterization and understanding of higher order inharmonicity as well as higher order mode identification.
In order to proceed with the in-air measurements of the violin mode and its harmonics during the installation of the suspensions in the near future (as well as measuring the already install suspensions once removed), we have built in Glasgow a line array of 24 speakers of 60 cm length to match the length of the fused silica fibres. Its lightweight and compact design make it suitable to locate it parallel and in close proximity to the fibre that wants to be excited.
This line array produces considerable sound from 300Hz and well above several kHz making it suitable to excite the fundamental mode and up to the 6th harmonic and beyond.
A more complete description can be found on the technical document T1700414T1700414.
It is relevant to this alog to remember that while preliminary FEA modelling of the actual fibre profiles measured during installation of the LHO ITMX suspension (end of March 2014), has been used to predict in general terms the observed departure of the frequencies of the violin mode harmonics from whole multiples of the fundamental (“inharmonicity”):
However this preliminary results show that this prediction is not yet accurate to the few Hz level required for identification:
In order to complete the list of possible causes for the different inair and invacuum measured violin mode frequencies, I add next the contributions suggested recently by Norna, Dennis and Jon Feicht:
Violin modes frequency variations due to air damping
Air damping lowers the in-air measured violin mode frequency by a value inverse proportional to the violin mode’s Q-factor. Such that the maximum frequency for a damped oscillator (fm) is related to the undamped maximum frequency (f0) by:
fm = f0 ∙ sqrt[1-1/(2∙Q2)]
A quick look at recent in-air measurement on the LHO alog 38743 suggest a Q of at least 100 in-air at the ~ 500 Hz fundamental mode. This would give a in-air measured frequency value of the fundamental of 0.012Hz lower than in-vacuum.
Violin modes frequency variations due to mass/length of the fibre decreasing as the water desorbs from the silica fibre in vacuum
The mass loading on the fibre, due to water adsorption in-air, should in principle cause the in-air measurement of the violin mode fundamental frequency to be lower than in-vacuum, as once much of the water is pumped off the fibre in vacuum the frequency should increase. Dennis Coyne calculated that about ~3500 monolayers of water (each 2.5 angstroms thick) would be necessary to cause a 1 Hz shift at 500 Hz, due to mass loading alone. It is commonly asserted in vacuum literature that stainless-steel surfaces of a vacuum system exposed to air can start with "hundreds of monolayers of water".
However fused silica is hydrophilic and the interaction of silica surfaces and water is complex; Surfaces of silica under water can swell and form layers of silica gel1. The modification of the fused silica surface by the chemisorption and physisorption of water may even lead to a reduction in the elastic modulus of the fused silica in the outer layers.
References
[1] V.V. Yaminsky, et. al., "Interaction between Surfaces of Fused Silica in Water", Langmuir 1998, 14, 3223-3235.
Didn't catch when this happened, but see on the Seismon (compact) medm window that "SEISMON DEAD". The "Keep Alive" is flashing on both Seismon screens.
When there haven't been any earthquakes for a while (I think about 7 hours, but I sure of how to verify this), there are processes that clean up the event files that seismon generates and leave the directory empty. The way the epics code is written, this means the clock that we use for the diag_main test and "seismon dead" light on the compact seismon screen stops updating, which makes that diagnostic confusing. I just noticed that last night, and I'm not sure what to do about it, but it's one of the few tests I can think of that are visible outside of the machine. The only way to be sure at this point is check that the list mostly agrees with the USGS page (seismon spams some events, occasionally misses one) and watch to see if the diag_main message clears when a new eq shows up.
This morning I completed the weekly PSL FAMIS tasks.
HPO Pump Diode Current Adjustment (FAMIS 8436)
With the ISS OFF, I adjusted the operating current of the HPO diode boxes. All currents were increased by 0.2 A, changes summarized in the table below:
Operating Current (A) | ||
Old | New | |
DB1 | 49.6 | 49.8 |
DB2 | 52.5 | 52.7 |
DB3 | 52.5 | 52.7 |
DB4 | 52.5 | 52.7 |
I did not adjust the operating temperatures of the DBs. The ISS is now back ON and the HPO is outputting 155.0 W; I have attached a screenshot of the PSL Beckhoff main screen for future reference. This completes FAMIS 8436.
PSL Power Watchdog Reset (FAMIS 3664)
I reset both power watchdogs at 16:34 UTC (9:34 PDT). This completes FAMIS 3664.
TITLE: 08/22 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
Wind: 4mph Gusts, 2mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
Maintenance Day!
Jumping headlong into Maintenance day. Have a pretty full board. Full steam ahead!
TITLE: 08/22 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Quiet shift, 1 lockloss, PCAL lines turned off briefly
LOG:
12:30 Lockloss, no apparent cause, back to observing 13:00
14:20 Turned off PCALX lines for a measurement, back on 14:35
Adam Mullavey called and said he needed to run a measurement for today's maintenance. His measurement needed the PCAL X lines turned off, so he had me turn the amplitudes on those lines down to 0. Unfortunately, he ran into some permissions issues and couldn't do his measurement. LHO was out of OBSERVE from 14:21 to 14:34 for this, but as far as I know the only differences during that time were from turning off the pcal lines. Attached screen shot shows the settings we were running while observing. All the oscsin and osccos amplitudes were zero'd for the planned measurement. I've reverted them to the pictured settings now.
The end Y BRS is continuing it's slow drift and is getting close to going out of range, but should survive through the end of the run. It's possible, however, if it gets rung up by people working in the area, it could cause a problem for the damping loops and leave the BRS in an unusable state.
TITLE: 08/22 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY: 39.5hr lock, many tours for the eclipse party. Quiet shift overall.
A. Urban, on behalf of the calibration group
The C00 vs. C01 comparison pages have been updated and include all C01 data from 2016-11-30 through 2017-08-01.
As part of this analysis, I've got updated PCAL-to-DARM ratio trends at 36.7, 331.9 and 1083.7 Hz (attached below).
Plots of both magntidue and phase residual timeseries trends are attached. These trends are computed by demodulating 300-second segments at each PCAL line frequency, then averaging to get a magnitude and phase out of each channel. In practice, I break up each 300-second segment into overlapping 100-second chunks, apply a Kaiser window, and then average over chunks to get a less noisy measurement. (It's basically Welch's method, except I'm demodulating rather than computing a PSD.) Finally, I remove most outliers that are due to locklosses and loud transient glitches. The same analysis was done on Livingston data; see L1 aLOG 35501.
In each plot below I show PCAL/strain trends for C00 (blue) and C01 (red) data. The trend shown in aquamarine applies a correction for f_cc to C01 data at the appropriate PCAL line frequency. Gray shaded regions correspond to times when we had a break in O2, once during the holiday season and once for commissioning work.
At mid and high frequencies, everything continues to be in order at the PCAL lines. You can see that in the bucket (331.9 Hz) all systematics are accounted for by f_cc and only very small (~1%) statistical fluctuations remain in C01. At high frequency (1083.7 Hz) there's a slight systematic offset at the level of 1% or so in magnitude and 1-2 degree in phase, which is consistent with Craig's error budget. However, in the C01 low frequency line there is a mounting phase offset prior to the May vent that becomes worse after the break: the offset is 2-3% in magnitude and about 2 degrees in phase from June all the way through August. I suspect this has to do with spring detuning in the signal recycling cavity, and will follow up on it soon.
J. Kissel I've processed the data from LHO aLOG 38232, in which I was looking to see if the complex, high frequency dynamics found in the UIM (L1) stage of H1 SUSETMY (see LHO aLOG 31603). Plots are attached; note that I've used the former 2016-11-17 data for ETMY. To guide the eye, I show the calibration group's dynamical model used during O2. Data shown with a coherence threshold of 0.75 or greater. I've not yet compared this against the unphysical, fitted update to the QUAD model that Brett developed for H1 SUS ETMY in CSWG aLOG 11197 It looks like - All suspensions see the "unknown" ~165 Hz resonance, though interestingly ITMY's mode appears to be split. ETMX and ITMY's are *strikingly* similar. - only ETMY and ITMX show what Norna suspects is the "UIM blade bending mode" at ~110 Hz. ETMY's is indeed the ugliest. - All but ETMX show evidence for resonances between 290 and 340 Hz, which are likely the (Suspension Point to Top Mass) wire violin mode fundamentals weakly excited by the UIM excitation. (see LHO aLOG 24917, T1300876) - All suspensions show their (UIM to PUM) wire violin mode fundamentals between 410 and 470 Hz (see LHO aLOG 24917, T1300876) - ETMY and ITMY's wire violin modes are *strikingly* similar; ITMX's modes are surprisingly low Q. - We don't see the TOP to UIM wire violin modes likely because I didn't excite up to high enough a frequency; they're between ~500-510 Hz for ETMY (modeled at 495 Hz). So now the question becomes -- what's the physical mechanism for this huge mystery resonance that's seen virtually identically in all QUADs? It seems quite a fundamental feature. Why is it split on ITMX? It would be nice to have similarly detailed measurement of L1's QUADs, but all evidence from calibration measurements on L1's ETMY UIM stage point to this same feature (see the discrepancy between model and measurement for the UIM stage, e.g. in 2016-11-25_L1_SUSETMY_L1_actuation_stages.pdf LHO aLOG 29899). Further, it's *still there* before and after their Bounce/Roll mode Dampers (BRDs) have been installed (i.e. the same feature is seen in O1 and O2 CAL measurements; the above linked measurement was after BRD install).
If anyone needs to fit this data to try out their FDIDENT skills, the data from the above concatenated transfer UIM to TST functions is attached, in the same format as before for ETMY. Analysis script lives here: /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/FullIFOActuatorTFs/ process_H1SUSQUAD_L1_HFDynamicsTest_20170814.m
I'm attaching the l2l st2 gs13 measurements for ITMX that we used for closeout after install. The 160 hz feature doesn't seem to show up on the ISI. The 300 hz feature maybe does? I don't think it's very conclusive.
TITLE: 08/21 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 7mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: 31.5hr lock, rode thorugh a few earthquakes, eclipse event tonight.
Committed the following modified files to SVN repository.
The minutes from the 12:00 weekly pre-maintenance meeting, usually held at 09:30. Planned Tuesday Maintenance items: (1). The window may extend past 12:00 due to TMDS Testing at End-X (2). Jeff K. needs IFO up for 15 to 20 minutes after 08:00 to run BSC ISI coupling measurements (3). Jeff K. Running charge measurements (4). Jason will be making the weekly PSL Diode current adjustment (5). Possible cleanroom moves (WP #7116) (6). Filiberto will hold off in dressing new cables into HAM6 rack until next week.