Title: 12/26 Day Shift 16:00-24:00 UTC (8:00-16:00 PST). All times in UTC.
State of H1: Observing
Shift Summary: In Observing for my entire shift and 20.5 hours total now. No issues this shift. Very quiet wind and seismic.
Incoming operator: Jim
Activity log:
21:30 Kyle on site for CP3 maintenance
21:41 Kyle starts his drive to CP3
22:30 Kyle done at MY
22:46 ~12 cars to LSB for afternoon tour
23:05 CW injection running alarm
23:22 CW injection inactive alarm
What a difference 24 hours make. The wind has remained below 10mph and the useism continues to trend down now at 0.6um/sec on average. There have been no audibles for saturations and the range trace is very lovely. Best to all-H
~1405 hrs. local Sampled ~ 1.5 quarts of LN2 at the spigot prior to the LLCV to examine appearance -> I did find a few suspended solids but cannot conclude that they originated from the LN2 or if they were liberated from the fitting that had been left open to the air uncapped Opened LLCV bypass valve 1 turn ccw then partially opened exhaust check valve bypass valve (to reduce back pressure) -> liquid evident at exhaust after 30 seconds -> Let fill for 90 seconds I placed a pan at the exhaust to collect liquid -> I did not see anything suspended in the colorless liquid -> I also noted that the local dewar mechanical gauge was indicating 110" which would translate to > 30% if the CDS transducer and mechanical gauge were calibrated to each other -> I cycled the valves to zero the mechanical gauge and, in doing so, changed the transducer output (was indicating 24.2% before cycling valve and 25.4% afterwards) I am surprised that, prior to the "plugging" earlier this week, the LLCV was, on average, open 19% to maintain a pump level of 92% but since has been manually kept at 15% open and yet the pump overfills after only a minute or so via the LLCV bypass circuit.
We have been cruising along at ~80 MPc for 18.5 hours currently. Wind and seismic are very calm. No issues to report.
O1 day 99
model restarts logged for Fri 25/Dec/2015 No restarts reported
Title: 12/26 Owl Shift 08:00-16:00 UTC (00:00-08:00 PST). All times in UTC.
State of H1: Observing at 80 Mpc for 12.5 hours.
Shift Summary: Very quiet shift. Got a high alarm for FMC-CS_LVEA_REHEAT_1B. Temperature reached 39 degC, 102 F.
Incoming operator: Travis
Things have been quiet. Useism is trending downward. Hardly any ETMY saturation tonight. Very stable BNS range. Wind below 5mph. LLO has been down because of wind.
Title: 12/25 EVE Shift 00:00-08:00 UTC
State of H1: NLN
Shift Summary: Started out rough, but after a couple rounds of IA roulette, the IFO locked, quiet times since.
Activity log:
00:30 Kyle off site
3:30 Locked, Observing
~06:00 I notice EX ISI starting to ring up
07:30 EX gets worse, I drop the IFO out of observe, change blends, back to NLN
Uneventful shift once in observing mode.
No wind to speak off, all antropogenic are quiet. Inspiral range pegged at 80Mpc.
About 2 hours ago the EX ISI started ringing up again. As the situation was getting worse over the last few minutes, I decided it was time to switch blends. Attached plot shows the StripTool I was watching with the EX CPS locations and IMC-F (the gray trace). I switched the Y DOF blend first (green), it changed smoothly, but didn't reduce the motion. Then I changed the X blend (blue), which settled things down pretty much immediately. I thought it was interesting that IMC-F seemed to lead the swings of the ISI, ie IMC-F seemed to change direction a little before the ISI did. Don't know what that means, but interesting.
I add for the operators: If an ISI is ringing up, and you change the beam direction blend to the 90 blends (X for EX, Y for EY), you should change the perpendicular blend as well. ASC probably doesn't care, ALS doesn't, but 20 micron motion of the tables is bad just on principle.
Finally back to Observing. No idea what changed, but I did yet another initial alignment, then we were finally able to get DRMI. Before that, the closest thing to a DRMI lock I could get was some hash on the PRMI striptool that looked a lot like the PRMI to DRMI transition. I did switch ETMX ISI to all 45 blends (99% sure that's irrelevant) and touched TMSX in pitch a tiny amount (probably also irrelevant, but not sure). Dark MICH is also still broken, but I've been getting PRMI locks all night and there are other ways to get rough BS alignments.
Nutsinee had a tough time on OWL shift with H1 behaving badly until approx. 15:10 UTC, when it mysteriously improved. But the bad behavior returned around 17:00 UTC for about 30 minutes and I spent some time investigating its cause during this interval. Microseism was not too bad and wind was calm. There was no indication of excess noise on H1:LSC-MOD_RF45_AM_CTRL_OUT_DQ or coherence of that channel with DARM. Looking at a spectrogram of H1:CAL-DELTAL_EXTERNAL_DQ one can see broadband bursts across the bucket turning on and off suddenly (1-s resolution), with durations verying from a few seconds to about 30-40 seconds. Sometimes these were accompanied by loud bursts in the 10-20 Hz region, other times not. I looked for burstiness in other chnnels that was correlated with this. There was nothing well correlated in seismometers or microphones (either on the floor or in e-bays) or OPLEVs. There were strong similarities on ASC-MICH_P and _Y, weaker on DHARD_P and Y, nothing on DSOFT_P and _Y, nothing on CSOFT, very weak similarities on CHARD and SRC2 P and Y. I am not familiar enough with the LSC/ASC couplings to know if this is just leakage of the length fluctuations onto ASC channels or if alignment is causing the problem. I looked at IMC_F an _L, MC2 TRANS which showed no indication that the cause came into the IFO on the light from the IMC. I tried looking at PRC ASC signals but they looked crazy in frequency with no time dependence (??). However SUS-PRM_M3_NOISEMON has large burst in the 10-30 Hz region on all OSEMS. HVETO finds these good for veto channels. Travis was not finding anything bumping against its limits. At 19:42:12 we lost lock. This coincides with the arrival of the maximum ground shaking in the 0.03-0.1 Hz from an EQ in Afghanistan, although the 1-3 Hz region showed sharp elevated shaking several minutes earlier. We are having a hard time getting back to locking.
It looks like the RF45 monitor sometimes does not see the RF45 noise. We will consider three times on the 25th. The reference time is 4 UTC, when there was nothing bad in DARM and the RF 45 was quiet. At 7:30, the RF 45 is obviously bad as seen by the monitor channel. At 17:04, there's very similar noise in DARM, but now the RF45 monitor stays at its reference. The first plot is DARM for the three times. The shape and amplitude of the excess noise for the two bad times is very similar. The second plot is the spectra of the RF 45 monitor at these times. It easily sees the problem the first bad time, but at the second bad time (corresponding to a burst of noise in Fred's spectrogram) it stays at the reference. The ASC-MICH channels look to be good witnesses of this noise. I think they're made from RF36, but that should be sensitive to RF45 issues. The third plot is the coherence with h(t) of RF45 and MICH_Y during the reference time. It has a few lines but is otherwise zero. The next plot shows high coherence with both during the first bad time. The last plot is coherence during the second bad time. There's just a tiny bit of coherence with the RF 45 witness. The MICH_Y coherence is basically the same as the other bad time. This is worrisome because the RF 45 monitor is not always a good witness of the noise in DARM (and other channels). But it doesn't seem to be a problem with noise in the witness channel masking the RF 45 junk. Maybe this points to the problem being somewhere that the monitor is not always able to see.
The reason that there's excess noise in PRM_M3_NOISEMON is just because of the control signal from PRCL. The attached spectrum shows that PRCL gets worse during the bad times, and that's just getting fed to PRM_M3. In fact, MICH, PRC, and SRC all have a similar noise shelf up to 30 Hz during the bad time. They all involve some RF 45 signal in their production. The POP_A RF9 and RF45 photodiode signals, in the I and Q quadratures, all have similar shelves except for 9Q (second plot). That's the only one that's not used for control, so I think it's seeing the noise impressed by the MICH/PRC/SRC loops all suppressing the RF 45 noise.
Title: 12/25 Day Shift 16:00-24:00 UTC (8:00-16:00 PST). All times in UTC.
State of H1: Locking
Shift Summary: The last half of the day has been spent trying to lock. Nothing out of the ordinary, just the usual run of the mill issues you have seen in a hundred aLogs. Ran IA twice since the AS spot looked pretty poor each time. Haven't made it past locking DRMI. Hopefully Jim has some more tricks up his tattoo sleeves.
Incoming operator: Jim
Activity log:
23:06 Kyle to MY for CP3 refill
23:30 Kyle back
1515 hrs. local -> Opened LLCV bypass valve one turn ccw -> less than 1 minute until liquid was evident out of the exhaust -> This is much different than has been recorded by Gerardo in the past few days (3 - 4 minutes) and is likely due to differences in our interpretations. Also, I routinely open the instrument air bowl drain valve at the pressure regulator near the LLCV actuator to verify that dry air is being supplied to the actuator -> Today this looks to have resulted in a disabling of the Start - Stop for this on the MEDM screen, i.e., the indicator bar went from green (START/enabled) to red (STOP/disabled). I had to re-enable this.
1610 - 1620 hrs. local I added a shim pack around CP3's LLCV valve stem with ~0.020" gap such that, in the event of a loss of instrument air pressure, the valve can now only stroke closed 0.020" from its current position.
We received 2 CS temp. high alarms at 3:25 and 3:30 PST.
Most likely due to a 6.2 EQ in Afghanistan.
O1 day 98
model restarts logged for Thu 24/Dec/2015
2015_12_24 21:00 h1nds1
2015_12_24 21:16 h1nds1
freeze up of h1nds1, looks like the first reboot didn't take?
here is a plot of the free disk space on /ligo for the past three weeks showing the results of yesterday's work. Note that the regular drops in free space happen on Tuesday morning's, it would be good to know what we do during maintenance which takes about 10GB of disk.
I updated the quad matlab model parameter file with SolidWorks estimates of the test mass and PUM rotational inertias. Previously these values were output from a fitting algorithm using the measured resonance frequencies, see log 10089.
The updated parameter files are quadopt_fiber.m (the generic quad file) and h1etmy.m. quadopt_fiber.m is the general quad file, h1etmy.m is specific to H1ETMY. They are currently identical since we have the most measurements from H1ETMY. Both live in this directory
.../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production
This update was done because there has been some discussion on the accuracy of the test mass inertias in the model. The solidworks mass values for the test mass and PUM agree with the measured weights to 0.2% and 0.07% respectively. This doesn't tell us the error for the inertias, but since they are small, it is a good sign. Previosuly, the inertias were chosen by the aforementioned fitting algorithm. These had differed from solidworks by 2% in roll (I3x) and yaw (I3z), and 7% in pitch (I3y). Further, Shivaraj pointed out that the pitch inertia from the fit was smaller than the yaw, which can't be true due to the flats on the optic. The assumption is that the solidworks estimates are more accurate.
With the updated inertias on the PUM and test mass, I made a new fit of the model, floating all the d's of each stage, the inertias of the top mass and UIM, the spring stiffnesses, and the vertical stiffness of the fibers. I wouldn’t put too much faith into the accuracy of these values. The best we can do is try to make a model that matches the information we have. If we ever get new or better information (such as good L-P coupling data) we can update the model with that then.
The plots in the first pdf show a comparison of the measured H1ETMY transfer functions to the previous model fit and the new one. They all match pretty well. The new fit appears to match the top mass L to P measurement better.
The plots in the second attached pdf show the ratios of the new fit to the old fit for the damped L to L TFs from all stages to the test mass. The damping loops were imported from those currently running at LHO. These ratios all appear to be within 10% of unity.
rev 7359: now reads foton files for main chain and reaction damping
rev 7436: Changed hard coded DAMP gains to get the correct values for LHO ETMX specifically.
rev 7508: Restored damping filter choice for P to level 2.1 filters as opposed to Keita's modification. Cleaned up error checking code on foton filter files, and allowed handling of filter archive files and files with the full path.
rev 7639: renaming lho etmy parameter file
rev 7642: Adding custom parameter file for each quad. Each one is a copy of h1etmy at this point, since that one has the most available data.
rev 7646: added ability to read live filters from sites, and ability to load custom parameter files for each suspension
rev 7652: updated to allow damping filters from sites from a specific gps time (in addition to the live reading option)
planned future revision - seismic noise will progate through the damping filters as in real life. i.e the OSEMs are relative sensors and measure the displacement between the cage and the suspension.
no recent (at least 4 years) functional changes have been made to this file.
- rev 2731: name of file changed to quadopt_fiber.m, removing the date to avoid confusion with Mark Barton's Mathametica files.
- rev 6374: updated based on H1ETM fit in 10089.
- rev 7392: updated pend.ln to provide as-built CM heights according to T1500046
- rev 7912: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit. Same as h1etmy.m.
- rev 7640: created the H1ETMY parameter file based on the fit discussed in 10089.
- rev 7911: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit. Same as quadopt_fiber.m.
I've now copied over the h1etmy.m updates to the other quad parameter files: h1etmx.m h1itmx.m h1itmy.m l1etmy.m l1etmx.m l1itmy.m l1itmx.m.
I also updated each parameter file with its repective measured test mass weight from https://galaxy.ligo.caltech.edu/optics/. Note, Kiwamu had already put in the h1etmx test mass weight on Aug 7, 2015.
With the exception of test mass weight, as before all quad parameter files are the same. The intention is to make each file more unique as we collect more information on each suspension (such as test mass weight).
Replotting TF_ratios_damped_M0L1L2L3_to_L3L_2015_12_24.pdf to zoom in on the y axis.