Displaying reports 53701-53720 of 84797.Go to page Start 2682 2683 2684 2685 2686 2687 2688 2689 2690 End
Reports until 11:22, Tuesday 29 November 2016
H1 PSL (PSL)
peter.king@LIGO.ORG - posted 11:22, Tuesday 29 November 2016 (31966)
laser trip
I was informed that the laser had tripped this morning.  Not sure exactly why the laser tripped as TwinCAT indicated
that the EPICS alarm was triggered.  At first glance it looks like the flow in head 3 caused the trip.  It reached
the trip value (0.4 lpm) roughly 2 seconds before heads 1 and 2.

    Attached are other trends of the laser power(s) versus the flow rate in head 3.  There is some evidence to
suggest that the NPRO might have tripped first, triggering the power watchdog for the front end (mis-named
Head2NPROa.png).

Images attached to this report
H1 AOS (DetChar)
paul.schale@LIGO.ORG - posted 11:11, Tuesday 29 November 2016 (31967)
H1 DQ Shift 21 November - 23 November

Summary:

Average range: 70 Mpc

Duty Cycle: 35% (commissioning activities reduced observing time)

1080Hz glitching continuing

Mysterious noise at 10-30Hz for ~2 hours on Tuesday (22nd)

Hardware injections during observing time on Wednesday (1 CBC, 10 detchar safety injections)

Full DQ Shift report: https://wiki.ligo.org/DetChar/DataQuality/DQShiftH120161121

H1 CDS (CDS, VE)
patrick.thomas@LIGO.ORG - posted 10:39, Tuesday 29 November 2016 (31965)
Updated vacuum alarm handler at ops station
Added error channels to help address issue reported in alogs 31910 and 31912. Also added all pressure gauges and updated guidance text.

Completes WP 6358.
LHO General
corey.gray@LIGO.ORG - posted 10:31, Tuesday 29 November 2016 (31964)
Maintenance Status

Hoping for a light Maintenance (since many activities done yesterday) & aiming for ending at noon.  Cheryl handed over a locked H1 & it stayed locked for quite a while into Maintenance before dropping out....

H1 PSL appeared to trip (causing lockloss).  Peter & Jeff B addressed and are looking into why it dropped out.

H1 CDS (SUS)
james.batch@LIGO.ORG - posted 09:56, Tuesday 29 November 2016 (31963)
Web MEDM screen shots modified to add ETMX, ETMY.
I have added MEDM overview screens for H1 SUS ETMX, ETMY to the CDS web screen shots pages. 
H1 ISC
kiwamu.izumi@LIGO.ORG - posted 09:55, Tuesday 29 November 2016 (31962)
removed a temporary digital camera from ISCT6

This morning when the interferometer was down, I went to the ISCT6 table and removed the temporary digital camera or CAM17 (that was for the SRC Gouy phase measurement, see for example 29389). The beam for this camera is currently dumped by an additional razor blade dump on the table. The ethernet cable was re-routed and plugged to the OMCR camera which is the nominal cabling configuration. Additionally, I have left the base plate for the camera untouched in case we want to revisit the same measurement.

H1 General
cheryl.vorvick@LIGO.ORG - posted 08:14, Tuesday 29 November 2016 (31959)
Ops Owl Summary:

State of H1: locked in NLN in Observe

Commissioners: Sheila, Jenne (early in the shift)

Activities:

Violin Mode Damping:

H1 General
cheryl.vorvick@LIGO.ORG - posted 07:29, Tuesday 29 November 2016 (31958)
changed phase on PI mode 28 in Observe 15:27-15:29UTC

H1 General
cheryl.vorvick@LIGO.ORG - posted 07:21, Tuesday 29 November 2016 (31957)
Maintenance Day Begins:
H1 General
cheryl.vorvick@LIGO.ORG - posted 06:17, Tuesday 29 November 2016 - last comment - 06:38, Tuesday 29 November 2016(31954)
Noise Tunings run by hand, no lock loss, running a2l, and Observe is on hold

Noise Tunings:

a2l:

Observe:

Comments related to this report
cheryl.vorvick@LIGO.ORG - 06:33, Tuesday 29 November 2016 (31955)

14:31UTC: H1 is in Observe

Manually put IMC_LOCK in ISS_DC_DECOUPLED, then H1 into Observe

cheryl.vorvick@LIGO.ORG - 06:38, Tuesday 29 November 2016 (31956)

Noise Tunings attachments:

Non-image files attached to this comment
H1 OpsInfo
sheila.dwyer@LIGO.ORG - posted 01:18, Tuesday 29 November 2016 (31953)
beam diverters back in guardian

Because we are probably not going to be able to close the pop beam diverter right away, I removed it from the CLOSE beam diverters state and added this state back into the normal path to nominal low noise, so that at least the AS and REFL beam diverters will be nominally closed for the start of the run. 

H1 General
cheryl.vorvick@LIGO.ORG - posted 01:07, Tuesday 29 November 2016 (31952)
Owl Shift Transition

State of H1: Initial Alignment just completed, working to lock full IFO

Commissioners: Jenne, Sheila

Activities:

H1 General
jim.warner@LIGO.ORG - posted 00:02, Tuesday 29 November 2016 (31950)
Shift Summary
TITLE: 11/29 Eve Shift: 00:00-TITLE: 11/29 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PS0:00 PST), all times posted in UTCTITLE: 11/29 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
TITLE: 11/29 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:    Not having much luck.
LOG:
1:00 Kyle back
1:00 Kiwamu to LVEA to check PSL spot position
 
Locking tonight has been difficult. Sheila and Jenne are realigning the IMC.
STATE of H1: Aligning
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
LOG:
H1 AOS
robert.schofield@LIGO.ORG - posted 23:39, Monday 28 November 2016 (31949)
New piezo mirror mount installed

Kiwamu and I installed the new piezo mirror mount. The frequency of the peak in quad diodes increased and was damped as expected, but the final arbitrator is DARM and we havent locked yet. I will put in a log with details when we do.

H1 CDS (Lockloss)
sheila.dwyer@LIGO.ORG - posted 21:02, Monday 28 November 2016 - last comment - 09:36, Friday 02 December 2016(31948)
POP 90 jumping, causes lockloss

Jenne, Sheila Keita

We had another instance of a jump in POP90, in which both the I and Q phases increased. We think this is a problem with the readback, similar to what is described in 31181.  

We were acquiring lock, and had no ASC running on the SRC.  We looked at witness sensors for all the interferometer optics, and it looks like none of them moved at the time.  We also don't see changes in other RF sensors, like AS36, AS90, or POP18. We looked at both quadratures of POP90 before rotation and it seems to have both a phase shift and a 3.5 dB increase in the sum of I+Q. The RFmon and LO mon on the demod don't have any jumps nearly that large, so if it is a problem in the demod it is probably downstream of the directional coupler for the RFmon. 

This seems not to be the same as the jumps in SRC alingment that started after last tuesday's maintence, (31804 31865 and other alogs), but since the symptom is very similar it would make debugging the other problem easier if this issue could be fixed. Since we use POP90 for a dither lock of the SRM angle durring lock acquisition, this can cause a lockloss if it happens while we are trying to lock. 

Images attached to this report
Comments related to this report
peter.king@LIGO.ORG - 09:36, Friday 02 December 2016 (32094)
I tested the chassis that was pulled out (S1000977).  During the testing I did not see any level changes
or glitches in either the I or Q channel outputs, except when a pair of cables to attached to the front
panels via a BNC tee were strongly wiggled.  Removal of the tee and wiggling the cables directly didn't
induce any changes.  Attached is an oscilloscope trace of the I&Q monitor output for the POP90 channel.
It is fuzzy because of an RF amplitude modulation I was applying, however the distortion discontinuities
are present with the modulation off.

    Daniel pointed out to me that the distortion is due to my not looking at the signal
differentially on the oscilloscope.  Sure enough it looks a lot cleaner when processed differentially.
I did however notice that if the RF input is more than -11 dBm, the monitor signals on the rear panel are
saturated/distorted.

    The only other output level changed that was observed was when the chassis was turned off in the
evening and back on again the following morning.

    The chassis (strictly) failed the following tests:
 - front panel monitor coupling factors (all channels at 100 MHz, failed by less than 1 dB)
 - IF beat note amplitude versus frequency (all channels, I & Q, at 100 kHz, failed by as little as 50 mV
     and as much as 360 mV)
 - IF output noise level (channel 3, I & Q, failed by as little as 3 dB and as much as 4 dB).  Channel 3
     is labelled as REFLAIR_27.

    By any chance when the chassis was in the rack, was there more than one cable attached to the (one)
front panel BNC connector?
Images attached to this comment
H1 IOO
kiwamu.izumi@LIGO.ORG - posted 17:07, Monday 28 November 2016 - last comment - 00:48, Tuesday 29 November 2016(31935)
IMC recovery

Robert, Kiwamu,

This is a summary of the recovery of the IMC alignment after the PSL PZT mirror mount swap today (for which I think Robert will make a separate report).

Synopsis-

IMC seems to have shifted its waist location horizontally by 0.25 mm based on the change seen by the suspension witness sensors. This apparently was large enough to reduce the amount of light at IMC-TRANS by a factor of two presumably due to a worse in-vac clipping in HAM2. Nevertheless, as of now, we seem to be able to lock the interferometer on DC readout without new issues.

Recovery process-

We temporarily placed an iris after the top periscope mirror and before the beam tubing. After the swap, we checked two existing irises that had been on the table and the new one at the top of the periscope to coarsely recover the alignment. Then checking the spot on the PSL wall coming out from the light pipe between the PSL and HAM1, we did a fine alignment. This was good enough to put us back to a position where we see the main light on IMC REFL camera. A final alignment was then done by engaging IMC ASC which automatically servoed the alignment to an optimum. The temporary iris was removed before we left the PSL.

After the successful lock of IMC and successful engagement of IMC ASC, we noticed that the IMC TRANS is smaller by a factor of two. This seems to be due to a slight change in the horizontal direction in the uncontrolled degree of freedom. Here is a table listing several changes in some relevant sensors.

    before  after  diff
MC1 PIT witness  -3   -2  +1 urad
MC2 PIT witness   510  507  0
MC3 PIT witness   -841  -842  -1 urad
IM4 PIT  -0.33  -0.34  almost 0
       
MC1 YAW witness  -1035  -1043  -8 urad
MC2 YAW witness  -672  -672  0
MC3 YAW witness  -996  -987  +9 urad
IM4 YAW  0.25  -0.08  - 0.33 cnts
       

As shown above, the only appreciable change is that in DOF2 of IMC YAW (highlighted by red texts). Using Kawazoe's formula (P1000135), one can find that this amounts to a lateral shift of the spot position by 0.25 mm toward HAM3 or away from PSL. [EDIT] Keita pointed out that the direction of the move that I initially reported was wrong. So the correct statement is that the beam shifted by 0.25 mm toward the PSL or away from HAM3.
 

Things we didn't optimize-

Comments related to this report
kiwamu.izumi@LIGO.ORG - 17:41, Monday 28 November 2016 (31938)

Two addenda.

Firstly, to cope with the fact that IMC TRANS decreased by a factor of two, I have edited the IMC_LOCK guardian and lowered all the FM_TRIG_THRESH_ON and _OFF values by a factor of two. In addition, I manually changed the IMC-MCL_TRIG_THRESH_ON and _OFF values by a factor of two as well. They don't seem to under control of any guardians. IMC locks fine with these new settings. The guardian is then checked into SVN.

Secondly, the spot positions on the PSL wall seem to have shifted by 1-2 mm towards the West. No obvious change was found in the vertical direction. See the attached picture. The new positions are recorded with black 'X' marks as shown in the picture.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 00:48, Tuesday 29 November 2016 (31951)

Jenne and I did a repeat of what we tried a few weeks ago after different PSL work: (30918) we restored the optics to their old values using the witness sensors, then moved the piezo to maximize build up without turning on the IMC WFS. This brought the spot back to its before position on IM4 trans, although the MC2 trans sum was low, so we think that as expected only the input beam has moved, not the mode cleaner optics or IMs.  However, we can't fix the input beam change simply by moving the PZT. 

We let the MCWFS run to increase the mode cleaner transmission, and watched the spots on both the ISS QPD and IM4 trans.  We walked IM3 and IM2 in yaw to bring both QPDs back to the spot positions before this morning's PSL work, and now Cheryl is doing inital alingment. 

To move this degree of freedom,  we moved IM2 1.284 urad in yaw for every urad that we moved IM3.  Since this is a degree of freedom that our inital alingment and ASC don't control, it may be a good idea to try moving this degree of freedom in full lock to see what impact it has on our noise and recycling gain. For the record, today we moved IM3 -2390 urad, and IM2 -3030 urad. 

H1 AOS (DetChar)
jason.oberling@LIGO.ORG - posted 11:39, Monday 28 November 2016 - last comment - 09:48, Tuesday 29 November 2016(31909)
End Station OpLev Glitching (WP 6348)

Following up on the DetChar report of ETMx oplev laser glitching causing problems, I confirmed (using the DetChar summary pages) that the laser was indeed showing signs of glitching.  I also noticed the ETMy laser was also showing signs of glitching.  I increased the power for both lasers to hopefully get them into a thermal state they are happy with.  I used the Current Monitor (outputs a voltage to monitor the current delivered to the laser diode) port on the back of each laser as a guide.  The changes were:

Seeing as I had to open the cooler for both lasers they will both need 4-6 hours to return to thermal equilibrium.  At that point a determination can be made as to whether or not this helped at all.  The attached 3 hour trend of the oplev SUM for both optical levers gives hope; after the power increase the SUM signal is quieter for both oplevs.  I will leave WP 6348 open for now as more adjustment may be necessary to fix the glitching.

Images attached to this report
Comments related to this report
jason.oberling@LIGO.ORG - 09:48, Tuesday 29 November 2016 (31961)DetChar

Further power adjustment for both lasers this morning as both were still showing signs of glitching (better than yesterday morning, but not gone).  Changes are:

  • ETMx
    • Current Monitor Before: 0.830 V
    • Current Monitor After: 0.845 V
  • ETMy
    • Current Monitor Before: 0.880 V
    • Current Monitor After: 0.897 V

As before these lasers will need ~4 hours to return to thermal equillibrium before I can assess whether or not this latest tweak helped.

H1 ISC (OpsInfo)
sheila.dwyer@LIGO.ORG - posted 19:33, Wednesday 23 November 2016 - last comment - 20:43, Monday 28 November 2016(31804)
Sudden alignment shift this morning

Keita, Sheila

At 11 am pacific time (19:00 UTC Nov 22nd), there was a sudden shift in alignment in the SRC that caused bad noise in DARM. The first attached screenshot shows the noise in DARM changing.

At this time, there is a shift in the alingment of SRM and SR2 in both pit and yaw, and other interferometer optics don't move significantly.  The OMs and OMC suspensions move as well, but that appears to be a result of the feedback. There is also an increase in POP90, a small drop in AS_A DC, and a small increase in AS90.  The signals on all 4 quadrants of ASA36 I change (the in loop signal, where we are using a funny matrix to take care of an offset).  On AS36 B, we see pitch signals, but not much signal in yaw. Also, the RF levels on all quadrants of AS36 WFS change by 5 to 8dB, which could be the result of the alignment shift.  

We looked at conlog for any changes at the time, there were only PI settings changing, we don't think there was anyone in the LVEA or CER at the time.  

The most obvious sign for an operator that this has happened would be that POP90 jumps suddenly in the middle of a lock stretch.  If this happens again, people could (go out of observe) open the SRC1 ASC loops by ramping the gains to zero, then try moving SRM to bring POP90 back to a normal level.  

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 20:22, Wednesday 23 November 2016 (31806)OpsInfo

Do we get to see POP90 when the Beam Diverters are closed?

sheila.dwyer@LIGO.ORG - 20:43, Monday 28 November 2016 (31947)

When the POP beam diverter is closed we won't see POP90.  

Displaying reports 53701-53720 of 84797.Go to page Start 2682 2683 2684 2685 2686 2687 2688 2689 2690 End