Displaying reports 44081-44100 of 88549.Go to page Start 2201 2202 2203 2204 2205 2206 2207 2208 2209 End
Reports until 10:53, Monday 10 December 2018
H1 ISC (DetChar)
gabriele.vajente@LIGO.ORG - posted 10:53, Monday 10 December 2018 - last comment - 10:53, Monday 10 December 2018(45803)
SRCL noise subtraction

This is a follow up to my previous elog entries on SRCL non-stationary noise subtractions (45403 and 45508), and to the recent observations that SRCL noise contribution to DARM is closer than predicetd by the noise budget (either from coherence 45785 or from a direct noise injection 45792).

I further developed the technique described in 45403 and 45508 to identify and model non-stationary noise couplings. Now I can directly estimate a parametric, realizable and stable linear filter for each coupling. More details on the algorithm and the results during a SRCL noise injection will follow.

For now, since the linear term is still dominant, I restrict the analysis to a linear and stationary coupling from SRCL_IN to CAL-DELTA_EXTERNAL. Using 600 seconds of quiet data (no noise injection) starting at GPS 1228461018, I can reconstruct the optimal transfer function from SRCL to DARM in order to cancel out all of the SRCL noise. The plot below shows the result, the blue traces are absolute values (y axis on the left) and the yellow traces are phase (y axis on the right). The dots show the coupling factors computed in the frequency domain using the direct approach described in 45403. The solid lines are the "parametric" couplings: in other words the algorithm tries to minimize a weighted band-limited RMS in a band between 20 and 400 Hz, by modeling the coupling as stable, realizable 10th order rational function. To be clear, it's not a fit to the frequency domain reconstruction, but rather a direct fit to the data cross spectral densities.

 

I can then convert the poles and zeros of this optimal coupling function to a IRR filter and perform a time domain subtraction. The result, shown below, confirms the level of SRCL noise in DARM predicted either by BruCO coherence 45785 or by Rana's injection 45792

 

The last attached plot shows the coherence between DARM and SRCL before and after the time domain subtraction.

For reference, here's the transfer function from LSC-SRCL_IN1 to CAL-DELTAL_EXTERNAL (all poles and zeros frequencies in Hz). Note that both signals have been normalized by subtracting the mean value [mean(SRCL) = 0.00159, mean(DELTAL) = -9.800e-9] and dividing by the standard deviation [std(SRCL) = 3.131, std(DELTAL) = 1.503e-5):

Z =    [  73.27096456+274.9515352j ,   73.27096456-274.9515352j ,
          -1.09403038+269.468058j  ,   -1.09403038-269.468058j  ,
        -166.83658568  +0.j        ,   -0.8012538 +162.2435469j ,
          -0.8012538 -162.2435469j ,   -7.08797763+133.8045331j ,
          -7.08797763-133.8045331j ,   -3.15622979+134.12022151j,
          -3.15622979-134.12022151j,    0.9151632 +130.36107968j,
           0.9151632 -130.36107968j,   -1.42267922+119.98903183j,
          -1.42267922-119.98903183j,   -1.20138561 +97.64824832j,
          -1.20138561 -97.64824832j,   12.51635674 +30.96586879j,
          12.51635674 -30.96586879j,   27.66665614  +0.j        ]

P =    [  -2.14932791+268.49097597j,   -2.14932791-268.49097597j,
        -121.14272574+208.73233613j, -121.14272574-208.73233613j,
          -0.91968157+162.46027366j,   -0.91968157-162.46027366j,
         -51.9247949  +97.84796774j,  -51.9247949  -97.84796774j,
         -12.82120671+136.99086962j,  -12.82120671-136.99086962j,
          -0.96319905+136.92492285j,   -0.96319905-136.92492285j,
          -1.4837154 +128.24815143j,   -1.4837154 -128.24815143j,
          -0.60056718+120.09145053j,   -0.60056718-120.09145053j,
          -0.48652029 +97.30282541j,   -0.48652029 -97.30282541j,
         -15.69466233 +33.36645134j,  -15.69466233 -33.36645134j],

K = 3.079408216222647


 
Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 09:42, Monday 10 December 2018 (45809)

The SRCL projection in the noise budget was made when the SRCL FF was tuned for the correct DARM offset.  On saturday night the DARM offset was changed and the SRCL FF was only adjusted with the scalar gain, 45782 so it is not surprising that the coupling is worse than in the noise budget.  

H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 09:52, Monday 10 December 2018 (45810)
Top Off Chiller Water Levels
   Added 150ml water to the crystal chiller. Water level in the diode chiller was OK. Both filters are clean and clear. No other issues or concerns noted.  
H1 PSL
edmond.merilh@LIGO.ORG - posted 09:49, Monday 10 December 2018 (45808)
PSL Weekly Report - 20 Day Trends FAMIS #10587

All plots look to be nominally ok. Chiller level steps coincide with Tuesday maintenance work.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 09:25, Monday 10 December 2018 (45807)
Monday Coordination Meeting Notes

Weekend Commissioning:  25 W work, looking at PI Modes (Seb & Terra)

Tues Maintenance Work Summary:  Stay in Laser Hazard & 4Hrs (i.e. end at noon)

Safety:  Be careful with icy conditions!

H1 SUS
jenne.driggers@LIGO.ORG - posted 08:13, Monday 10 December 2018 (45800)
Ndscope for violin mode monitoring

Just so that other people are aware, I've made ndscope templates for the violin mode drive and monitors.  They're accessible from both my locking screen and the normal violin mode overview screen.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 08:11, Monday 10 December 2018 (45799)
Morning Status

TITLE: 12/10 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.37 μm/s

Light snow outside on ground from last night, but no issue driving/walking around parking lot (a little foggy on Rt 10).
QUICK SUMMARY:

H1 ISC
daniel.brown@LIGO.ORG - posted 03:31, Monday 10 December 2018 - last comment - 09:18, Monday 10 December 2018(45795)
Locking today

Craig, Terra, Dan

Here's some observations from today on issues with locking, overall the alignment doesn't seem great and I'm not sure what we're doing wrong:

We ran initial alignment several times today. However, during MICH dark align the WFS seem to be taking us to something other than the symmetric elephant shape we usually have. We checked the phasing of AS45_B today and it all seemed fine. We touched up BS in either PRMI or check mich fringes if it wouldn't even lock that. Seems suspicious.

DRMI has been taking a long time to lock, PRMI seems fine, flashes look good.

Doing initial alignment of the arms has also been troublesome, getting good flashes in green has been more difficult than before, Y-arm has been particularly temperamental.

Getting through ENGAGE_REFL_POP_WFS was bit of a rollercoaster each time, PRC1 and PRC2 made some large detours.

We managed to get up to nominal low noise once for a few hour lock. The final lock didn't look very good though, there was a steady 0.6Hz oscillation in the PRG/RF18/arm powers that wouldn't die down, although it was stable overzealous commissioning brought it down.

We're trying to get it locked so Terra can do some PI work, however it's not looking likely at the moment.

Images attached to this report
Comments related to this report
craig.cahillane@LIGO.ORG - 03:11, Monday 10 December 2018 (45796)
I upped the upper thresholds on MICH and SRCL DRMI locking from 37 to 60, since our trigger POPAIR B RF18 I is around 140 cts when locked.  This seemed to moderately help with the last two DRMI locks (2 mins, 8 mins).
thomas.vo@LIGO.ORG - 08:42, Monday 10 December 2018 (45804)

The increased contrast defect from the TCS pre-loading might have changed the offset on the MICH DARK wfs loop, so Mich alignment probably should be adjusted by hand until it's fixed.

sheila.dwyer@LIGO.ORG - 09:18, Monday 10 December 2018 (45806)

We also have MICH_BRIGHT_ALIGN, which uses a dither alignment. 

H1 ISC (ISC)
rana.adhikari@LIGO.ORG - posted 23:37, Sunday 09 December 2018 - last comment - 18:45, Monday 10 December 2018(45792)
SRCL Noise coupling again

I was skeptical about the SRCL noise in the noise budget, so I checked it again. I think it is pretty close.

Its a simple method, but should be accurate. SRCL_FF left on in the Guardian set state in NLN.

  1. Turn on broadband noise excitation in SRCL2_EXC with AwgGui.
  2. Adjust calibration of SRCL_OUT in DTT until the SRCL_OUT trace matches DARM.
  3. turn off excitation to see how the ambient SRCL compares to DARM.

From this exercise I get the attached plot. Looks like its very close in the 40-90 Hz band. Options:

  1. better low pass filtering; Downside: this is hard and will make the loop more unstable.
  2. lower the SRCL gain: could be fine, but we don't yet know what the allowed SRCL error signal fluctuations are. i.e., how much can the SRC length fluctuate before it goes nonlinear or ruins the WFS signals?
  3. improve the sensing noise: more power, more modulation depth, less electronics noise. Do we have a SRCL noise budget?
Non-image files attached to this report
Comments related to this report
peter.fritschel@LIGO.ORG - 06:50, Monday 10 December 2018 (45797)

Why does this look so different than the SRCL contribution in the noise budget in entry 45169 , which was made just after the SRCL and MICH feed-forward was improved? In that NB the SRCL noise goes below 1e-21 strain/rtHz just above 70 Hz, while in this one that doesn't happen until 300 Hz. Has something in SRCL changed (loop gain, filters?) or is the Nov 9 NB thought to be in error?

 

gabriele.vajente@LIGO.ORG - 07:27, Monday 10 December 2018 (45798)

This is consistent with the BruCo projection based on coherence between DARM and SRCL. See https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=45782

And also consistent with the level of cancelation you can get by linear noise subtraction ( will post more later on this)

sheila.dwyer@LIGO.ORG - 09:00, Monday 10 December 2018 (45805)

On Saturday night the DARM offset was changed and the SRCL FF wasn't re-tuned, so you would not expect this to match the noise budget.  I don't know if these changes were in place last night.

craig.cahillane@LIGO.ORG - 15:13, Monday 10 December 2018 (45819)
The DARM offset during this measurement was 18.3 cts (~12 pm), giving 20 mA (23.8 mW) of power on the OMC DCPD SUM channel.  
Guardian is the one who controls the DARM offset during the INCREASE_POWER and ADJUST_POWER state, so it always sets it to whatever gives 20 mA on the DCPDs.
It's possible the SRCLFF needs to be retuned after the vent.  However, I doubt it will improve the SRCL to DARM by more than a factor of 2 or so (i.e. our current SRCLFF is decent).
Images attached to this comment
sheila.dwyer@LIGO.ORG - 18:45, Monday 10 December 2018 (45828)

Here is a noise budget where only the SRCL noise is updated, taken today.  (With 20mA DCPD sum at 20 W input power). The SRCL FF hasn't been returned since the TCS changes, that seems to explain the larger coupling. 

Images attached to this comment
H1 ISC
sheila.dwyer@LIGO.ORG - posted 20:46, Sunday 09 December 2018 - last comment - 00:55, Monday 10 December 2018(45791)
phasing of REFL air

Sheila, Dan Brown, Rana

Because DRMI acquisition has been slow, we looked at the phasing of REFLAIR which is what we use to acquire DRMI. 

By injecting a 132 Hz line in PRM with notches on in MICH and SRCL, we measured that in DRMI the phase of REFLAIR 45 should be 112 degrees to minimize PRCL in the Q phase (currently 97), and for REFLAIR 9 the phase should be 8 degrees to minimize PRCL in the Q phase (currently -23 degrees).  

We reverted these changes since we lost lock and had trouble reacquiring with the new phases.  We didn't get a chance to measure the POP9I to SRCL element, but that would be the next step if we want to try to use these phases for DRMI acquisition.   

Comments related to this report
rana.adhikari@LIGO.ORG - 00:37, Monday 10 December 2018 (45793)

Afterwards, we checked out the 1f in-vac diodes. We drove PRM and phased REFL & POP and minimized the Q phase signal via DTT ASD. The big change in REFL45 is because we wanted to change the sign to match the SRCL -> POP sign.

In most cases, this worked as expected. However, we were not able to get anything smaller than a ratio of 1:3 for REFL45. Seems like something is wrong with this chain. Maybe some strange optical effect or (more likely) a malfunction in the whitening gain or whitening filter. Since we don't use REFL45 for anything at the moment, it may not have been obvious before.

Name Dec 07 2018 04:48:21 UTC Dec 10 2018 08:28:01 UTC
Value Alarm Status Alarm Severity Value Alarm Status Alarm Severity
H1:LSC-POP_A_RF45_PHASE_R -4.9 NO_ALARM NO_ALARM 12.1 NO_ALARM NO_ALARM
H1:LSC-POP_A_RF9_PHASE_R -20.5 NO_ALARM NO_ALARM -8.5 NO_ALARM NO_ALARM
H1:LSC-REFL_A_RF45_PHASE_R -64 NO_ALARM NO_ALARM 130 NO_ALARM NO_ALARM
H1:LSC-REFL_A_RF9_PHASE_R 0 NO_ALARM NO_ALARM -3 NO_ALARM NO_ALARM

The table above is what CONLOG gives us when we ask for the Diffs.

do not be alarmed by the lack of Alarms

rana.adhikari@LIGO.ORG - 00:55, Monday 10 December 2018 (45794)

DanB, Craig, Rana

also, we started to investigate switching SRCL & MICH from POP to REFL in case that might reduce the REFL saturations; since REFL9 & REFL45 come from the same photodetector it may be a good idea to have the SRCL & MICH loops suppress the 45 MHz outputs. Perhaps closing the 45 MHz LSC loops will reduce some of the excess noise in the ASC loops.

Looks feasible in practice, but not sure it it makes sense in principle. I wonder if anyone has thought about or even tried this switchover before?

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 19:32, Sunday 09 December 2018 (45789)
seeding on CLF measurement

Terry and I quickly set up a 1811 on the CLF beam to check for seeding, and we see that our level of 3MHz sidebands on the CLF (which will be at the interferomter carrier frequency) is similar to what was seen at LLO 37945

Details:

We put the 1811 (AC coupled version) in place of the CLF rejected diode.  We used the half wave plate in front of the PBS to reduce the power here.  Once the diode was in we set the waveplate so that we saw 495 +/- 5mV of DC output (transimpedance 10V/mA) and measured the RF (+/- 1dBm for all):

-75dBm at 3.127 MHz
-75dBm at 200 MHz
-75.8 dBm 203.128 MHz  

Comparing this to LLO, we are getting 4 times more DC power, and about 6dBm more 3MHz signal, so that means that relative to the carrier our seeding power level is similar to LLO.  We haven't moved the RF amplifiers, feedthroughs, or attentuators as was done at LLO, which is consistent with the LLO results.  

While we were doing this measurement, I must have bumped the PBS in the CLF path which is very loose in it's mount, misalinging the fiber input  Terry tightened the mount, and we were able to find the beam in reflection off the OPO by carefully adjusting the PBS mount.  Then we used the two steering mirrors in front of the fiber coupler to maximize the transmission.  We found while doing this that the CLF launch diode was misaligned, and it looks like this has been misaligned for more than 20 days.  The beam is now aligned onto the diode.  Terry measured 4mW going towards the fiber, and the fiber launch diode reports 3.75mW towards the fiber.  The CLF Trigger diode reports 1 mW coming out of the chamber.  

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 23:30, Friday 07 December 2018 - last comment - 16:45, Monday 10 December 2018(45767)
squeezer injected into interferometer

Summary:

We were able to lock the squeezing angle using the 3MHz signal from the OMC DCPD's, and we have caused a few lockloses.  We have found that our locking scheme is introducing a lot of noise, so our next step is to lock the OPO length to the laser frequency.  

Locklosses:

In our first attempt we used the interferometer locked at 2W DC readout to look for the LO error signal.  We caused a lockloss then, and so we then changed to working with the interferometer locked on RF and the OMC locked.  We caused a couple of other locklosses this afternoon, one when the interferometer was locked on RF and the OPO became unlocked with the beam diverter open.  After this we added closing the beam diverter to the OPO guardian DOWN state, and the state CHECK_EOM (which we enter when the TTFSS EOM is railed).  

After successfully locking the squeezer angle, we transitioned to DC readout.  When we attempted to close the beam diverter we lost lock, which we also don't understand.  

We have been injecting ~10uW of CLF (measured on SQZT6), which gives us about 10 dBm of RF on the 3MHz demod.  We are wondering if this is too much and might be part of our lockloss problems.  We tried reducing it by a factor of 2.  

Locking:

Nutsinee will post details of the squeezing angle lock configuration that we used tonight, even though we don't plan to keep using this scheme. 

The basic steps:

Uncontrolled squeezing:

Images attached to this report
Non-image files attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 11:39, Saturday 08 December 2018 (45772)

I am not sure what the free-running plot represents. In this case, the 2 lasers differ in frequency by as much as tens of kHz. This would completely invalidate the correlations that are responsible for squeezing. Every now and then the frequencies will cross and one might catch a short glimpse of (anti) squeezing.

The first plot is somewhat of a mystery too. If we really suffer from excess phase noise (as we have measured), why doesn't it effect squeezing at all frequencies? Could it be seeding through the CLF instead?

lisa.barsotti@LIGO.ORG - 14:26, Saturday 08 December 2018 (45776)

For reference, at LLO the nominal CLF power (measured on SQZT6) was 50 uW, tests up to 200 uW didn't show a large amount of seeding ( LLO log 41270). So, in principle 10 uW should be well below the seeding threshold.

On the other hand, some "seed hunting" on the double AOM path on ISCT6 was done before injection in the intererferometer, see for example: LLO log 37945 . I don't recall if you have done a similar characterization at LHO.

sheila.dwyer@LIGO.ORG - 11:20, Sunday 09 December 2018 (45784)

Lisa- no we haven't done any seed hunting here.  

Daniel- I agree that it isn't clear what is happening without the CLF injected, especially since the level of anti squeezing is way too high. 

daniel.sigg@LIGO.ORG - 20:40, Sunday 09 December 2018 (45790)

The 10µW is measured transmitted by the OPO, I believe the 50-200µW at L1 are incident to the OPO. The CLF LO signal is fairly high with ~6 dBm (in the quad phase) when we are locked.

lisa.barsotti@LIGO.ORG - 16:45, Monday 10 December 2018 (45826)

So, about the CLF power: all of the numbers reported in the LLO log so far quote the CLF power as measured on the CLF REFL diode, so BEFORE entering the OPO. The OPO has a 4% transmission for the 3 MHz - so indeed the 10 uW quoted for this LHO attempt, measured AFTER the OPO, are 5 times higher than the 50 uW used at LLO, since 50 uW * 0.04 = 2 uW of CLF AFTER the OPO. So, as we all discussed today, the first test would be to lower this power and see if the extra noise is caused by that.

H1 CDS
patrick.thomas@LIGO.ORG - posted 14:19, Tuesday 27 November 2018 - last comment - 19:17, Sunday 09 December 2018(45534)
'Terminator' terminal emulator bug and work around
I believe I have found a relevant bug report and a work around for various issues using the 'Terminator' terminal emulator program, including:

1. New terminals were placed behind existing terminals.
2. Opening a new terminal on a workspace that did not already have a terminal open on it would move an already existing terminal from another workspace to the workspace that the new terminal was opened on.

The bug report is here: https://bugs.launchpad.net/terminator/+bug/1508531

The work around is mentioned in one of the comments. Edit your ~/.config/terminator/config file and add 'dbus=False' under [global_config]. For example:

[global_config]
	dbus=False
[keybindings]
[profiles]
  [[default]]
    scrollback_infinite = True
[layouts]
  [[default]]
    [[[child1]]]
      type = Terminal
      parent = window0
    [[[window0]]]
      type = Window
      parent = ""
[plugins]


This seems to have resolved the issues mentioned above for me.
Comments related to this report
sheila.dwyer@LIGO.ORG - 11:00, Thursday 29 November 2018 (45577)

Thanks Patrick, this is a great problem to solve.  Can we add this to everyone's profile by default?

rana.adhikari@LIGO.ORG - 19:17, Sunday 09 December 2018 (45788)

can also solve this by using the "Preferences" option in The Terminator:

  1. right-click on Terminator
  2. find "Preferences"
  3. un-select the DBus server check box
Displaying reports 44081-44100 of 88549.Go to page Start 2201 2202 2203 2204 2205 2206 2207 2208 2209 End