Displaying reports 44681-44700 of 88413.Go to page Start 2231 2232 2233 2234 2235 2236 2237 2238 2239 End
Reports until 11:13, Tuesday 06 November 2018
LHO VE
chandra.romel@LIGO.ORG - posted 11:13, Tuesday 06 November 2018 - last comment - 17:28, Tuesday 06 November 2018(45048)
EY roughing pump & purge air tested

Turned ON QDP80 roughing pump for a couple of hours along with the purge air skid to test in preparation for next week's vent. Purge air dew point measured -43degC.

Comments related to this report
kyle.ryan@LIGO.ORG - 17:28, Tuesday 06 November 2018 (45073)

I ran the vent/purge supply (Kobelco skid), QDP80s and levitated the Vertex, YBM and XBM turbos (so as to charge batteries) at the Corner Station -> Note that the Kobelco compressor wouldn't start initially.  It displayed an "RTD error" which wouldn't reset and then displayed "-115 F" for all temperatures.  After powering on/off a few times it finally cleared up and then started/ran normally.  After 2 hours of run time the dew point, as measured at the YBM vent/purge valve, was -43C.  All of the air temperatures on the Kobelco were much cooler than normal (the lube oil temperature was normal) due to the lack of demand. 

H1 SUS (CAL, CDS, ISC)
jeffrey.kissel@LIGO.ORG - posted 10:54, Tuesday 06 November 2018 - last comment - 11:48, Tuesday 06 November 2018(45047)
SDF (safe) files reconciled for all SUS
J. Kissel, J. Driggers

In prep for the ISC triggering shut offs, as well as a change in configuration to the dolphin network, all suspension models will need to be restarted today. As such, I've reconciled all suspensions safe.snap SDF files. I attach a full detail of what I've accepted / reverted, but aside from capturing the latest alignment offsets, the only suspensions that had major changes that needed reconciling were the QUADs -- ETMX, ETMY, ITMX, ITMY. With the help of Jenne, we did our best to accept or revert changes on those suspensions that were related to the past ~week's worth of commissioning.
Non-image files attached to this report
Comments related to this report
patrick.thomas@LIGO.ORG - 11:47, Tuesday 06 November 2018 (45053)
ITMY
"- accepting violin mode matrix 2_11 from 0.0 to 1.0
- accepting turning on mode 11, and several phase tuning filters."

Also from violin mode damping work.
patrick.thomas@LIGO.ORG - 11:43, Tuesday 06 November 2018 (45052)
"- Violin mode matrix 02_20 from 1.0 set to zero (controlled by guardian?)"

This was probably from the violin mode damping I was working on last night. I have been using mode 20 as a test filter module.
jenne.driggers@LIGO.ORG - 11:48, Tuesday 06 November 2018 (45054)

The one weird thing that I wasn't sure of, was the TRAMPs for ASC-AS_A_RF45 I and Q segments 1-4.  I'm not sure why those were set to 30sec, but I reverted them to 0sec.

H1 SQZ (SQZ)
nutsinee.kijbunchoo@LIGO.ORG - posted 10:29, Tuesday 06 November 2018 (45019)
A quick look at A/EOM pump injection

Terry, Daniel, Haocun, Nutsinee

 

After running into several problems of EOMs not working as they should, we finally installed a New Focus 4002 EOM in the green path with half wave plate at the input and output rotated 45 deg.  The whole set up is to use EOM as an amplitude modulator so we can inject intensity noise into the OPO loop. We have always had a lot of unexplained noise and we're hoping intensity fluctuation+crystal interaction could explain at least some of them.

 

We hooked up SR785 swept sine excitation to the EOM while OPO is locked. Got about 7% of intensity modulation. TTFSS I-MON goes to CH2 and SHG launch diode readout (monitors what goes to the fiber coupler) goes to CH1.

 

This data is then multiplied by OPO open loop gain and calibrated into Hz/mW 

(V_ttfss/V_GRPD) * (FWHM Hz/ I-MON PDH Vpk) * (GRPD Transimpedance V/A) * (GRPD Responsivity A/W) 

PD gain and dual DC photodiode amplifier board transfer function are included. 

The diode response "pole" is around 8kHz, which is the turn around point of the plot above.

(A fun fact, the response of the EOM to swept sine signal drops as you go towards DC)

If we were to repeat this transfer function with OPO locked, we got a tail biting effect going on as well. 

Note that the phase here could change depending how much power is going to the temporary EOM we installed. When the rejected (wrong polarization) diode reads about the same as the launch diode the phase above can flip 180 deg. This is likely due to EOM crystal changing the output beam polarization depending how it's heated. With this unreliable response we concluded that the A/EOM set up is no good for power fluctuation control.

 

Moving on.

 

Now that we have Hz/mW calibration, we can use the launch diode to figure out how much phase noise do we expect LO to see (calibrated into mW then multiply by Hz/mW).

Note that at 100Hz the frequency noise is almost as bad as Mephisto free running (100Hz/sqrt(Hz) at 100Hz). I pointed out the 1.3kHz line because it also shows up in OPO spectrum, and it is what killed our lock when HAM6 was in air (the peak was much worse in air). This line is to be investigated. 60kHz line may or may not matter. Could it be a laser PZT resonance (?). I will be posting more noise budget (OPO, LO) in a separate log. 

 

Now convert the plot above into radian and calculate the rms.

It's 1 rad /sqrt(Hz) at 344Hz and doesn't go down to a mrad until 39kHz. The LO loop have to have suppression of 40dB at 100Hz and a UGF of at least at 39kHz to keep sqz phase noise down to mrad level (note that this is all green projection so there's a factor of 2 down, but that still doesn't help). This is why using a PFD and slow path signal to OPO PZT alone didn't work. Currently we feed the fast path signal to TTFSS additive offset which gives LO loop a UGF of ~50kHz.

 

Images attached to this report
Non-image files attached to this report
H1 AOS
gabriele.vajente@LIGO.ORG - posted 09:02, Tuesday 06 November 2018 - last comment - 13:13, Tuesday 06 November 2018(45042)
BruCo scan for 1225344730

A BruCo scan for the period listed in 45013 is available here. There are a lot of interesting coherences in the low frequency region (10-30 Hz), some of them already identified and corrected (see 45036). None of them is near one, but they are all not neglegible and very likely enough to explain most of the noise when summed:

A couple of channels are intriguing, and I don't have a good explanation for them

Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 09:30, Tuesday 06 November 2018 (45043)

Follow up on IM1 coherence. 

Looking at the IM1 VOLTMON signals ('H1:SUS-IM1_M1_VOLTMON_LR_OUT_DQ', 'H1:SUS-IM1_M1_VOLTMON_UR_OUT_DQ',  'H1:SUS-IM1_M1_VOLTMON_LL_OUT_DQ', 'H1:SUS-IM1_M1_VOLTMON_UL_OUT_DQ'), the four channels appear very different. In particular, LL has large glitches, and LR has somewhat smaller glitches, while UL and UR looks stationary. The plot below shows the spectra and time series of the four channels. Solid lines in the top panel are spectra computed with the entire 600s period, while the dashed lines are spectra computed only selecting the shaded time range in the bottom plot, where there are no big LL glitches (but probably still some small or medium size glitches). 

 

The coherence with DARM is there only if we include the glitches. So it's worth investigating this channel to se what's going on there. Maybe it doesn't explain the noise in DARM (and the coherence is an over estimate), or maybe it can explain some of the DARM glitches.

 

Images attached to this comment
gabriele.vajente@LIGO.ORG - 09:52, Tuesday 06 November 2018 (45045)

Looking more closely to the LL glitches, here's a spectrogram of DARM and IM1 LL. There are a few glitches in both channels, but only one DARM glitch seems to line up with a IM1 glitch. However, if you zoom in, it looks like the IM1 glitch happened a second before the DARM glitch. So the coherence might just be a coincidence. I think it's still worth investigating the IM1 coil drivers.

 

Images attached to this comment
sheila.dwyer@LIGO.ORG - 13:13, Tuesday 06 November 2018 (45057)

Thanks Gabriele. 

The coherence with POP LF was gone last in last night's lock, attached is a coherecnce taken at 15:33 UTC Nov 6th.  This could have coupled through the one of the ASC loops (CHARD Y or SRC2P) that we rolled off better yesterday. 

Images attached to this comment
LHO General
corey.gray@LIGO.ORG - posted 08:06, Tuesday 06 November 2018 (45039)
Morning Status: Tues Maintenance!

TITLE: 11/06 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY:

H1 ISC (ISC)
craig.cahillane@LIGO.ORG - posted 02:03, Tuesday 06 November 2018 (45038)
MICH Feedforward First Pass and Iteration
We did two rounds of MICH to DARM feedforward tonight by actuating on the ETMs as opposed to the ITMs.

We did the usual measure MICH_OUT to DARM_IN1 with FF off, then measured MICHFF to DARM_IN1, divide them and fit a zpk to them (via Lee's iirrational).  That gave us the result in PDF 1, and the orange lines in PNG 1.  This filter is named "Nov5" in the MICHFF filter module.
The coherence was largely reduced, to be sure, but the performance was mediocre between 20 and 35 Hz due to bad phasing.  

So we iterated on the fit using Jenne's convenient feedforward paper.  We retrieved the current filter in the MICHFF filter module using my filterModuleStateExtractor (call it alpha), and found beta = 1 - (DARM IN / MICH OUT)/[alpha * (DARM IN / MICHFF)], the iterative filter TF.  This gave us the fit in PDF 2, and is the red line in PNG 1.  This filter was implemented as "Nov5b" in the MICHFF filter module.
The coherence was reduced further in the 20 - 35 Hz band.  

This process was useful because the first round of the feedforward reduced the noise sufficiently to give a clean TF of the high-Q notches we see around 18 and 25 Hz.  I figure MICH to SRCL to DARM accounts for most of the remaining coherence, we haven't redone the SRCL to DARM feedforward to the ETMs.
The change from ITM to ETM actuation and MICHFF FM engagement is updated in LOWNOISE_LENGTH_CONTROL.

The templates for the MICH FF measurements are:
/opt/rtcds/userapps/release/lsc/h1/scripts/feedforward/MICH_to_DARM_excitation.xml
/opt/rtcds/userapps/release/lsc/h1/scripts/feedforward/MICHFF_to_DARM_excitation.xml

The results for the DARM IN1/MICH OUT and DARM IN1/MICHFF are actively read by the script in /ligo/home/craig.cahillane/Git/Feedforward/MICH2DARMfeedforward.ipynb.  
Images attached to this report
Non-image files attached to this report
H1 ISC (ISC)
georgia.mansell@LIGO.ORG - posted 00:53, Tuesday 06 November 2018 (45037)
Lines around 18-28 Hz

Just a quick note in case these show up again:

During one of our locks this evening a number of lines showed up in DARM between 18 and 28 Hz (blue trace, 1225511648) and stuck around for ~half an hour. Their amplitude appeared very stable. We tried to track them down in LSC and ASC signals but didn't find anything convincing.

I turned off the violin mode damping, and the lines (gradually) went away (red trace), when I turned the violin mode damping back on the lines did not return. Not sure if this was because of the violin mode damping or something else. (note: the extra broadband noise in the red trace is due to the feed-forward tuning that was going on in parallel).

Images attached to this report
H1 AOS
sheila.dwyer@LIGO.ORG - posted 23:08, Monday 05 November 2018 (45036)
Summary alog

There have been a lot of things happening today, most of which is other logs, but I thought it would be useful to make a summary:

A noise budget including all of these improvements is attached, there is a trace here for HAM3 coupling as well as SRCL and MICH, but there is a risk that we are double counting now because the HAM3 noise couples to DARM through MICH (and SRCL). The last attachment is a comparison of the DARM spectrum tonight to Friday night in grey.  The improvements today have brought us to the early O2 reference below 25 Hz.  

 

 

Images attached to this report
H1 ISC (ISC, SUS)
hang.yu@LIGO.ORG - posted 19:02, Monday 05 November 2018 (45033)
Reducing LSC MICH noise by reducing the local damping?

Peter, Hang

One brute-force way of reducing the LSC MICH noise is to reduce its loop gain, and then we can move the LP filters to lower freqs. To achieve so we need to know the LSC MICH noise budget at low freq (which dominates the rms) and see if it is possible to reduce the input noise to the loop.

In the first plot we show the noise projection to MICH ctrl output based on f-domain MISO coherence analysis. The low-freq rms is largely dominated by the BS local damping noise (mostly from L, with a non-negligible contribution from P and Y). As a comparison, the largest ISI contribution (from BS ISI itself) is almost a factor of 10 below the BOSEM noise.

Since LSC MICH is already controlled with a clean, interferometric signal, it might not be necessary to have high gains on the local damping loops anymore. Thus we might want to reduce the local damping gain and thus reduce the amount of input noise to MICH. This should allow us to further reduce MICH noise to DARM by lowering MICH BW.

Images attached to this report
H1 ISC
stefan.ballmer@LIGO.ORG - posted 18:58, Monday 05 November 2018 (45035)
SRCL and MICH OLG in nominal low-noise
We measured the SRCL OLG in nominal now-noise and found it at 20Hz, with plenty of phase margin. We lowered it by 3dB ( H1:LSC-SRCL1_GAIN = -8.8 ), to 15Hz, which seemed to help DARM at 30Hz.

We also looked at MICH - it currently has a 6Hz UGF. Attached is a OLG measurement, but I am not sure I trust the phase at 6Hz. Craig and SHJeila are now working on MICH FF, which currently is worse than O2, and limiting DARM.
Images attached to this report
H1 ISC
stefan.ballmer@LIGO.ORG - posted 18:50, Monday 05 November 2018 (45034)
POP_A_RF9_I ---> SRCL tweaked
We fine-tuned the LSC SRCL input matrix again today by driving PRCL length at 32Hz and 135Hz, and minimizing the lines from the SRCL error signal: 

POP_A_RF9_I ---> SRCL was 0.038 and was set to 0.024

This reduced  the PRCL to SRCL coupling by a factor of 14 to 30 initially, cleaning up the SRCL error signal nicely. However, we noticed that in the next lock the coupling again came up some, to a net reduction of about a factor of 5.
We added this settings to lscparams.py.
H1 ISC
gabriele.vajente@LIGO.ORG - posted 16:27, Monday 05 November 2018 (45030)
Model of SRCL feed-forward instability

I made a rough but representative model of why the SRCL feed-forward causes instabilities. The model works quite well in predicting an instability at about 1 Hz when the SRCL feed-forward is engaged and DC-coupled.

The model is based on:

With the feed-forward off, the model reproduces well the open loop transfer functions. The key thing to consider here are however the closed-loop responses of the two coupled loops. The plot below shows three traces: in blue (hidden by the green trace) the case without feed-forward, which is known to be stable (as confirmed by the open loop gain); in orange the case with the SRCL feed-forward on, but without the high pass: this trace shows a "wiggle" around 1 Hz; in green the case with feed-forward on and high pass at 10 Hz (this trace hides the blue trace).

 

So the model explains quite well that adding the current 10Hz high pass remove any perturbation to the closed loop gain at 1 Hz. Morevoer, we can take the ratio [closed loop gain with DC-coupled feed-forward] / [closed loop gain without DC-coupled feed-forward] and fit it. The fit contains indeed an unstable pole at about 1.03 Hz. So the model explains how the interaction of the SRCL feed-forward with the SRCL and MICH loop creates an instability.

Finally, if we reduce the geometrical coupling of BS to SRCL to 10% of the value we get by actuating only on the BS (in other words if we send the MICH control to SRM or SR2 or SR3 and cancel 90% of the coupling), the model predicts that the 1 Hz instability is gone, see the plot below for a zoom of the closed loop transfer function around 1 Hz. Blue trace: stable, no SRCL FF; orange unstable, just with DC couple FF and MICH driving to BS only; green stable, with DC coupled SRCL FF and MICH driving to both BS and SRC, with a precision of 10%.

 

So the model gives us two ways (at least) to fix this instability, by reducing the MICH / SRCL cross coupling:

 

 

 

Images attached to this report
H1 ISC (ISC)
craig.cahillane@LIGO.ORG - posted 16:22, Monday 05 November 2018 (45029)
MICH Feedforward on/off Comparison O2 and O3
Sheila, Craig

I gathered a bunch of times of MICH excitations with feedforward on and off for O2 and O3 to see how well we're doing now as opposed to the past.

We seem to be doing an order of magnitude worse now than we did in O2.

Template exists at /ligo/home/craig.cahillane/Git/IFO/LSC/data/MICH_to_DARM_excitations_O2.xml.

MICH Excitation Times:
O2 MICH FF off: July 1 2016, 9:14:00 UTC
O2 MICH FF on:  June 14, 2017, 00:20:05 UTC
O3 MICH FF off: Nov 4, 2018, 10:29:37 UTC
O3 MICH FF on:  Nov 3, 2018, 22:47:00 UTC
Images attached to this report
H1 General
cheryl.vorvick@LIGO.ORG - posted 16:21, Monday 05 November 2018 (45031)
OPS Day Summary:
H1 AOS (AOS)
cheryl.vorvick@LIGO.ORG - posted 16:10, Monday 05 November 2018 (45028)
OpLev Inspection - Weekly FAMIS: 11190

OpLev trends for a week - NOTE SR3 optical lever was turned off today for a test, and is still off,  so the change in it's signal is understood.  See TVo for more info.

Images attached to this report
H1 PSL (PSL)
cheryl.vorvick@LIGO.ORG - posted 16:03, Monday 05 November 2018 (45027)
PSL weekly Report FAMIS: 10985

Laser Status:
Front End Power is 33.26W (should be around 30 W)
70W Output Power is 75.6W
Front End Watch is GREEN
70W Watch is GREEN

PMC:
It has been locked 0 days, 6 hr 29 minutes (should be daysweeks)
Reflected power = 14.87Watts
Transmitted power = 43.86Watts
PowerSum = 58.73Watts.

FSS:
It has been locked for 0 days 3 hr and 17 min (should be dys/weeks)
TPD[V] = 2.939V (min 0.9V)

ISS:
The diffracted power is around 2.2%
Last saturation event was 0 days 3 hours and 17 minutes ag (should be days/weeks)


Possible Issues:

H1 ISC
jenne.driggers@LIGO.ORG - posted 15:30, Monday 05 November 2018 - last comment - 17:51, Monday 05 November 2018(45026)
SRC2 ASC semi-coherent with DARM

SRC2 is pretty coherent with DARM (attached .png, bottom right corner pink and cyan).  I did some injections, so that Sheila can stick these into the noise budget (.xml attachments).  But, we should roll this QPD loop off faster.

Images attached to this report
Non-image files attached to this report
Comments related to this report
hang.yu@LIGO.ORG - 17:51, Monday 05 November 2018 (45032)ISC

After Jenne notice the problem, we put some extra LPs in SRC2 loops.

For the SRC2 P loop, we lowered it DC gain by 3dB from 200 to 140 and added a 4th order ellip filt at 10 Hz with 40 dB attenuation.

For SRC2 Y loop, we tried to put a LP as aggressive as the PIT one but it broke the lock once. So we lowered the SRC2 Y loop gain by 6 dB from 200 to 100 and used a 4th order ellip filt at 12 Hz with 30 dB attenuation.

The LPs seem to improved DARM noise below 30 Hz. See the attached figure.

Images attached to this comment
H1 ISC
stefan.ballmer@LIGO.ORG - posted 14:06, Monday 05 November 2018 - last comment - 08:36, Tuesday 06 November 2018(45013)
H1 quiet stretch
Attached is the DARM spectrum, DARM coherence with some auxiliary channels, and the LSC auxiliary error point spectra for a quiet stretch on Saturday:

1225344730 (Nov 4 2018 05:31:52 UTC).

Note that - compared to Aug 21 2015, PRCL has an excess noise bump up to 60Hz, and an increased high frequency flat noise level (I hesitate to call it shot noise).
That bleeds slightly over to SRCL. Hoverer, the linear noise coupling, at least below 30Hz, is dominated by SRCL.

Gabriele might also post a bruco for this stretch.
Also note that this is from the same lock as Shaila's noise budget (alog 44998)
Images attached to this report
Comments related to this report
georgia.mansell@LIGO.ORG - 15:09, Monday 05 November 2018 (45025)

I re-ran Kiwamu's OMC DCPD cross-correlation template on this quiet lock stretch (it is hard to find enough time between the big DARM glitches to get a useful number of averages). See attached: blue is the DARM spectrum, and red is the correlated noise. I updated the calibration in this template to match the TF calibration of the DARM FOM DTT template.

A quick by-eye comparison of this and the O1 and O2 cross correlated noise: it looks like we are currently somewhere in between.

Images attached to this comment
gabriele.vajente@LIGO.ORG - 08:36, Tuesday 06 November 2018 (45041)
Displaying reports 44681-44700 of 88413.Go to page Start 2231 2232 2233 2234 2235 2236 2237 2238 2239 End