Displaying reports 45401-45420 of 88367.Go to page Start 2267 2268 2269 2270 2271 2272 2273 2274 2275 End
Reports until 15:31, Monday 01 October 2018
H1 PSL
yannick.lecoeuche@LIGO.ORG - posted 15:31, Monday 01 October 2018 (44260)
PSL Weekly

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

PMC:
It has been locked 1 days, 19 hr 33 minutes (should be days/weeks)
Reflected power = 17.05Watts
Transmitted power = 43.55Watts
PowerSum = 60.6Watts.

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

ISS:
The diffracted power is around 1.5%
Last saturation event was 1 days 19 hours and 33 minutes ago (should be days/weeks)
 

H1 CDS (DAQ, SQZ)
david.barker@LIGO.ORG - posted 15:19, Monday 01 October 2018 (44259)
h1sqz model change and DAQ restart

WP7845 h1sqz model change and DAQ restart.

Following a restart of the h1sqz model (remove 1 slow, 1 fast, add 1 fast channel to DAQ) the DAQ was restarted.

2018_10_01 13:45 h1sqz
2018_10_01 15:08 h1broadcast0
2018_10_01 15:08 h1dc0
2018_10_01 15:08 h1fw0
2018_10_01 15:08 h1fw2
2018_10_01 15:08 h1nds0
2018_10_01 15:08 h1nds1
2018_10_01 15:08 h1tw0
2018_10_01 15:08 h1tw1

H1 ISC
jenne.driggers@LIGO.ORG - posted 14:37, Monday 01 October 2018 (44251)
Monday AM locking
H1 SQZ (SQZ)
nutsinee.kijbunchoo@LIGO.ORG - posted 13:58, Monday 01 October 2018 - last comment - 11:42, Tuesday 02 October 2018(44257)
SQZ model changed

Sheila, Haocun, Terry, Nutsinee

We moved the PSL feed forward summing point so that it happens before the OPO frequency servo filter bank.

WP#7845

Comments related to this report
terry.mcrae@LIGO.ORG - 11:42, Tuesday 02 October 2018 (44295)

Model attached.

Non-image files attached to this comment
H1 SEI
yannick.lecoeuche@LIGO.ORG - posted 12:40, Monday 01 October 2018 (44256)
SEI seismometer mass position check

All T240 proof masses within range, 1 STS proof mass out of range. Relevant script output:

All T240s proof masses that within healthy range (< 0.3 [V]). Great!

 

There are 1 STS proof masses out of range ( > 2.0 [V] )!
STS A DOF X/U = -8.06 [V]
All other proof masses are within range ( < 2.0 [V] )

H1 PSL
edmond.merilh@LIGO.ORG - posted 10:56, Monday 01 October 2018 (44255)
PSL Weekly Report - 10 Day Trends FAMIS #10577

It appears we are "steady as she goes".

Images attached to this report
H1 AOS (AOS, SUS)
yannick.lecoeuche@LIGO.ORG - posted 10:29, Monday 01 October 2018 - last comment - 14:53, Monday 01 October 2018(44254)
Optical Lever 7 Day Trends

PR3 YAW displaced by about 20 urad, ETMY YAW approaching 10 urads.

This closes FAMIS 11185

Images attached to this report
Comments related to this report
edmond.merilh@LIGO.ORG - 14:53, Monday 01 October 2018 (44258)

PR3 OpLev was recentered this morning. The others will be re-centered on a TOO basis.

Images attached to this comment
H1 General
yannick.lecoeuche@LIGO.ORG - posted 10:16, Monday 01 October 2018 (44253)
Morning Meeting Minutes

-PR3 Oplev alignment

-Tuesday Maintenance Work (Laser Safe 8-10 am):

 

H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 08:32, Monday 01 October 2018 (44252)
Monthly PSL Chiller Filter Check (FAMIS #8313)
   Checked both filters and chillers. 

   All is in order. Both filters are clean and clear, except as noted in previous reports there is yellowing in the crystal chiller filter due to plumbing work on the crystal chiller circuit. No debris was noted in either filter canister.  

   Did not any cooling water to either chiller. 

Closing FAMIS ticket #8313. 
H1 ISC
gabriele.vajente@LIGO.ORG - posted 18:25, Sunday 30 September 2018 (44250)
PRCL offset

It looks like the optimal buildup happens for a PRCL offset slightly away from zero, i.e. -100

 

Images attached to this report
H1 SQZ (SQZ)
nutsinee.kijbunchoo@LIGO.ORG - posted 17:42, Sunday 30 September 2018 (44249)
LO work today

Not much got done. I installed a LP with Fc = 800Hz and -20dB attenuation between the output of LO common mode board and input of PZT driver. Because we can't bypass the PZT driver (Beckhoff needs it to talk to in-vac driver chassis) I turned on the 4Hz/400Hz compensation. OUT2 on the LO common mode board also get signal from IN2 and hooked up to IN1 so we can use both gain slide bars to give it even less gain. I can close the loop with the lowest gain setting without killing the OPO lock but non of the sign combinations (at input and slow) would lock the loop. Looking at IMON on SR785 the noise was pretty much all over the place but ~50kHz-70kHz seems to be its favorite hang-out spot.  I *think* we need a lot of gain to suppress high frequency noise but also can't have that because it will kick the OPO out of place (?). Right now the error signal comes out of IQ demod box. Will it help to install a PFD?
 

Feed forward work: I played around a little bit. Funny that I can't seem to make a different whether I get the output gain to 1, 100, or 1000. Even giving it an arbitrary offset wouldn't make a different to VCO frequency difference. The feed forward signal did show up on H1:SQZ-OPO_FREQ_OUTPUT (summing point according to the front end model).

 

Today I also learned that open/close the table can make >10mW difference in the Mephisto output power. I couldn't engage the EOM path until the power was stabilized.

Attachments: 1) LO config I've tried. 2) Spectrum of LO IMON

Images attached to this report
H1 ISC
gabriele.vajente@LIGO.ORG - posted 17:26, Sunday 30 September 2018 (44247)
Checked L2 test mass actuation

One possible suspect for the CSOFT problem is that one of the test mass actuators did not behave as expected. I injected noise directly into the L2_P stage, and measured the transfer function to DHARD_P error signal (I used DHARD since it is the most sensitive error signals).

All test masses L2 actuators behave as expected in pitch.

 

Images attached to this report
H1 ISC
gabriele.vajente@LIGO.ORG - posted 15:22, Sunday 30 September 2018 (44246)
Another try to decouple CHARD from CSOFT

Spoiler alert: no success (yet) in fixing the right-half-plane zero in CSOFT_P

Attempt 1

I added a line at 1 Hz on CHARD_P (amplitude 1000 cts) and could see it well in both CHARD_P and CSOFT_P. The transfer function at the line was CSOFT_P / CHARD_P = -1.3e-5, although the phase was not exactly 180 degrees. Nevertheless, I used this value of 1.3e-5 in the CSOFT blend filter bank, and could reduce the CHARD_P to CSOFT_P coupling by a factor of 3-5 or so (compare green trace TF with blue trace TF).

 

I measured again the CSOFT plant and found that the right-half-plane zero is still there.

Attempt 2

Since I saw a different optimal gain at different frequencies, and some phase rotation, I set up a sweep sine measurement of the coupling. The result is shown below, for frequencies between 0.5 and 2 Hz. There is indeed some structure and some (not too small) phase rotation, ecpecially around 1 Hz. The blue dot are the measurements, and the orange trace is a fit:

 

I implemented this filter in the CSOFT blend filter bank and measured again the coupling with the subtraction on. At all frequencies the coupling is now at least 20 times smaller. With a frequency dependent constant I was never able to get better than a factor of a few at frequencies around 1 Hz:

 

Unfortunately, this has almost no effect on the bad zero in the CSOFT_P transfer function.

 

Images attached to this report
H1 TCS (AWC, TCS)
daniel.vander-hyde@LIGO.ORG - posted 02:15, Sunday 30 September 2018 - last comment - 10:10, Tuesday 02 October 2018(44243)
Testing the inverted ring heater step response

Stefan, TVo, TJ, Danny

      Stefan has the idea of significantly reducing the amount of time it takes a test mass to reach a final lens by utilizing the ring heater step response and carefully designing an inverse filter to realize the inverse response.  We tested the idea in a previous post using Comsol data and were able to get a time series of the ring heater settings necessary to achieve a "step lens". To test this with measured data I took a time series  from H1:TCS-ITMY_HWS_PROBE_SPHERICAL_POWER after the ring heater settings had been changed by a reasonably large amount and attempted to perform the same procedure. The matlab zpk model of the system filter and inverse filter are attached figures. There are also comparison figures of the ring heater inputs and another figure their respective responses. 

Testing the new ring heater time series: 

With an initial lens around 3 microdiopters, the following figure shows convergence to a final lens of approximately -16 +/- 3 microdiopters within the first three hours but is about 1/2 the predicted lens. I might need to take another look at my model to see why this might be. 

I cut the script the short because there will probably be commissioners coming in tomorrow so I am using this method (on workstation ZOTWS2) in attempts to restore the original ITMY lens by tomorrow morning (but will run till 9/31 00:00 PST to maintain the lens). 

 

 

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 01:32, Sunday 30 September 2018 (44245)

Could the same missing 50% explain why the preloading was off?

daniel.vander-hyde@LIGO.ORG - 09:58, Tuesday 02 October 2018 (44271)AWC, TCS

Sorry Daniel. This 50% was due to a couple of ridiculous mistakes on my part. The first mistake was that I assumed that the initial step response was caused by a ring heater step of 1 watt when in reality it was caused by a step of 3.13 watts (please see attached image for updated plant zpk model with new gain).  The second, and most glaring mistake, was not thinking about the additive power from both of the upper and lower portions of the ring heaters so this left a factor of two missing in my model. I've attached time series of the measured data of the ring heater power compared to the time series from the updated model. I've attached a spherical power time series comparison as well. The final differential lens that the model suggests is 18.98 microdiopters.

In regards to pre-loading, I can update you on how these time series compare to the TCS simulation time series whose input parameters are used in the pre-loading estimates. 

Images attached to this comment
thomas.vo@LIGO.ORG - 08:47, Tuesday 02 October 2018 (44282)

The model of the pre-loading estimates use the calibration in diopters/watt on the TCS simulation page.

Spherical power (udiopters) = [ 2*(-9E-6) + 0.9E-6]  * P_RH = -17 udiopters for 1 Watt

The first coefficent in the equation is the substrate lens (the factor of 2 for double passing) and the second coefficient is the radius of curvature change.

daniel.vander-hyde@LIGO.ORG - 10:10, Tuesday 02 October 2018 (44287)AWC, TCS

Here is a comparison plot with the added TCS simulation time series. The simulation appears to be converging to a differential lens of 18 +/- 1 microdiopters.  

Images attached to this comment
H1 SQZ (SQZ)
nutsinee.kijbunchoo@LIGO.ORG - posted 17:19, Saturday 29 September 2018 - last comment - 17:19, Sunday 30 September 2018(44242)
SQZ locking loops automated

Haocun, Nutsinee

 

Almost every locking loop in SQZ land is now automated. I haven't created a manager node yet so you'll have to lock each loop by hand. Starting from SHG>OPO>PLL>FREQ>CLF (necessary for working on 3MHz locking loop).

 

SQZ_OPO Guardian will feed beat note error signal to laser temperature when it's in DOWN and feed PZT offset to pump laser temperature when it's LOCKED_ON_DUAL (or LOCKED). It will also disengage EOM when it's rail and stay in the CHECK_EOM state until somebody close it by hand (to make EOM relock itself requires a little more thinking. It probably could look at PLL guardian state).

 

SQZ_PLL (phase locking loop) will take care of beat note locking using OPO PZT once the OPO is locked (with TTFSS). SQZ_FREQ will feed (frequency) error signal from OPO common mode board fast path to OPO PZT once SQZ_PLL is locked.

 

When SQZ_OPO is down it will also take PLL, FREQ, and CLF down with it. Once OPO is relocked everything down the path still has to be locked by hand. PLL will complain if OPO isn't nominal and FREQ will complain if PLL is not nominal.

 

Neither feed forward nor 80MHz VCO is touched by Guardian yet. Everything worked repeatedly at least all day today. Will try to leave everything locked overnight.

 

All the SQZ guardians window can be found under SQZ GUARDIAN OVERVIEW button. I will create a compact overview of these guardian windows on SQZ_OVERVIEW later.

 

Terry also made a nice diagram of our current locking scheme. See attachment. Hopefully it'll be in the dcc soon.

 

Next: Lock the LO.

Images attached to this report
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 17:19, Sunday 30 September 2018 (44248)

Attached a screenshot of the new screen. Dash lines indicate independence. Arrows indicate flow/order of locking (eg. PLL and CLF can happen at the same time but FREQ has to happen after PLL is locked). In the end there should be a master node that controls everything from OPO to LO.

Images attached to this comment
H1 ISC
gabriele.vajente@LIGO.ORG - posted 16:47, Saturday 29 September 2018 (44240)
More on CSOFT and DSOFT

Summary

I think Hang's conclusions about the sign flip in the sensing matrix for CSOFT are wrong. Here's why, in brief:

  1. the new sensing matrix (with hang's changed sign) has degenerate rows for DSOFT_P and CSOFT_P, so with that configuration we are sensing only one of the two degrees of freedom
  2. I tried to step CSOFT_P and DSOFT_P (with a step of 0.3 slider units, using Hang's script move_ARM.py) and found that both CSOFT_P and DSOFT_P signals are sensitive ONLY to DSOFT (see plot below)
  3. I measured a sensing matrix at DC, and found that the signs do not match what reported by Hang's measurement.
  4. Inverting my DC measurement of the sensing matrix and using it, I get a nice decoupling of CSOFT_P and DSOFT_P.

Details

Step responses

Below the response to a step (with all soft loops open) in both CSOFT and DSOFT, by 0.3 slider units, using Hang's move_ARM.py script. The plot right below shows the response of both DSOFT and CSOFT error signals with the sensing matrix that has Hang's change of sign. Clearly both signals respond only to DSOFT, and are orthogonal to CSOFT. So even though in this configuration we are closing both CSOFT_P and DSOFT_P, we are controlling only DSOFT_P.

 

Sensing matrix at DC

I measured again the CSOFT / DSOFT / TMSX / TMSY sensing matrices for the four TRANS QPDs, using the same script used in the past. The results for pitch and yaw are reported below, in units of QPD signals over test mass and TMS slider values:

 

  CSOFT_PIT DSOFT_PIT TMS X PIT TMS Y PIT
H1:ASC-X_TR_A_PIT_INMON 0.027080 0.025287 0.081631 -0.000531
H1:ASC-X_TR_B_PIT_INMON -0.030390 -0.032043 0.162007 -0.001058
H1:ASC-Y_TR_A_PIT_INMON -0.001537 -0.003221 0.000275 0.089293
H1:ASC-Y_TR_B_PIT_INMON -0.187802 0.186769 -0.000672 0.182058

 

  CSOFT_YAW DSOFT_YAW TMS X YAW TMS Y YAW
H1:ASC-X_TR_A_YAW_INMON -0.012131 -0.011012 0.110482 0.000160
H1:ASC-X_TR_B_YAW_INMON 0.138589 0.137854 0.240005 -0.002157
H1:ASC-Y_TR_A_YAW_INMON 0.003813 -0.010138 -0.001525 0.097219
H1:ASC-Y_TR_B_YAW_INMON -0.115291 0.122388 0.001860 0.151168

Comparing the sensing matrix elements for CSOFT in my measurment and Hang's measurements, there's a sign flip for all Y QPDs. I am not sure what the origin of this difference is. However, I inverted the pitch and yaw matrices, to obtain the following:

 

  H1:ASC-X_TR_A_PIT_INMON H1:ASC-X_TR_B_PIT_INMON H1:ASC-Y_TR_A_PIT_INMON H1:ASC-Y_TR_B_PIT_INMON
CSOFT_PIT 12.185237 -6.159686 5.330350 -2.614611
DSOFT_PIT 11.668271 -5.858967 -5.454441 2.675180
TMS X PIT 4.597597 3.856154 -0.006480 0.039001
TMS Y PIT 0.616454 -0.329222 11.094065 0.051387

 

  H1:ASC-X_TR_A_YAW_INMON H1:ASC-X_TR_B_YAW_INMON H1:ASC-Y_TR_A_YAW_INMON H1:ASC-Y_TR_B_YAW_INMON
CSOFT_YAW -6.957181 3.270353 6.010876 -3.811676
DSOFT_YAW -6.338919 2.849835 -5.982599 3.894886
TMS X YAW 7.655904 0.642867 0.050068 -0.031134
TMS Y YAW -0.268093 0.179000 9.427309 0.555133

Based on those measurements, and rescaling the elements so to match the size and sign of the current, error signals, I computed a new ASC input matrix for soft pitch and yaw and implemented it. It's very close to the old one, before Hang's sign flip.

New step response

With the new input matrix, the CSOFT and DSOFT error signals behave as expected:

 

To cross check, I also stepped CSOFT_Y and DSOFT_Y, and foud the error signal properly decoupled:

 

A also did a quick measurement, with both CSOFT and DSOFT PIT loops closed, by injecting a line at 5.1 Hz. When injecting a DSOFT line, only the DSOFT signal sees it. Instead, when injecting a CSOFT line, there is some cross-coupling to DSOFT: the DSOFT signal also sees a line at 5.1 Hz, just a bit smaller than what is seen in CSOFT. It's not clear to me why this is the case. See fourth attachment.

Images attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 16:15, Friday 28 September 2018 - last comment - 01:05, Sunday 30 September 2018(44234)
1st attempt at bagging leaking 12" CFF flange atop the OMC tube was attempted then aborted

I tried to bag and then evacuate the leaking 12" CFF flange so at to reduce the leak rate until this can be repaired in NOV. but my attempt was thwarted by the unique fabrication of this 10" nozzle.  As Gerardo M. pointed out to me later, the nozzle roll has a vacuum weld on the interior of the roll seam and an external stitch weld.  This is unexpected as all "normal" port nozzles utilize full penetration seam welds.  The net effect of this is that a channel is left on the external side of the seam and this channel makes it impossible to seal a bag against (without cheating and using some sort of fluid sealer).  I'll point this unique detail out to Chandra R. next week and she can decide if the benefit of potentially reducing the leak rate is worth the use of :the required fluid sealant. 

Comments related to this report
chandra.romel@LIGO.ORG - 01:05, Sunday 30 September 2018 (44244)

You can seal along the stitch weld assuming it penetrates the interior vacuum weld, leaving no air channel. You could also seal directly at beam tube.

Images attached to this comment
Displaying reports 45401-45420 of 88367.Go to page Start 2267 2268 2269 2270 2271 2272 2273 2274 2275 End