Displaying reports 53221-53240 of 83280.Go to page Start 2658 2659 2660 2661 2662 2663 2664 2665 2666 End
Reports until 12:17, Wednesday 26 October 2016
H1 CAL
aaron.viets@LIGO.ORG - posted 12:17, Wednesday 26 October 2016 - last comment - 08:30, Friday 28 October 2016(30888)
Calibration Factor Comparison between GDS pipeline and SLM tool
Below are plots comparing the kappas and cavity pole from LHO as computed in the GDS pipeline and the SLM tool. The data is from the end of a lock stretch, starting on October 24, 2016, at GPS time 1161341820, and lasting 4.5 hours. The agreement is very good for the most part, with the following exceptions:

1) kappa_c as computed by GDS is slightly larger than that computed by SLM.

2) The cavity pole as computed by GDS is smaller by about 2-3% (~10 Hz).

Below is a table of mean and standard deviation values for the data taken from GDS, SLM, and the ratio GDS / SLM:

                                   SLM mean         SLM std          GDS mean          GDS std             ratio mean            ratio std

Re(kappa_tst)             0.8920              0.0068            0.8915                0.0058              0.9995                  0.0044

Im(kappa_tst)             -0.0158             0.0039            -0.0145               0.0014              0.9725                   1.0764

Re(kappa_pu)             0.8961              0.0080            0.8956                0.0059              0.9995                  0.0067

Im(kappa_pu)             -0.0050            0.0056            -0.0034              0.0022               0.1662                  28.8601

kappa_c                      1.1115                0.0094            1.1168                 0.0087               1.0048                  0.0078

f_c                               354.2332         2.9296            345.0556           2.3106               0.9742                   0.0104
Non-image files attached to this report
Comments related to this report
aaron.viets@LIGO.ORG - 08:30, Friday 28 October 2016 (30957)
Below is an updated table of mean and standard deviation values for the data taken from GDS, SLM, and the ratio GDS / SLM with imaginary parts rescaled by adding 1.0 (~the magnitude of the kappas):

                                   SLM mean         SLM std          GDS mean          GDS std             ratio mean            ratio std

Re(kappa_tst)             0.8920              0.0068            0.8915                0.0058              0.9995                  0.0044

Im(kappa_tst)             -0.0158             0.0039            -0.0145               0.0014              1.0014                   0.0042

Re(kappa_pu)             0.8961              0.0080            0.8956                0.0059              0.9995                  0.0067

Im(kappa_pu)             -0.0050            0.0056            -0.0034              0.0022               1.0017                   0.0061

kappa_c                      1.1115                0.0094            1.1168                 0.0087               1.0048                  0.0078

f_c                               354.2332         2.9296            345.0556           2.3106               0.9742                   0.0104


Here are covariance matrices and correlation coefficient matrices between SLM and GDS:

       Covariance                          Correlation

Re(kappa_tst)
1.0e-04 *
    0.4618    0.3208                  1.0000    0.8163
    0.3208    0.3345                 0.8163    1.0000

Im(kappa_tst)
1.0e-04 *
    0.1507    0.0012                   1.0000    0.0211
    0.0012    0.0210                   0.0211    1.0000

Re(kappa_pu)
1.0e-04 *
    0.6385    0.3128                 1.0000    0.6636
    0.3128    0.3480                 0.6636    1.0000

Im(kappa_pu)
1.0e-04 *
    0.3140    -0.0036               1.0000   -0.0293
   -0.0036    0.0495               -0.0293    1.0000

kappa_c
1.0e-04 *
    0.8895    0.4464               1.0000    0.5464
    0.4464    0.7502               0.5464    1.0000

f_c
    8.5828   -0.0252              1.0000   -0.0037
   -0.0252    5.3387              -0.0037    1.0000

Updated plots are attached as well.
Non-image files attached to this comment
H1 ISC (DetChar, ISC)
lisa.barsotti@LIGO.ORG - posted 12:02, Wednesday 26 October 2016 - last comment - 22:55, Wednesday 26 October 2016(30895)
Request for bruco on SRCL/PRCL/MICH
Stefan and I were wondering if someone could re-run Bruco on SRCL/PRCL/MICH on  the other night good data, similarly to what Gabriele did some time ago.

Also, I attach here the coherence between SRCL and IMC WFS at some point during O1; this seems much lower than what seen recently, which I think makes sense based on  Sheila's IMC WFS comparison  before and after the HPO was turned on.

Images attached to this report
Comments related to this report
young-min.kim@LIGO.ORG - 13:22, Wednesday 26 October 2016 (30897)

Here are the BruCo scan on SRCL/PRCL/MICH on the other good time.

I picked up Oct. 24, 08:00 UTC as the other good time.

SRCL: https://ldas-jobs.ligo-wa.caltech.edu/~youngmin/BruCo/PRE-ER10/H1/Oct24/H1-SRCL-1161331217-600/

PRCL: https://ldas-jobs.ligo-wa.caltech.edu/~youngmin/BruCo/PRE-ER10/H1/Oct24/H1-PRCL-1161331217-600/

MICH: https://ldas-jobs.ligo-wa.caltech.edu/~youngmin/BruCo/PRE-ER10/H1/Oct24/H1-MICH-1161331217-600/

 

The results are updated using new excluded channel lists.

sheila.dwyer@LIGO.ORG - 22:55, Wednesday 26 October 2016 (30912)

It looks like the coherence of the IMC WFS with the SRCL error signal is mostly above 80 Hz, where our jitter is similar to what it was during O1 according to the IMC WFS (spectra in the alog that Lisa links ). 

I looked at the coherence of the two sensors used for the SRCL error signal, POP45 I and POP9I, and we can see that POP 9I has more coherence with the IMC WFS at the frequencies where we think accoustic motion of mounts on the PSL table dominate the jitter. 

Images attached to this comment
H1 SEI
hugh.radkins@LIGO.ORG - posted 09:55, Wednesday 26 October 2016 (30887)
SEI Alignment differences after Tuesday's HEPI Work

Yesterday, all the ISI and HEPIs were deisolated to check the fluid system Accumulators' gas charge.  All HEPI and ISI DC positions are held by the Isolation loops except for the BSC's ISIs.  I reviewed these platforms' cartesian positions and the ETMYs RX tilt has the largest shift at 3urads, ITMX RX delta is 1.5urads.  Some positions change by a couple ums: ETMY X shifted 2um, ITMX X shifted 1um.  All other shifts are a few hundred nm or nrads or less with most being less than 100nanounits.

I don't think the SEI is contributing to alignment difficulties.

H1 PSL
keita.kawabe@LIGO.ORG - posted 09:34, Wednesday 26 October 2016 - last comment - 14:00, Friday 28 October 2016(30886)
PMC length locking

I got suspicious about PMC length locking offset and changed H1:PSL-PMC_INOFFSET.

Increasing it by 1.7mV decreased the PMC length feedback by about a factor of 2, and 1st loop out of loop sensor by a factor of 4 or so, which doesn't make sense. In the attached, red and green are with nominal 3.1mV offset, blue and brown are with 4.8mV.

(After this measurement I noticed that Daniel increased the length gain from 16 to 28dB and forgot to bring it back. This measurement is with 28dB locking gain, but it still doesn't make sense.)

What's the nominal signal level for PMC demod? Is it tiny? When is the last time the PMC demod phase was optimized?

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 15:46, Wednesday 26 October 2016 (30902)

More strange stuff, when we look at the PDA and PDB photodetectors of the first loop in the ISS. In the attached plot, the current traces are with a PMC offset of 3.28mV, reference traces 1-15 are with a 3.58mV offset and reference traces 16-19 are with a 2.98mV offset. With a positive offset change we see a some degradation in PDA at high frequencies, whereas PDB sees significantly less noise. For a negative offset PDA gets a tad bit better and PDB gets worse. Overall PDB shows up to an order of magnitude change in its noise level, whereas PDA only shows up to a factor of 2, going the opposite way. The PMC gain was high and 28dB.

Non-image files attached to this comment
daniel.sigg@LIGO.ORG - 13:18, Wednesday 26 October 2016 (30896)

Here is the throughput as function of the offset with a Lorentzian as a fit. The parameters are 0.761, 3.28mV and 4.59mV for the amplitude, offset and HWHM, respectively. Looks like the demodulated signal is only ~9mV pk-pk.

Non-image files attached to this comment
sheila.dwyer@LIGO.ORG - 08:12, Thursday 27 October 2016 (30922)

(Keita writing as Sheila)

For those of you who are interested, Daniel's measurement doesn't mean that the noise behavior (in length locking and in intensity noise) makes sense.

keita.kawabe@LIGO.ORG - 11:13, Thursday 27 October 2016 (30930)

(Now writing as myself.)

According to T0900577 (select ilspmc_servo3.pdf) the output of TUF-3 mixer is amplified by a DC gain of 4 and sent to a summation amplifier that has a gain of 10 for the demod and a gain of 1/100 for the offset.

The offset signal seems to be calibrated to represent the offset in the OUTPUT of the summation amplifier (i.e. +-100mV when the offset from DAC is +-10V). Update: I was deceived by HOPR and LOPR of he signal on MEDM being 100 and -100, but the calibration filter of this channel of this gain is just 3.2k, so the number should represent the equivalent offset after the gain of 4 but before the gain of 10.

So this 9mVpp is after the gain of 40 total, the demod right after the mixer should be ~9mV/4/10=230uVpp.

Update: The demod right after the mixer should be ~9mV/4=2.3mVpp.

If this is true this is excessively small and cannot be good, and I wonder if the demod phase is correct or if this is an expected signal level. If this is as designed, can't we increase the modulation depth upstream or something?

(The main document in the above DCC is so-called PDF Portfolio, which is just a document containing all pdfs listed in "other files". If you're on Linux workstations the pdf in the above DCC appears as if it's just a one-page document promoting Adobe product, but if you're using evince document viewer, change "thumbnails" on the left panel to "attachments", and you can select whichever file in the portfolio to view).

daniel.sigg@LIGO.ORG - 14:00, Friday 28 October 2016 (30963)

Looking at the RF chain:

  • The output of the RF amp in the CER is 13 dBm
  • There is a 2 dB attenuator in the CER
  • Assuming 1 dB cable loss
  • There is a 20 dB attenuator at the PSL rack panel

Therefore, the drive to the modulator seems to be -10 dBm, or 71 mV rms. A standard New Focus 4004 EOM has a modulation coefficient of 25 mrad/V. So the estimated modulation depth is around 1 mrad.

The mixer readbacks are flawed and just see ADC noise. They could use a gain of 200 to get above the ADC noise. Proposed values:

  • N7: OP27
  • R33: 1K
  • R11: 200K
  • R12: 0
  • C4: 33p
  • J2: remove
H1 General
jeffrey.bartlett@LIGO.ORG - posted 06:20, Wednesday 26 October 2016 (30885)
Ops Owl Shift Summary (Shortened)
 Ops Shift Log: 10/26/2016, Owl Shift 07:00 – 15:00 (00:00 - 08:00) Time -  UTC (PT)
State of H1: IFO is unlocked. Working on relocking after the maintenance window
Intent Bit: Commissioning
Wind: Is ranging from Calm to Light Breeze (0-7mph)
0.03 – 0.1Hz: Currently at 0.07um/s – Ringing down from EQ
0.1 – 0.3Hz: Trending lower – Currently at 0.8um/s
Outgoing Operator: TJ
Incoming Operator: Travis
 
Activity Log: Time - UTC (PT)
07:00 (00:00) Take over from TJ
07:45 (00:45) Adjust Dust Monitor alarm levels
12:18 (05:18) Put IFO into DOWN, due to alignment and locking troubles 
13:30 (06:30) End Shift early. 

Shift Details:
Support: Sheila 
Shift Summary: IFO unlocked. 

After a difficult but successful Initial Alignment by the Evening shift, working on relocking. After a long night (very long for Sheila) of many tweaks were able to get the IFO to lock at DC_READOUT once for about 30 minutes. After this lock broke we were unable to get past green locking. There are problems with INPUT_ALIGN hanging at LOCKING_XARM_IR, (see aLOG #30881). Sheila did not think there was much chance of successful locking. I put the IFO into DOWN to await the refreshed minds and fingers of the day shift to continue the good works of the past two shifts.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 05:57, Wednesday 26 October 2016 - last comment - 13:46, Wednesday 26 October 2016(30884)
X-Arm Green Laser Power
 Sheila & Jeff B.
 
 Over the past few shifts the ALS green power build up in the X arm has steadfastly remained below 0.95 despite all tuning efforts. The Y arm build up as been normal. We trended the X Arm DC power. On the 24th the power of the green laser dropped from 1.02 to 0.95, (trend posted below).       

   
Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 13:46, Wednesday 26 October 2016 (30898)

[Travis, Jenne]

We tried chasing alignments a little bit, but also can't get the transmitted power above 0.95ish.  Travis suggested looking at the laser itself.  In the attached screenshot you can see that the green DC power measured at the end station dropped suddenly, at a time corresponding to the drop in transmitted power.  Why would the power drop like that?  Were there things going on at the end station around the 24th?

Images attached to this comment
H1 PSL
peter.king@LIGO.ORG - posted 04:23, Wednesday 26 October 2016 (30883)
Picomotor equipped mirror mounts installed
After making a minor modification to a pair of mirror mount supports, a pair of Picomotor equipped mounts
were installed on the PSL table.  These mounts steer the beam into the pre-modecleaner, the controls for
which are accessible from the ISC Picomotor MEDM screen.  Picomotor A (aka #1) is the one furthest from the
pre-modecleaner and closest to the high power oscillator, B (aka #2) the one closest to the pre-modecleaner.
Yaw controls are X, pitch Y.

    The modification made to the base was to avoid crushing the flat cables that come from the Picomotors.

    Work performed under work permit #6268.


Rick/Jason/Peter
H1 ISC
sheila.dwyer@LIGO.ORG - posted 02:57, Wednesday 26 October 2016 (30882)
DBB plugged back in

This afternoon Kiwamu and I plugged the DBB back in.  When we did this, the PSL external shutter closed; Peter King said that it is a know issue that shutters close randomly when you power things on or off in those racks. 

I also took put a 1/100 divider on the BNC connector from the 18V rack power, AC coupled it with a 560 and plugged it into LSC_EXTRA_AI_1.  The plan is once we are locking to try another test of the DBB shutters, and see if it still has an impact on our nosie with the TCS and alingment changes from last weekend.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 02:48, Wednesday 26 October 2016 - last comment - 00:51, Thursday 27 October 2016(30881)
Alingment troubles

We have had trouble with alingment since maintence day today.  There were several things that happened that could potentially impact alingment: SUS models were restarted, HEPI work, and adding picomotors to the PSL before the PMC.  The PSL work is probably the most likely culprit.  I hope that we will be more selective about what we choose to do on maintence day from now on.

Alingment symptoms:

The PMC alingment is not as good as it had been.  There were also shifts in the alingments of MC1+3, especially in yaw.  Were these from model reboots or did someone intentiaonally change them to relock the mode cleaner?  The spot on IM4 trans move from 0.2 in yaw to -0.35 or so.  TJ and I trended all the IM osems and they hadn't moved much, but we restored the small changes.  Once Jeff B and I finally got the IFO locked (I engaged the soft loops one at a time by hand), our recycling gain was very low (below 24).  I tried to move MC1+3 in yaw to restore the position on IM4, both earlier with TJ and with the full IFO locked, the MC WFS generally drag it back to where it was.  With the full IFO locked I moved IM3 in yaw, which did help the recycling gain (I chose IM3 because it's after teh Faraday, not because I think it is what moved).  I moved it too fast and broke the interferometer lock, so we finished using it to restore the position on IM4 Trans with just the mode cleaner locked.  We partially reverted this because we saw no flashes in the arm, and are going to give up for the night now.

If we still have this problem in the morning, it is probably worth taking a look at the irises that Cheryl placed on the PSL table a while ago to see if the beam goes into the IMC with the same alignment.

REFL WFS don't work for PR2 at 2 Watts:

I changed the ISC_LOCK guardian back to using POPX WFS for acquisition.  The point of the POPX WFS is that they can be used even when inital alingment isn't great and the recycling gain is low, so we would like to keep them on for power up and switch to REFL WFS in LOWNOISE_ASC.  I've put some code in low noise ASC to switch back, but we haven't gotten to test this yet. I guess that the matrix to use REFL to control PR2 was probably tested at 25 Watts last night but set up in the guardian for use at 2 Watts, because Jeff B couldn't engage the REFL WFS yesterday morning after commisioners left.  Tonight it was clearly breaking the lock, which might have been partly because of our bad alingment, but when we changed it back to POPX it was fine. 

Initial Alignment changes:

Jeff B and I just made a few changes to initial alingment, after TJ, Evan, and I had difficulty with input align earlier in the night.  Although our alingment change today probably contributed to this, I think the changes are good and things I've been meaning to do for a while anyway.

Comments related to this report
kiwamu.izumi@LIGO.ORG - 15:31, Wednesday 26 October 2016 (30899)

Betsy, Jason, Travis, Kiwamu,

After some investigation and tentative adjustments, the situation did not improve after all. We still have no idea what happened.

In the end, we restored all the suspensions back to where they were before the maintenance and steered the IM3 yaw to obtain a value of +0.2 in IM4_TRANS_YAW.


[Some conclusions]

  • We don't think the PSL pointing has changed according to the irises in the PSL.
  • The MC2 trans loop (DOF3) seems to bring us to the same point as before according to the beam spots on the wall of the PSL booth (see the attached picture).
  • The behavior this time seems to be different from the old mysterious behavior we had seen in 2014 (15650) in the sense that restoring all the suspensions did not bring us back to the same IM4 QPD position this time. 

[Summary of the activities]

  • We went into the PSL and checked the beam spot on two iris locations.
    • One right below the bottom periscope (which I think was installed for allocation of the PZT mirror last year, 17976). And the other at the transmission of the bottom periscope mirror which Cheryl installed a long time ago.
    • Both of them seemed extremely good and therefore we found no indication of misalignment.
  • We restored all the suspensions to where they were before the maintenance by using the witness sensors.
  • We went into IOT2L and steered some optics.
    • The beam seemed higher everywhere by a few mm which is consistent that we have some misalignment in yaw. Although, since it was so small that we decided not correct for it.
    • We centered the beam on REFL LSC diode and the two WFS diodes. The LSC diode was aligned manually by steering the beam splitter in front. The WFSs were aligned using the picomotors. All of them were done when the IMC was unlocked.
    • Re-adjusted some beam dumps, trying to catch stray light without approaching too close to the main beam.
  • Checked the beam spots on the PSL wall by opening the PSL light pipe. See the attached picture.
    • Out of three beam spots, two were found to be unchanged. The other one was different by a few mm. I have no idea what this means and how yesterday's activity impacted on these locations (30867).

[Summary of the shift]

The following tables summarize the alignment before the alignment and after our investigation and adjustments.

Summary table for pitch

 

before [urad]

around Oct/24/2016 20:50 UTC

after [urad]

around Oct/26/2016 21:20 UTC

change [urad]

after - before

MC1 witness sensor   +44  +40  -4
MC2 witness sensor  +503  +501  -2
MC3 witness sensor  -915  -912  +3
IM1 witness sensor  +186  +186  0
IM2 witness sensor  +608  +607  -1
IM3 witness sensor  + 1956  +1932  -24
IM4 witness sensor  -3860  -3863  -3

 

Summary table for yaw

 

before [urad]

around Oct/24/2016 20:50 UTC

after [urad]

around Oct/26/2016 21:20 UTC

change [urad]

after - before

MC1 witness sensor   -1037  -1050  -13
MC2 witness sensor  -676  -676  0
MC3 witness sensor  -1011  -996  +15
IM1 witness sensor  +1117  +1117  0
IM2 witness sensor  -209  -208  +1
IM3 witness sensor  -37  +145  +182
IM4 witness sensor  -533  -558  -25

As I was writing these values, I noticed that the the beam waist location of the IMC translated by roughly 0.5 mm according to equation (4) in P1000135. I have no idea how we ended up introducing this translation in the IMC eigen axis without changing the input beam line determined by the PSL periscope mirror and the MC2 spot position. As expected, we compensated whatever the misalignment by introducing a +182 urad offset to IM2. If this compensation by IM3 is not perfect (and probably this is true in reality), this will result in a different spot position on PRM. The rest of the interferometer should be fine in principle.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 00:51, Thursday 27 October 2016 (30918)

Jenne, Sheila, Kiwamu,

In addition, we did a brief test in order to distinguish whether this is due to a change in the PLS pointing or something in the suspensions.

We conclude that misalignment in PSL (if any) don't explain what we see on IM4_TRANS. Again, we still don't have an idea of what happened.

[The test]

We restored all the suspensions back to the values listed above. We disabled the IMC ASCs so that they don't pull the suspensions to whatever the points they want to park. The idea is that with the restored suspension, we should get back to the same value on IM4_TRANS if all the misalignment was due to something in the PSL. If the spot on IM4_TRANS does not come back to the old location, then something in the chamber must have changed.

[Results]

Initially, the yaw signal of IM4_TRANS was about -0.4 counts before we restored the suspensions. After the restoration, the value became -0.1 which is closer to what it was (+0.2). However, obviously we did not fully come back to the old value on IM4_TRANS. This means that misalignment in PSL alone can not explain the situation right now. Something else likely in the chamber must have moved.

This result motivated us not to touch the PSL. Instead we decided to move IMs to recover a high recycling gain in the interferometer (30910).

H1 PEM
jeffrey.bartlett@LIGO.ORG - posted 00:50, Wednesday 26 October 2016 (30880)
Dust Monitor Alarm Levels
   Reset the dust monitor alarm levels back to correct values after maintenance window. 
H1 SUS
sheila.dwyer@LIGO.ORG - posted 00:20, Wednesday 26 October 2016 - last comment - 11:07, Wednesday 26 October 2016(30879)
ETMX BIO settings keep being restored to something wrong

For some reason the ETMX bio settings are frequently being set to something inoperable. I think this is the third time I've seen these settings in the last week or two. (It happened on sunday after the CDS problems, and I think maybe last tuesday). The ESD should be set to high volts, enabled.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 11:07, Wednesday 26 October 2016 (30892)
Open FRS Ticket 6527.

I'll look at this as soon as I can. Apologies for leaving before full recovery to be able to catch and address this.
H1 CAL (CAL)
richard.savage@LIGO.ORG - posted 18:33, Tuesday 25 October 2016 - last comment - 10:57, Wednesday 26 October 2016(30877)
Yend Pcal beams realigned - clipping relieved

DarkhanT, Yuki Inoue (KAGRA), RickS (SudarshanK assisting with image analysis over the phone - until the phone died).

Today, we went to Yend to investigate the apparent clipping that EvanG had discovered (see entry 30827).

We found that both beams were off centered on the aperture of the Rx module integrating sphere, with the Outer (lower) beam clipping on the aperture (see attached image).  Blocking one beam and then the other revealed that the increased noise in the Rx power sensor spectrum was all due to the clipping of the Outer beam.

Camera images revealed that the beams had moved on the ETM as well (exonerating movement of the ETM as the cause of the movement on the Rx side).

Analyzing Pcal camera images we found the beam position offsets from the optimal locations were (x, y): Upper (-1.5, 1.8); Lower (-6.9, -2.5) (millimeters) Usual x,y convention: positive x, right; positive y, up.

Not knowing what had moved, we used the output steering mirrors in the Tx module to center the beams on the Rx intetrating sphere aperture (see attached photo).

After moving the beams, analysis of camera images (see attached)  gave the following beam locations (x, y): Upper (-1.4, -0.9); Lower (-1.3, -1.4) (millimeters). 

These are within our 2 mm tolerance.

We installed apertures at the output of the Tx module and at the input (just upstream of the steering mirrors) in the Rx module.

We will repeat the Yend calibration using the Working Standard as soon as possible.

Images attached to this report
Comments related to this report
evan.goetz@LIGO.ORG - 10:57, Wednesday 26 October 2016 (30890)
Spectra look much better too! Attached are times from before Oct 11 maintenance work (blue), just after Oct 18 maintenance work (green), and this morning after the clipping had been fixed (red). Note that the amplitude of the 331.9 Hz has returned to the O1 amplitude.

A trend of the mean power level over the last 10 days is also attached. The calibration discrepancy between TX and RX PD is likely now reduced. Previously, as identified by Shivaraj (LHO aLOG 30845), the discrepancy was ~4%. Now the discrepancy is less than ~1% as the end of the trend indicates.
Images attached to this comment
H1 ISC (ISC, PSL)
marc.pirello@LIGO.ORG - posted 16:37, Tuesday 25 October 2016 - last comment - 10:57, Wednesday 26 October 2016(30869)
H1 VCO Modification Complete

M. Pirello, A. Ramiez,  E Castrellon

Work Permit 6271

Per ECR E1600292 we applied the VCO capacitor mod to all 5 VCO's in the corner station and one at each end station.  This process includes replacing the 10nF capacitors on C79 and C80 with 2uF capacitors, and checking the voltage rails to verify elimination of the 420kHz oscillations.

Corner Station Units:

S1200563, S1200559, S1200560, S1200564, S1200558

End X:

S1200561

End Y:

S1200566

Notes:

End X, there was a very inconvient clean room pole directly in the path of extraction for the VCO from the rack.  We had to relocate 2 chassis to angle the VCO enough for removal.  All chassis were put back in their original positions before leaving.

End Y, this VCO required more capacitance to remove all of the 420kHz noise on the -24V Rail, with the addition of a 2nd 2uF capacitor, the noise was eliminated.

Comments related to this report
marc.pirello@LIGO.ORG - 10:57, Wednesday 26 October 2016 (30891)ISC, PSL

After going through my notes, the following should also be logged.

VCO S1200563 is outfitted with a PLL board.  This board is attached to the existing board via an SMA-T connector on the Low Noise VCO Board.  This connector was very loose when we opened up the chassis, and the end that is supposed to connect to the PLL board was disconnected and wedged between two VCO modules.  The SMA was very loose here.  We showed Richard this and he advised us to remove the SMA-T and the SMA jumper cable which was disconnected, we then used an SMA cable torque wrench to ensure proper torque on the connectors.

When we worked on the 2nd PLL VCO chassis (S1200564), we noticed that the SMA-T was torqued, and the SMA jumper was attached to the PLL board.

LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 15:13, Tuesday 25 October 2016 - last comment - 10:25, Thursday 03 November 2016(30860)
Y-End RGA Powered On

(Carlos, Richard, Gerardo)

Y-End RGA is ON.

Comments related to this report
kyle.ryan@LIGO.ORG - 11:11, Wednesday 26 October 2016 (30893)
By "on" I assume that the electronics are energized (i.e. the fan is running) but not the filament?
chandra.romel@LIGO.ORG - 10:25, Thursday 03 November 2016 (31162)
That is correct, Kyle.
H1 CAL (CAL)
evan.goetz@LIGO.ORG - posted 13:38, Monday 24 October 2016 - last comment - 10:25, Wednesday 26 October 2016(30811)
Amplitude of 331.9 Hz Pcal line reduced
Since the noise of the detector has improved around the 331.9 Hz Pcal injection frequency, we can reduce the amplitude of the injection (current setting 9000 cts for both sine and cosine). I have reverted changes that increased the amplitude of this line (see LHO aLOG 30476). The new amplitude setting is 2900 (for both sine and cosine amplitudes), which is the same as it was before increasing the injection amplitude.

This also brings the total injections to Pcal Y below the threshold (see LHO aLOG 30802). The threshold is 44,000 counts. The current total injection is now 38650.0 counts.

Screenshot of excitation settings attached.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 13:45, Monday 24 October 2016 (30812)
Note to self: check the front-end calculations of the uncertainty and coherence of these lines before and after this change after the IFO reverted back to 25 [W] input power. 
Example checks: 
   - do the calculations show the expected decrease in coherence / increase in uncertainty? 
   - how much was the uncertainty / coherence when the SNR was so high? 
   - do we like that level of uncertainty? did it reveal more real optical parameter changes instead of noise?

evan.goetz@LIGO.ORG - 10:25, Wednesday 26 October 2016 (30889)
Delayed update, these changes were accepted in the SDF today (Oct. 26, 2016, ~10:20 PDT).
Displaying reports 53221-53240 of 83280.Go to page Start 2658 2659 2660 2661 2662 2663 2664 2665 2666 End