9/4 DAY Shift: 15:00-23:00UTC (08:00-16:00PDT), all times posted in UTC
Summary: Able to get a few hours of Observation time during the shift. Also had a few hours of PEM Injections by Robert. Coordinated a bit with LLO with regards to when to drop out of Observation as well. All of this is pointing us toward a goal of having long double-coincidence duty cycles for the next week so we can get an idea of the state of our machines going into O1.
Robert plans to continue with injections into the evening so he can have a lighter day tomorrow.
Handed off a nice H1 (~70Mpc) to Nutsinee with quiet seismic and slight winds.
Poll of Control Room Work: PCal/OMC model work, Calibration Analysis, PEM Injection analysis, Ops Script work.
Support: Had Commissioners around, but not needed since H1 was locked the whole time (since 16UTC / 10pm PST)
Day's Activities
ECR: https://dcc.ligo.org/LIGO-E1500373
userapps/cal/common/models/PCAL_MASTER.mdl
userapps/omc/h1/models/omc.mdl
userapps/omc/common/models/omc.mdl
h1calex, h1caley and h1omc were all successfully built but not installed. These will be installed on next Tuesday.
The seized up compressor on the supplemental chiller unit for the staging building, commonly described as the AAON Unit has been replaced, charged, and is now running at 100%.
Chris S. Joe D. Both 70% This week the guys have cleaned the original caulking and installed metal strips on 200 meters of tube enclosure on the top side. They have also cleaned the caulking on an additional 60 meters of enclosure.
I had stepped out the control room for ~15min, and when I came back the first thing I noticed was a YELLOW "OK" on the GWIstat screen. I asked around the Control Room to see if anyone knew why we were out of Science Mode (granted I should have announced my exit), but no one seemed to notice the drop from OBSERVATION.
I took us back to Observation Mode immediately since there was no reason given for having us out. I looked in the Verbal Alarm terminal, and did not see a note of the Intent Bit being changed. (So, I've talked to TJ about getting this in the Verbal Alarm script. And to also have time stamps attached to the Intention Bit alarms so we'll know when these come up.
Keita admitted he was the culprit; he opened a DTT session [which has an excitation], and then started it. (We tested this, while in Observation mode, and we were able to open this DTT session, which had excitation selected, and this did not drop us out. Robert & I thought that just opening a session would drop us out. He mentioned that maybe this is the case with AWG. We should test whether it can drop us out.). So this is when we were out:
16:19-16:29UTC Out of OBSERVATION
Addendum:
Prior to PEM Injections, Robert and I wanted to check if AWG does in fact have a different effect with regards to staying in Observation Mode with Excitation channels. Robert opened an AWG session (no drop), but once he merely selected an excitation in AWG, we were dropped out of Observation Mode. This is even WITHOUT hitting the "Set/Run" button!
When you do this, the DIAG_EXC guardian Node gets an orange box and has the message: EXC: [system] excitation!
We were dropped out of Observation at: 20:10UTC due to this excitation being selected (and NOT run) (this was different from what DTT did).
The noise below 30 Hz looks a bit non stationary, see the zoom in of the attached spectrogram.
The behavior of the noise reminds me very much of scattered light, but I'm not 100% positive right now.
For some reason Evan is reluctant to make a new post about it: LHO alog 21210, comment 5 (H1NB_2015-08-27_123000.pdf)
Due to a crazy big offset of -0.5 in Y_TR_B_PIT (for SOFT modes sensing), Y IR QPDB is almost always railing a bit in 24W operation, and Y IR QPDA is not too far.
Next time IFO drops out of lock, somebody needs to lower the whitening gain by 3dB and set a new dark offset for each quadrant.
These whitening gains are controlled by the ISC_LOCK guardian. We already lower them by 6 dB in the DRMI_ON_POP state (which produces the momentary fake jump in arm power that everyone asks about), so it sounds like we should be lowering them by 9 dB instead.
[Shamefully, we don't change the dark offsets when we change the whitening in this step.]
Shame.
DRMI_ON_POP now turns down whitening gain from 18 dB to 9 dB.
The landscapers will be out this weekend-Saturday and possibly Sunday for weed control in front of the OSB, Staging Building, and the LSB.
Patrick handed off an H1 which has been at Nominal Low Noise since about 5:30utc (10:30pmPST) with a range hovering around 70Mpc. There was a noticeable step down in range (~60Mpc) at 12:04UTC for about 30-60min (Patrick notes several ETMy saturations around 12:10UTC & Ed notes there were earthquakes aroudn 12:15UTC).
Injection around 11:15UTC?
Looks like we have been in Observation Mode since 6:00UTC, but GWIstat says we've only been in this state since about 11:15UTC (this isn't Peter's Burst from last night....maybe a Transient Injection? Or some other injection? Is there a schedule for these things??).
Today's Outlook: PEM Injections for good chunk of day
Will stay in Observation a little, but Robert says he said would like to start PEM Injections within an hour or so (~16:45UTC?), and will be PEM Injecting for a good chunk of the day so he does not have to do much on Saturday. Have just talked with Lisa at LLO and they will be interested when we go out of Observation, so they could also go out and do some much-need commissioning.
Seismically, we look fairly quiet with microseism noticeably trending down by 0.1um/s over the last 24hrs. Winds are also quiet.
ER8 Day 18, no restarts reported.
Per request by Robert Schofield, I am lowering the air flows in the LVEA to allow him to preform his injections. These will be going down from ~15000 CFM to ~11000 CFM. Since the weather is cooling down, I will leave these flows at this rate until something or someone convinces me otherwise.
12:45 UTC Christina here 12:51 UTC Karen here More SUS ETMY saturation alarms. Most if not all were coincident with glitches in the spectrum. List of all from verbal alarms script: SUS E_T_M_Y saturating (Fri Sep 4 8:13:12 UTC) SUS E_T_M_Y saturating (Fri Sep 4 8:28:3 UTC) SUS E_T_M_Y saturating (Fri Sep 4 8:28:5 UTC) SUS E_T_M_Y saturating (Fri Sep 4 10:40:16 UTC) SUS E_T_M_Y saturating (Fri Sep 4 10:51:18 UTC) SUS E_T_M_Y saturating (Fri Sep 4 11:15:5 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:24 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:26 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:28 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:10:30 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:47:13 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:47:26 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:47:29 UTC) SUS E_T_M_Y saturating (Fri Sep 4 12:48:39 UTC) SUS E_T_M_Y saturating (Fri Sep 4 13:24:44 UTC) SUS E_T_M_Y saturating (Fri Sep 4 13:24:46 UTC) SUS E_T_M_Y saturating (Fri Sep 4 14:44:33 UTC) Nice quiet shift otherwise. H1 remains in observing mode around 70 Mpc. Handing off to Corey.
A scheduled burst hardware injection was done early this morning, at GPS 1125390500 = Sep 04 2015 01:28:03 PDT, that was extremely loud. It was detected by Coherent WaveBurst (see https://gracedb.ligo.org//events/view/G181472) and also produced several MBTA triggers that were inserted into GraceDB, with (inferred) coalescence end times up to 37 seconds later. I have removed all future burst injections from the tinj schedule file so that no more will be done until we sort this out and make sure that future injections will have reasonable amplitudes.
Dan, Daniel, Evan
The addition of a 9.1 MHz bandpass on the OCXO output has removed the broadband excess noise between DCPD sum and null. The dashed lines in the figure show the sum and the null as they were three days ago (2015-08-31 7:00:00 Z), while the solid lines show the sum and the null after the filter was inserted.
Since at least June (probably longer), we've had a broadband excess noise between the sum and null DCPD streams. Stefan et al. identified this as 45.5 MHz oscillator noise a few weeks ago (20182).
In parallel, we switched the 9 MHz generation from an IFR to the OCXO (19648), and we installed Daniel's RFAM driver / active suppression circuit (20392), but the excess noise remained (20403). For a while we suspected that this was 45.5 MHz phase noise (and hence not supressed by the RFAM stabilization), but the shape and magnitude of the oscillator phase noise coupling (20783) were not enough to explain the observed noise in the DCPDs, under the assumption that the OCXO phase noise is flat at high frequencies (20582). For that matter, the shape and magnitude of the oscillator amplitude noise coupling were also not enough to explain the observed noise in the DCPDs, assuming a linear coupling from the RFAM (as sensed by the EOM driver's OOL detector) (20559).
Daniel et al. looked at the 45.5 MHz spectrum directly out of the harmonic generator in CER, and found that most of the noise is actually offset from the 45.5 MHz carrier by 1 MHz or so (20930), which is above the bandwidth of the RFAM suppression circuit. This suggested that the noise we were seeing in the DCPDs could be downconvered from several megahertz into the audio band.
Yesterday there was a flurry of work by Keita, Fil, Rich, et al. to find the source of this excess noise on the 45.5 MHz (21094 et seq.). Eventually we found circumstantial evidence that this excess noise was caused by baseband noise out of the 9.1 MHz OCXO.
Tonight we installed a 9.1 MHz bandpass filter on the OCXO output. This has removed the huge 1 MHz sidebands on the 45.5 MHz signal, and it also seems to have greatly lowered the coherence between DCPD A and DCPD B above a few hundred hertz.
The chain from OCXO to filter to distribution amplifier currently involves some BNC, since we could not find the right combination of threaded connectors to connect the filter to the amplifier. This should be rectified.
Also, it appears that our sum is lower than our null in a few places (400 Hz in particular), which deserves some investigation.
"NULL>SUM" problem is just DARM loop. You're talking about 10%-ish difference, and DARM OLTF gain is still 0.1-0.2 at 400Hz.
See attached.
I don't know how to obtain official DARM OLTF model, so I just took 2015-08-29_H1_DARM_OLGTF_7to1200Hz_tf.txt in
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/DARMOLGTFs/
The coherence for this OLTF measurement was much larger than 0.95 for the entire frequency range shown on the plot.
On the bottom is |1+OLTF|. I interpolated this to the frequency spacing of SUM and NULL spectra, and plotted SUM*|1+OLTF|, SUM, and NULL at the top.
Note that DARM OLTF template measures -1*OLTF.
Nice work. After O1 we can figure things out now you have narrowed it down.
Nice work!
Great job! Following up on the discussion during the commissioning meeting today, at LLO Evan's equivalent plot of the coherence between the two OMC PDs is already below 10^-3 (below 3 kHz).
Fil and I replaced the BNC cable with an SMA/N cable.
The attached pdf contains current Stage-1 and Stage-2 NB model performance of ITMY chamber for X,Y,Z and RZ dof. Fig 1- ST1 ITMY X Low frequency near microseism model performance is limited by the ground blend filter (HEPI L4C+IPS) 1-5Hz frequency band is limited by GND-STS passing through the sensor correction path 5Hz and above (upto 10Hz say) is limited by Stage-2 back reaction Below microseism model does not match with actual performance. (May be because of some tilt coupling?? But it looks like actual measurement is limited by the sensor noises (T240/CPS) via isolation filter. - Not sure about it) Fig 2- ST2 ITMY X Instead of T240 BLND OUT, I have used T240 BLND IN as the input (stage-1 displacement) to the ST-2 model. Though the model and measured GS13 are in agreement above blend frequency (250mHz), the shape between 1-3Hz are not same. The model output looks more like the input signal T240 BLND IN. May be a better input noise model will work better. Since the stage-2 model performance above ~1Hz is highly dependent on stage-1 displacement, we can san say that the Stage-2 back reaction on stage-1 can have effect on the final performance of the model. Fig 3 - ST1 ITMY Y Most of the features and model performance are same as X dof. Fig 4 - ST2 ITMY Y Though this one is same as ST2 ITMY X only thing I have noticed here is the actual IFO ST1 performance is better than ST2 between ~ 300-500 mHz. Fig 5- ST1 ITMY Z ST-1 model performance matches the actual measurement at almost all the frequency range of interest. The conclusions derived for ground model and Stage-2 back reaction hold here too. Fig 6- ST2 ITMY Z Unlike X and Y dof, the model performance between 60 to 250 mHz is quite good (I am still trying to figure out why this sort of discrepancy exists between these dofs ???) At the same time the mismatch between model and actual performance above 5Hz is noticeable. Model is over estimating the actual performance here (though the model has already included stage-2 back reaction in Stage-1) Fig 7- ST1 ITMY RZ Apart from the limitations of the model due to ground noise at low frequencies, the performance of this stage is mostly limited by CPS sensor noise via BLEND+ISO path. Fig 8- ST1 ITMY RZ Please DO NOT go through this figure. Still need to sort out the problems. Same sort of features can be seen in almost all the BSC chambers except BS where the stage-2 controllers are not in use.
T240 and GS13 sensor noise floors are added to the seismic noise budget plots.
This entry is meant to survey the sensing noises of the OMC DCPDs before the EOM driver swap. However, other than the 45 MHz RFAM coupling, we have no reason to expect the couplings to change dramatically after the swap.
The DCPD sum and null data (and ISS intensity noise data) were collected from an undisturbed lock stretch on 2015-07-31.
Noise terms as follows:
The downward slope in the null at high frequencies is almost certainly some imperfect inversion of the AA filter, the uncompensated premap poles, or the downsampling filter.
* What is the reasoning behind the updated suspension thermal noise plot?
* Its weird that cHard doesn't show up. At LLO, cHard is the dominant noise from 10-15 Hz. Its coupling is 10x less than dHard, but its sensing noise is a lot worse.
I remade this plot for a more recent spectrum. This includes the new EOM driver, a second stage of whitening, and dc-lowpassing on the ISS outer loop PDs.
This time I also included some displacement noises; namely, the couplings from the PRCL, MICH, and SRCL controls. Somewhat surprising is that the PRCL control noise seems to be close to the total DCPD noise from 10 to 20 Hz. [I vaguely recall that the Wipfian noise budget predicted an unexpectedly high PRCL coupling at one point, but I cannot find an alog entry supporting this.]
Here is the above plot referred to test mass displacement, along with some of our usual anticipated displacement noises. Evidently the budgeting doesn't really add up below 100 Hz, but there are still some more displacement noises that need to be added (ASC, gas, BS DAC, etc.).
Since we weren't actually in the lowest-noise quad PUM state for this measurement, the DAC noise from the PUM is higher than what is shown in the plot above.
If the updated buget (attached) is right, this means that actually there are low-frequency gains to be had from 20 to 70 Hz. There is still evidently some excess from 50 to 200 Hz.
Here is a budget for a more recent lock, with the PUM drivers in the low-noise state. The control noise couplings (PRCL, MICH, SRCL, dHard) were all remeasured for this lock configuration.
As for other ASC loops, there is some contribution from the BS loops around 30 Hz (not included in this budget). I have also looked at cHard, but I have to drive more than 100 times above the quiescient control noise in order to even begin to see anything in the DARM spectrum, so these loops do not seem to contribute in a significant way.
Also included is a plot of sensing noises (and some displacement noises from LSC) in the OMC DCPDs, along with the sum/null residual. At high frequencies, the residual seems to approach the projected 45 MHz oscillator noise (except for the high-frequency excess, which we've seen before seems to be coherent with REFL9).
Evidently there is a bit of explaining to do in the bucket...
Some corrections/modifications/additions to the above:
Of course, the budgeted noises don't at all add up from 20 Hz to 200 Hz, so we are missing something big. Next we want to look at upconversion and jitter noises, as well as control noise from other ASC loops.