Displaying reports 44961-44980 of 88435.Go to page Start 2245 2246 2247 2248 2249 2250 2251 2252 2253 End
Reports until 09:56, Wednesday 24 October 2018
H1 ISC
jenne.driggers@LIGO.ORG - posted 09:56, Wednesday 24 October 2018 - last comment - 11:07, Thursday 25 October 2018(44781)
Reduced 9MHz modulation depth

I reduced the 9MHz modulation depth by 6dB, and it seems like that gives us several more Mpc. It seems like our sensitivity is really improving when I reduce the modulation depth, although I'm not sure why it has such a significant effect, particularly at high frequencies.  I plot here also 3 of the calibration lines, so you can see that their peaks are lining up pretty well.  If anything, the green and brown traces with the 9MHz at it's lock acquisition value are a bit worse than they look here, since the 1080Hz line should be scaled up by a teeny bit.

Note that the lockloss around 16:45 was me, trying to reduce the 9MHz by another 3dB, but the old script that I use to step by hand further didn't include compensation for the analog CARM gain.  I've fixed the script, so will likely try again next lock.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:43, Wednesday 24 October 2018 (44786)

I have now put the 9MHz reduction into the main acquisition sequence path.

The attached plot shows that we are really seeing more power circulating in the arm cavities (and also less power at the AS port) when the 9MHz modulation depth is reduced.  So, there must be some offset somewhere that we're reducing. 

Also, I tried reducing the modulation depth by 8dB rather than just 6dB, and the IFO gets noticeably more glitchy when I do the extra 2dB.  So, it seems like 6dB of reduction is a reasonable place, and we can work on finding what is causing this circulating power change.

Since we're reducing the 9MHz modulation depth from 0.2ish to 0.1, we're changing the 9MHz power from 4% to 1%, so should have ~3% more carrier power.  That is consistent with the increase in circulating power that we see.  However, the apparent shot noise reduction implies a much larger increase in power, so something is still not quite hanging together.

Images attached to this comment
peter.fritschel@LIGO.ORG - 13:04, Wednesday 24 October 2018 (44787)

It would be worth checking the RF levels on the other LSC RFPDs used for LSC control (if you haven't already), as was done yesterday for REFL9.

keita.kawabe@LIGO.ORG - 15:52, Wednesday 24 October 2018 (44793)

Premature to say we're gaining something, as I don't see the same reduction in uncalibrated DARM nor in OMC DCPD.

In the first attachment , red, blue and brown are from the single lock stretch corresponding to Jenne's red, blue and brown. No improvement at 1kHz at all, and the frequency noise part (f>2k or so) is worse when 9MHz was reduced. In Jenne's plot the improvement was pretty much 15 % or so over the large frequency region.

The second attachment is later in the morning. Blue is small RF9, green is large RF9.

In the latter there seem to be a difference at 100Hz but I don't know if this was due to high/low RF9 mod index.

Optical gain difference between high/low RF9 was no larger than a few % in both of the lock stretches.

 

Images attached to this comment
keita.kawabe@LIGO.ORG - 16:55, Wednesday 24 October 2018 (44796)

Update (Jenne, Keita): Things makes more sense now.

In the attached, you should compare red (reduced RF9) with brown (not reduced) from the same lock stretch, or blue (not reduced) with pink (reduced) from another lock stretch. Legends are in UTC. In both of the cases, smaller modulation index increases the frequency noise in high kHz but seems to somewhat reduce noise at 100Hz.

It didn't make sense at first because there was an error in the legend of Jenne's plot.


Details:

Turns out that the legend for the brown trace (15:59:07, 9MHz back to normal) in Jenne's plot was incorrect, it was neither UTC nor local time, it was actually from 09:53:02 UTC, i.e yesterday. This means that all of her "9MHz reduced" traces are from today and all of "9MHz normal" traces are from yesterday.

But she intended to look at 15:59:07 UTC for brown trace, which was from today when 9MHz was reduced (but the CM gain setting was not changed to compensate). In the attached, red and brown are the same as Jenne's red and what Jenne intended to show in brown, these are from the same lock stretch.

Blue and pink are from another lock stretch later in the morning. (In this case, CM gain setting was changed to compensate for the optical gain.)

Low RF makes frequency noise worse at high-kHz due to lower S/N (pink VS blue). In the case of red VS brown, overall CM gain was lower, making the difference larger than pink VS blue.

To confuse the matter further, somehow at some point in yesterday the shot noise level seemed to have improved according to  Sheila, and that is clearly seen in green trace from yesterday.

Images attached to this comment
jenne.driggers@LIGO.ORG - 17:19, Wednesday 24 October 2018 (44799)

There is at least a bit of a change in the range during the on/off test that I meant to plot the times of from this morning.  See attached.

I've modified EvanH's old stepping modulation depth script so that it will change the modulation depth, wait 10 min, then change it back, repeating 5 times.  If the IFO is locked when the last person leaves for the night, please launch this (attached, and in /ligo/home/jenne.driggers/LHO_work/2018_10_24_9MHz_reduction/step_9MHz_many.py)

Images attached to this comment
Non-image files attached to this comment
craig.cahillane@LIGO.ORG - 02:53, Thursday 25 October 2018 (44812)ISC
I modified Jenne's modification of step9.py so that the user can CTRL+C the skip at any point and the PD gains will all be returned to their original values when the script starting running.  Useful for when we lose lock during the test.  

Pressing Ctrl+C while the gains are changed and the interferometer is locked is not recommended: the script will instantaneously return all gains to original values.

Code lives in:
/ligo/home/craig.cahillane/utils/step9mod.py

Started a run of this code at Oct 25 2018 09:52:44 UTC (1224496382).
keita.kawabe@LIGO.ORG - 11:07, Thursday 25 October 2018 (44826)

Yet another update:

For the moment I take back my statement about lower modulation index VS high kHz frequency noise, the coupling itself is slowly changing with time and I might have been tricked.

H1 AOS (ISC)
hang.yu@LIGO.ORG - posted 09:54, Wednesday 24 October 2018 (44780)
Nonlinear SRCL noise coupling -- significant from 30 to 80 Hz

Rana, Hang

We retook the nonlinear SRCL noise coupling measurement. In our previous study without SRCLFF (LHO:44770), the linear component was too high to expose the nonlinear part. This time we inject SRCL noise with both the MICH and SRCL FF on to reduce the linear component (thanks Sheila et al. for performing the injection; LHO:44772) and, as a result, now we are able to expose the NL couplings.

Please see the first attached plot for the SRCL noise projection. The blue trace is the DARM ASD, the orange is the projection of SRCL based on excess power (which captures both the linear and NL coupling), and the green one is the SRCL projection based on pure linear coherence (i.e., the residual linear coupling after the online FF).

It seems that the SRCL noise is the dominant noise source in the 20-40 Hz band, and is significant all the way up to ~ 300 Hz. Below 30 Hz, the SRCL coupling is still mostly linear from the FF residual, whereas in the 30-80 Hz band the nonlinear coupling dominates.

The ratio between the NL/L PSDs projected onto DARM is shown in the second plot. In the 30-80 Hz band, the NL coupling is typically a few to 10 times higher than the residual linear component in power.

===================================================================================

The data we used for generating the plots started from gps 1224400998 for 1024 sec. The excess power projection also used data from gps 1224399618 for 1024 sec with active SRCL noise injection (both MICH and SRCL FF on).

Images attached to this report
H1 PSL (DetChar, ISC, PSL)
gabriele.vajente@LIGO.ORG - posted 09:50, Wednesday 24 October 2018 - last comment - 10:16, Wednesday 24 October 2018(44779)
Intensity noise?

[Jenne, Gabriele]

We might be limited by intensity noise that we can't sense with the ISS first loop diodes. Now that we got your attention, see the details below. The most interesting plot is the last one.

This morning we checked whether the ISS second loop was open. The output switch of the second loop board (H1:PSL-ISS_SECONDLOOP_OUTPUT_SWITCH_MON) was indeed open, but the input switch on the first loop board was closed (H1:PSL-ISS_SECONDLOOP_CLOSED). So we decided to open it.

We were surprised to see that the sensitivity got significantly worse when the switch was open. See below (H1:PSL-ISS_SECONDLOOP_CLOSED = 1 means switch closed, first loop closed but second loop still open at the output of the second loop board, H1:PSL-ISS_SECONDLOOP_CLOSED = 0 means switch open at the input of the first loop board, but the first loop is still closed)

 

At the same time we see that the first loop signals (PDA is out-of-loop and PDB is in-loop) also changed. The in-loop signal did not show any difference, while the out-of-loop signal noise floor increased by about a factor of ten. See below (top panel is again DARM, bottom panel is the in-loop signal (dashed) and the out-of-loop signal (solid).

 

So it looks like the noise in DARM increased at almost all frequencies by about the same factor as the noise seen by the ISS first loop (out-of-loop) PDA sensor.

However, coherence is very poor between DARM and PDA/PDB, even when the noise is high.

 

It's however clear that the noise increase in DARM is related to toggling the ISS input switch (we tried many times).

Spectrograms of DARM and PDA (out-of-loop signal) in the quiet and noisy periods show that the noise is highly non stationary, so maybe this is enough to explain the lack of coherence.

 

So the next question is how close is the intensity noise (as measured by the ISS first loop out-of-loop signal) to limiting us in normal condition?

To answer, we computed the ratio of the DARM spectrum over the PDA spectrum while in the noisy state, and use this ratio to project the quiet state PDA spectrum into DARM. We restricted the projection to only those points where the DARM noise got higher by more than a factor of two when in the noisy state. The result, shown below, seems to indicate that we are likely limited by "intensity" noise measured by the ISS first loop sensor, which couples in a non-stationary or non-linear way, so we don't see coherence.

 

Next steps:

Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 10:16, Wednesday 24 October 2018 (44782)

More information:

  • when the ISS second loop switch is open (noisy state), we see a clear increase of intensity noise in the ISS second loop signal, which is coherent with DARM
  • there is also an increase of "frequency noise", at least as seen by REFL SERVO signals.

 

Images attached to this comment
H1 ISC
gabriele.vajente@LIGO.ORG - posted 07:39, Wednesday 24 October 2018 - last comment - 07:39, Wednesday 24 October 2018(44767)
Retuned feedforward, but...

In breif, I measured, fitted and retuned the MICH and SRCL feedforward. The results are good, but the first SRCL FF filter I tries showed the same instability reported in 44740, probably due to the "large" gain below 10 Hz that's neede to have a good fit down to 10 Hz. So I restricted the fit above 30 Hz, and got a new filter, which should have good performance in the 30 to 100 Hz region. I haven't tested it yet, since the IFO unlocked.

Measurement templates are attached, since I don't have permissions to copy them in /opt/rtcds/userapps/release/lsc/h1

The plot below shows the DARM spectrum without any feedforward (red), with MICH only (blue) and woth MICH+SRCL (black).

 

The configuration that gives the good MICH filter and the (tentative) good SRCL filter ois shown in the last attached screenshot.

Images attached to this report
Non-image files attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 18:28, Tuesday 23 October 2018 (44768)

For Hang:

SRCL noise   (MICHFF on, SRCLFF off) 1224376571 1224376692
SRCLFF noise (MICHFF on, SRCLFF off) 1224377188 1224377289
 

hang.yu@LIGO.ORG - 21:57, Tuesday 23 October 2018 (44770)ISC

Thanks Gabriele for the time stamps.

We used Gabriele's SRCL noise injection to study how much SRCL coupling is linear (which can be easily subtracted), and how much is nonlinear (due to non-stationary coupling, e.g.). The conclusion is that we do not see significant nonlinear coupling.

Please see the attached plot for the results.

We looked at two periods of data, one starting from gps 1224376598 (w/ SRCL injection) and one from gps 1224377643 (quiet). Each piece of data was 128 s long. We computed the SRCL to DARM projection based on both excess power projection (which captures NL effects) and linear coherence. Then we projected SRCL to DARM for the ''quiet'' time using the two coupling coefficients (orange for the excess power, green for the linear coherence). No significant difference could be seen, meaning that the NL component is sufficiently small.

Images attached to this comment
H1 CDS
jenne.driggers@LIGO.ORG - posted 06:17, Wednesday 24 October 2018 - last comment - 09:16, Wednesday 24 October 2018(44776)
h1seih23 and h1seih45 had dackill problems again

The h1seih23 and h1seih45 computers had their dackill glitches again.  This is what killed the several hour lock at 22W that was left overnight.  I requested the HAM 2,3,4,5 HEPI and ISI guardians to "ready", then ssh'ed to the computers and ran the startWorld script, as in alog 44672 and alog 44695.

Also, just in case some settings get missed, I took the SEI_CONF guardian to WINDY_NOBRSXY and then back to WINDY_NOBRSX, to force any sensor correction settings to be put back.  The SEI_CONF medm screen made it look like everything was in its expected state, and all of the lights (except end X due to BRSX issues) were green, but since this was a problem last week, hopefully this ensures all sensor correction is properly turned on.

Comments related to this report
jason.oberling@LIGO.ORG - 09:16, Wednesday 24 October 2018 (44778)

This is the third occurrence of this issue (first 2 were logged here and here); this is already covered by FRS 11680.

H1 ISC (ISC)
craig.cahillane@LIGO.ORG - posted 04:09, Wednesday 24 October 2018 (44775)
Calibrated CARM Spectrum
Rana, Craig

Today we calibrated the CARM servo board spectrum into Hz.

First, we drove a strong line in the MC2 suspensions at 71.1 Hz, and measured the transfer function from REFL_SERVO_ERR_OUT_DQ (we assume counts from the common mode servo board error signal) to IMC_F_OUT_DQ (calibrated into kHz).
We got 3.1e-7 kHz/cts, or 0.5 Hz/V, at 71.1 Hz, assuming an ADC of 2^16 cts / 40 V. 
Assuming a CARM pole of 0.5 Hz, this gives a CARM optical gain at DC = 284 V/Hz.

We've also measured the CARM OLG, giving a UGF of 10 kHz.  
By extrapolating the CARM OLG with a 1/f^2 line, we can approximately calibrate CARM into Hz of frequency noise incident on the interferometer:


where 
 is the CARM OLG, 
 is the common mode boost (z=4kHz,p=40Hz), 
 is the REFL9 sensing chain,
 is the CARM plant, and 
 is the common mode board test1 point.

The calibrated spectrum is pretty flat, quickly reaching an RMS of 2 Hz at high frequencies.  This RMS frequency noise seems too high to me, and the spectrum doesn't have the shape I expected.
Images attached to this report
Non-image files attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 00:04, Wednesday 24 October 2018 (44772)
calibrated DARM spectrum

Sheila, Georgia, Craig, Hang, Rana

We have a calibrated DARM spectrum that we can compare to the noise during O2, and it looks like our noise from 40-100 Hz is very similar to the noise floor after the Montana earthquake last July (ignore the large injection just above 70 Hz).  The first attached screenshot shows the noise before and after the earthquake and now for a comparison. The second screenshot shows the coherence of DARM with ASC and LSC signals, none of which are high above 35 Hz.  

Done tonight:

 

Images attached to this report
H1 ISC (ISC)
rana.adhikari@LIGO.ORG - posted 22:58, Tuesday 23 October 2018 - last comment - 07:06, Wednesday 24 October 2018(44771)
REFL9 RF level check

Craig, Rana

We checked the RF levels at the REFL9 demod board RF MON (-23 dB coupled output) with 50 Ohm terminated oscope.

So to convert this trace back into the input of the demod board we multiply by ~14.

From the scope trace, we can see that the fastest slew is ~140 mV / 10 ns (10 V/us). This is not a problem for the FET mixers on the board.

The slew rate limit of the RFPD output amp is 450 V/us, so we are from hitting the hard slew rate limit. The question that remains is how close can we be before there is some non-negligible downconversion.

Thinking back to the iLIGO days, we used to have trouble with the MAX4107 (450 V/us slew rate) when it was putting out ~150 mV-pk at 2*25 MHz (~30 V/us).

So I think if the LMH6642 distorts at the same fraction of slew rate as the 4107, we are close to seeing this excess noise. To be sure, we'll need to do a more careful and systematic test with some spare RFPD and demod electronics. Tricky.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 07:06, Wednesday 24 October 2018 (44777)

Something that we haven't done yet is the reduction of the 9MHz modulation depth by 6dB, once we're at high power.  We should see if this helps get us far enough away from these slew rate limits.

H1 SUS (ISC, SUS)
georgia.mansell@LIGO.ORG - posted 22:39, Tuesday 23 October 2018 (44769)
ETM charge measurements today

[Georgia, Patrick]

We ran the usual charge measurements today - the quadrant-by-quadrant effective bias voltage measurements on both ETMX and ETMY, and the additional measurements of combinations of the four parameters on ETMX (measured by driving combinations of the signal and bias electrodes).

The ETMY effective bias trend remains consistent with ~50 V offsets on the UL quadrant (coupling to pitch), the UR quadrant (coupling to yaw), and the LL quadrant (both pitch and yaw). The first attachment shows this over the last few months.

The ETMX effective bias is trending back towards zero after the bias was switched on September 11. The second screen shot shows the quadrant-by-quadrant measurement for ETMX.

This trend is also seen in the four-parameter measurement which makes sense. The third attachment shows the alpha and gamma parameters in the first column, these are associated with the ESD actuation strength and should not change over time. The second column is the beta+beta2 parameters, as measured by driving the bias and measuring the response on the op lev, and by driving the signal electrodes and measuring the response on the op lev. This measurement should be immune to space-charge polarisation which we assume is symmetric. The bias-driven beta+beta2 seems to have taken a jump recently (though I don't want to jump to conclusions based on two data points), while the longitudinal signal drive did not. This is strange. The third column shows beta-beta2 and the Veff, which are sensitive to space charge polarisation and consistent with the quadrant-by-quadrant measurements.

 

Note when running these measurements - it can be hard to tell if the HV is on or off. Even with the HV off a small signal is seen in the ESDAMON channels whin driving the quadrants. These channels are calibrated into volts and should see a large excitation from the charge measurements (100s of volts, exact numbers depend on the measurement). Up until today the ETMY L3 ESDAMON and LVESDAMON filters were turned off, leaving those channels in counts, not volts. I have switched those filters on now.

Images attached to this report
H1 CAL (DetChar, ISC)
jeffrey.kissel@LIGO.ORG - posted 17:31, Tuesday 23 October 2018 (44766)
H1CALCS Front-end Calibration (DELTAL_EXTERNAL) Updated, and Good-ish (Maximum Systematic Error between 20-800 Hz is 15%)
J. Kissel, S. Dwyer, E. Goetz, L. Sun

Lilli Shiela and I were able to successfully update the calibration of DELTAL_EXTERNAL today. The residual systematic error is no worse that 15 % and 7 degrees (likely due to a slightly wrong coupled cavity pole, and slightly wrong actuator strengths, and slightly wrong sensing vs actuation relative delay). Recall that this calibration is informed by quick, limited frequency band, measurements, so I'm happy that the results are even this good.

The big gotcha that took us so long: the MEDM screens (recently upgraded by Jeff) do not correctly reflect what's happening in the front-end in each actuator replica's ESD path. Namely, with the replica ESD linearization bypassed, the replica BIAS bank has no influence on the ESD path (this was not Jeff's impression of how it should be, thus he didn't update the MEDM screen that way). Thus, when we had installed the correct replica bias -- and it just happened to be negative -- it did not affect the replica signal path. Thus -- unless we change the model in the future to be more reflective of real life -- we need to apply the bias voltage *sign* and only the sign somewhere in the replica control path. Combined with several other sign flips between the O2 configuration of interferometer control and the current interferometer control (a different arm, a different output matrix, a different bias sign), this was very difficult to find (which is why we needed Sheila's new set of eyes to help figure out the problem).

I've accepted all of the settings in the CAL-CS model as they stand now, so we should have this good(ish) calibration permanently.

I've confirmed the updated calibration and it's systematic error with a PCAL to DARM sweep and an DARM Open Loop Gain, which can be found here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
    2018-10-23_H1DARM_OLGTF_23to800Hz_10min.xml
    2018-10-23_H1_PCAL2DARM_TF_23to800Hz_2min.xml
they've been exported for future processing by Evan and Lilli. These measurements and their exports have been committed to the above location in the repo.

The attached 2 screenshots show two things:
 - The PCAL to DELTAL_EXTERNAL transfer function (left two panels of first attachment), which quantifies the residual systematic error in the calibration
 - A calibrated (to the accuracy quantified above) amplitude spectral density of DELTAL EXTERNAL.

There are plenty of qualifiers on the noise of this ASD -- it's in the middle of tonight's round of commissioning. The biggest know problem is that they're actively working on tuning the LSC feed-forward, so there is no MICH, PRCL or SRCL feed-forward on during this ASD. Please focus on the fact that the PCAL lines (in green X's) at 35 and 330 Hz are matching the LIVE DELTAL_EXTERNAL (in red).
Images attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 16:27, Tuesday 23 October 2018 (44765)
Replaced BSC10's annulus ion pump

I determined that something was amis after having replaced BSC10's AIP pump body this morning and, so, swapped the controller out as well.  Something still isn't working - I don't believe the pump current data even though the absolute value is plausible.  I'll continue to investigate at the next opportunity.  Until then, I am leaving the AIP energized but have shut down the pump cart and local turbo.   

H1 SQZ
daniel.sigg@LIGO.ORG - posted 16:25, Tuesday 23 October 2018 (44764)
Adding filters to DCPDs

Terry Daniel

Added a Thorlabs FLH1064-8, a FLH532-4 and a FLH532-4 in front of the DCPDs which monitor the IR laser light, the SHG green light and the green light launched into the fiber, respectively. This blocks the ambient light and makes us insensitive to the table lights.

H1 ISC (ISC)
hang.yu@LIGO.ORG - posted 12:15, Tuesday 23 October 2018 - last comment - 10:50, Wednesday 24 October 2018(44746)
DARM noise after subtracting linear coherence with aux dofs

We tried to do some DARM noise budgeting based on its coherence with the auxiliary degree of freedoms. The data we use for this analysis are starting from GPS 1224301218 and for a duration of 1024 sec. The auxiliary loops we consider so far includes LSC MICH/SRCL/PRCL/MCL, ASC CH/CS/DH/DS P/Y, as well as the ones we used for jitter noise subtraction during O2 (PSL-DIAG_BULLSEYE_PIT/YAW & IMC-WFS_A/B_DC_PIT/YAW). We only focused on the freq range from 10-100 Hz as this should be the band where the auxiliary DOFs' coupling being most significant.

In the first attached plot, the blue trace is the raw DARM output, the orange trace is the one after we removed all the linear coherence with the aux loops we considered (computed based on the f-domain MISO coherence; the subtraction is also done in the f-domain, i.e., the subtraction is assumed to be ideal), and the green trace is an O2 H1 reference before the Montana earthquake. There exists some calibration uncertainties and we simply scaled the current and O2 DARM to match at 100 Hz. Nonetheless, it suggests that we have some excess noise below 60 Hz compared to the O2 ref, and those noise cannot be solved by tuning LSC FF nor A2L.

In the second plot we show the noise projections from the LSC auxiliary loops, in the third plot the projection based on the ASC loops, and the last plot the projection based on the jitter channels.

For the LSC, coupling right now is dominated by SRCL (and its slope is much sharper than 1/f^2 as I would naively expect due to DARM detuning...).

For the ASC, we have large DS_P coupling because we are trying to suppress the 0.5 Hz oscillation. However, as we have SRC ASC controlled it seems unnecessary to have such a high BW DS_P loop. The noise above 20 Hz is then dominated by CH_Y and DH_Y. For DH_Y we have some margin and should be able to improve the LP relatively easily. For CH_Y, however, as we kept losing phase for that loop at ~ 3 Hz the optimization might be challenging... Need to think more carefully how to handle it.

For the jitter noise, we do not see significant couplings to DARM.

===============================================================

In principle the all the linear coherence can be subtracted out and should not contaminate DARM. Ideally the subtraction should happen online, but in the worst case we can still remove them from offline regressions (as we did for this study). Thus those noise should be the easy ones to tackle.

The subtraction residuals, if not explained by the coherence with aux dofs we haven't considered so far, are probably from nonlinear couplings and would be harder to remove. That would be the hard part of the commissioning work. From the current study, we do see excess noises in the <60 Hz region that cannot be explained by the linear couplings between the major LSC/ASC loops and DARM, and thus we might need to start thinking about the origins and solutions to those noises.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 12:52, Tuesday 23 October 2018 (44753)

There is a small amount of coherence with the jitter channels above 200Hz, but it's pretty small relative to what we used to see.  Interestingly, there are some sharp lines of coherence with the bullseye width channel above 800 Hz.

The IMC WFS and the bullseye are only saved to 2kHz, so we should re-look at these coherences online next time we're at NomLowNoise to check if there are any surprises at higher frequencies.

EDIT: Jason noticed today that the bullseye is not well aligned, so we should revisit the coherences with the bullseye after he aligns it (likely during next Tuesday's maintenance).

Images attached to this comment
thomas.vo@LIGO.ORG - 10:50, Wednesday 24 October 2018 (44784)

Attached is a higher frequency coherence between IMC_WFS and DARM up to 7 khz, doesn't look like interesting at higher frequencies than what Jenne had posted about earlier.  The bullseye sensor is doesn't sample past 2khz so it's not included.

Images attached to this comment
H1 ISC
sheila.dwyer@LIGO.ORG - posted 23:14, Monday 22 October 2018 - last comment - 23:12, Tuesday 23 October 2018(44740)
SRC ASC, LSC feedforward

Sheila, Hang, Craig, Georgia, Danny, Thomas

Comments related to this report
craig.cahillane@LIGO.ORG - 23:35, Monday 22 October 2018 (44744)ISC
The new SRCL FF is implemented in FM4 of SRCLFF1, named "Oct22".  It corresponds to the dashed green line in the plot below.

Sheila created two dtt templates in /opt/rtcds/userapps/release/lsc/h1/templates/ which make the DARM err/ SRCL out and DARM err/ SRCL FF measurements.  My notebook in /ligo/home/craig.cahillane/Git/Feedforward/SRCL2DARMfeedforward.ipynb reads in the latest results in those templates using dtt2hdf then fits them with iirrational.  Some tweaking of the fit was required.  Thanks to Hang for the useful pyctrl library for easy communication with iirrational and foton.

If you want to use this notebook, you first have to source my anaconda environment to get iirrational and dtt2hdf:
source /ligo/home/craig.cahillane/bashScripts/activateAnaconda.sh
jupyter notebook /ligo/home/craig.cahillane/Git/Feedforward/SRCL2DARMfeedforward.ipynb
Non-image files attached to this comment
craig.cahillane@LIGO.ORG - 02:08, Tuesday 23 October 2018 (44745)
The filter "Oct22", in conjunction with the "AC" filter already in the SRCLFF1 bank, was unstable. 

The AC filter was supposed to AC couple the SRCL feedforward.  It consisted of two zeros at 0 Hz and two res g poles with low Q at around 1.0 Hz.  I tried pushing the AC cutoff up to 10 Hz, but I still had an instability at 3.5 Hz.
This instability was caused by the Oct22 filter adding too much gain and phase to the loop, giving a phase crossover right at 3.5 Hz with gain > 1.  (pic 1)

So I created the "Oct23" filter and a new "AC" filter by hand.  It's not the best fit in the world, but it's not unstable.

EDIT: I enabled SRCLFF1 in the LOWNOISE_LENGTH_CONTROL guardian.  The filter module gain should be 1.0, not -1.0, for "Oct23".  Changed in lscparams.
Images attached to this comment
Non-image files attached to this comment
gabriele.vajente@LIGO.ORG - 12:08, Tuesday 23 October 2018 (44751)

It looks like when we are in NLN, the L3 ISCINF input to the ITMs (coming from the LSC feedforward) is the same, but the actual control signal sent to the L2 actuators is different in ITMX and ITMY. This might explain part of the instability issue: the SRCL feedforward is supposed to be a purely differential drive, and tus orthogonal to SRCL. But the ITM driving unbalance can cause a common drive, which feeds back to SRCL.

It seems that the difference in L2 driving in the two ITMs is a residual mistake from the ESD low noise transition. We'll fix it and measure again the feedforward paths.

 

Images attached to this comment
sheila.dwyer@LIGO.ORG - 23:12, Tuesday 23 October 2018 (44773)

The differences in filter states and gains that are residual from the ESD transition are only in L3, so shouldn't impact the feedforward.  I don't know why the drives to the 2 ITMs are different.  

H1 PSL
gabriele.vajente@LIGO.ORG - posted 11:37, Monday 22 October 2018 - last comment - 16:07, Tuesday 23 October 2018(44726)
Chnaged h1psliss model

Related to WP 7881, modified and recompiled the PSL ISS model, to change the name of a filter bank from PSL-ISS_SECONDLOOP_REFERENCE_DIFFRACTION_CAL to PSL-ISS_SECONDLOOP_REFERENCE_DFR_CAL

Modified accordingly the MEDM screen in /opt/rtcds/userapps/trunk/psl/common/medm/ISS/PSL_CUST_SECONDLOOP_SLOWOFFSET.adl

Comments related to this report
gabriele.vajente@LIGO.ORG - 16:07, Tuesday 23 October 2018 (44763)

After today's maintenance and restart of the ISS model, the second loop is no more working at powers above ~10 W. It's fine to engage the second loop at 2 W, and to increase the power to 10 W. Above that, the loop drives the diffracted power very high.

It's not clear if the problem is to be traced to some configuration parameter in the ISS model, or to the fact that the diffracted power is now larger (2.4% instead of 1.4%).

More dedicated time is needed to investigate the problem.

Displaying reports 44961-44980 of 88435.Go to page Start 2245 2246 2247 2248 2249 2250 2251 2252 2253 End