Displaying reports 59961-59980 of 83146.Go to page Start 2995 2996 2997 2998 2999 3000 3001 3002 3003 End
Reports until 17:41, Sunday 29 November 2015
H1 General
patrick.thomas@LIGO.ORG - posted 17:41, Sunday 29 November 2015 - last comment - 22:02, Sunday 29 November 2015(23812)
Observing
Kiwamu, Patrick

Switching the ISI blends to 45 mHz made all the difference. Accepted the SDF differences for the blends. (See attached screenshots). No problems as soon as we did that.

There is a yellow box with 'TPD' written in it flashing in the PSL area of the Ops overview. Kiwamu looked at the medm code and it appears when H1:PSL-FSS_TPD_DC_OUTPUT < 0.9. It is currently around 0.86.

There is still a testpoint open on H1LSC.
Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 22:02, Sunday 29 November 2015 (23815)

Good job, you guys!!  (And looks like you might have been up to 85Mpc for the first few hours?!  Wow.)

LHO General
patrick.thomas@LIGO.ORG - posted 16:11, Sunday 29 November 2015 (23811)
Ops DAY Beginning Shift Summary
TITLE: 11/29 [EVE Shift]: 00:00-08:00 UTC (16:00-00:00 PDT), all times posted in UTC

STATE Of H1: Lock acquisition
OUTGOING OPERATOR: Corey
QUICK SUMMARY: Kiwamu is here and has been working with Corey to help try to relock.
From the cameras:
The lights are off in the LVEA.
The lights are off in the PSL enclosure.
I can not tell if the lights are on or off at mid X and mid Y.
The lights are off at end X.
The lights are off at end Y.

The 0.03 - 0.1 Hz (earthquake) seismic band is between ~ 0.02 and 0.1 um/s.
The 0.1 - 0.3 Hz (microseism) seismic band is between ~ 0.2 and 0.8 um/s.

The winds are between ~ 0 and 5 mph.

The ISI blends are on Quite_90.

From pinging:
CDS WAP is off at the LVEA.
CDS WAP is on at mid X.
CDS WAP is on at mid Y.
CDS WAP is off at end X.
CDS WAP is off at end Y.
LHO General
corey.gray@LIGO.ORG - posted 15:58, Sunday 29 November 2015 (23810)
DAY Ops Summary

TITLE:  11/29 DAY Shift:  16:00-00:00UTC (08:00-16:00PDT), all times posted in UTC     

STATE of H1:  Lock Acquisition

Incoming Operator:  Patrick 

Support:  Kiwamu over the phone and then

Quick Summary:

  Rough shift which hopefully just related to issues with alignment (i.e. input pointing restoration?).  Right now we are waiting to see how H1 proceeds through lock aquisition.  Kiwamu has been here to help & is here to assist Patrick.

Shift Log:

H1 IOO
corey.gray@LIGO.ORG - posted 15:34, Sunday 29 November 2015 (23809)
Input Alignment Pointing Changes

Attached is a plot of the last 24hrs covering restoration attempts for the Input Alignment.  Additionally there is a plot also looking at the last 30days.

Non-image files attached to this report
H1 General
corey.gray@LIGO.ORG - posted 11:23, Sunday 29 November 2015 - last comment - 12:38, Sunday 29 November 2015(23805)
H1 Update

A bit of a frustrating morning.

Since Alignment was decent enough to get through DRMI, I opted to look at Input Alignment again.  Patrick pretty much restored the IM4 Trans Pit/Yaw to where they should be (good thing!).  I thought the yaw could be moved a little more though.  I decided to move the IM3 in yaw a bit.  (Talked with Kiwamu and he felt this was good to try).

Since the input pointing was changed, I then started an Initial Alignment.  Unfortunately, I ran into issues at the beginning with ALS.  I could have sworn both ALSx & y were fine at first, but after waiting a few minutes for control signals to converge, I noticed ALSy was in a completely bad alignment state.  I spent way too much time trying to get an alignment back, could never get much above 0.5 & when I did WFS drove the alignment off.  After talking with Kiwamu, he suggested taking guardian to LOCKED NO SLOW NO WFS & tweak on ITMy & ITMy.  Finally, made some progress here and took the arms up to 1.05, went to INITIAL ALIGNMENT (which enables wfs), and Y-arm looked great....

...but then ALSx all of a sudden looked ugly.  It had a 0:0 mode, but it's power was oscillating from 0.4 -0.8 with a period of 6-7sec.  (on the Tidal strip tool, the ALS x & y REFL control signals are oscillating with this period.  useism doesn't look bad (under 90 percentile & there's no wind).  Asked whether the tidal issues Patrick had last night could be an issue here, but since we aren't fully locked it should not.  So moving on...

Oh, and within a few minutes, I lost ALSy again!!

SO:  Going to work on ALSx & then ALSy (probably with no WFS).  Kiwamu said another knob I can use is the ALS WFS GAIN for each arm, if needed.

OK, back at it.

Comments related to this report
corey.gray@LIGO.ORG - 11:31, Sunday 29 November 2015 (23806)

Just further notes.  I initially did move TMS when working on the Yarm, but then I returned it to its OSEM values.  BUT, after tweaking only the ITMy & ETMy, I see that the TMS OSEM values have drifted a bit.  Maybe this is standard, but I was surprised at that.

patrick.thomas@LIGO.ORG - 12:31, Sunday 29 November 2015 (23807)
I've also had the same kind of issues trying to lock ALS recently.
corey.gray@LIGO.ORG - 12:38, Sunday 29 November 2015 (23808)

Hey Patrick!  Sorry, I've not been able to recover what you did last night.  Well, Kiwamu will be on site in a bit---I was just wanting to figure this out!  :-/

Other ALS notes:

  • Since X-arm ALS looked ugly even with WFS (seeing 0.15Hz oscillation), I enabled the 45mHz blends for the Xarm.  This had no effect
  • I tried adjusting ALS WFS gain from 0.5.  Went up and down, but this also had no effect.

At this point now, the ALS spot is really ugly (and this is after returning sliders to original values 

Oh, and another odd effect is how AS AIR video looks.  there's a couple of spots which look like they are rotating through every few seconds (I've not seen that before).  

H1 General
corey.gray@LIGO.ORG - posted 06:47, Sunday 29 November 2015 - last comment - 08:15, Sunday 29 November 2015(23802)
Update Status

Had a sick OWL shift operator last night.  Although Nutsinee offered to accept a call to come in to cover the shift last minute, Mike & I opted to not call someone in at short notice with freezing condition.  At the time, H1 was in the middle of a long lock, but unfortunately H1 dropped out of lock before midnight.  Patrick fought valiantly and stayed a bit beyond his shift (see his alogs for the play-by-play); I talked with him before going to bed & opted it would be better to get sleep before coming in early.  

Walked in at 14:35UTC (6:35am), to H1 trying to lock DRMI, and it did within a few minutes.  Right now it is stuck trying to go to REDUCE CARM OFFSET, but there is a Guardian message of:  NO IR in arms!!

Comments related to this report
corey.gray@LIGO.ORG - 07:19, Sunday 29 November 2015 (23803)

Was able to get past the "NO IR in ARMS" issue, by taking ISC_LOCK to MANUAL, selecting PREP_TR_CARM, but only made a few steps afteward.

Alignment is looking decent.  Made it all the way to RF DARM (no issues with IR for whatever reason), but it dropped attempting DARM WFS.  

Went to LOCK PRMI at 15:07, and it successfullly locked within 3min, but it looked good (POP 18 & 90 were both over 150).   Now waiting for DRMI.

corey.gray@LIGO.ORG - 08:15, Sunday 29 November 2015 (23804)

Current Alignment seems ok since we are making it past DRMI.  Since we are dropping out during steps after DRMI, I'm considering continuing an Input Alignment change (investigating now using the IM Recovery procedure).  If I need to make a change, I will then need to run another Initial Alignment, and then try locking again.  

I'm leaning toward Input Alignment, if I still have trouble after that, I will give Kiwamu a call (already sent him an email giving him a heads up of where I'm at thus far).

LHO General
patrick.thomas@LIGO.ORG - posted 01:40, Sunday 29 November 2015 (23801)
Setting request to NLN and going home


			
			
H1 General
patrick.thomas@LIGO.ORG - posted 00:08, Sunday 29 November 2015 - last comment - 01:30, Sunday 29 November 2015(23791)
Current State
I believe I have moved IM1 and IM2 to there approximate positions before the HAM2 ISI trip (alog 23777). I moved IM1 in PITCH from 800 to 592. I moved IM2 in PITCH from 17980 to 17232.

I started an initial alignment. I got to the point where both ALS_XARM and ALS_YARM were at the INITIAL_ALIGNMENT state and was waiting for the ASC convergence. However when I got to GREEN_WFS_OFFLOADED the Y arm dropped in power. I am now struggling to bring it back.
Comments related to this report
patrick.thomas@LIGO.ORG - 00:10, Sunday 29 November 2015 (23792)
And of course we just had a GRB alert.
patrick.thomas@LIGO.ORG - 00:31, Sunday 29 November 2015 (23793)
Got back to GREEN_WFS_UNLOADED. This time the power stayed high in both arms.
patrick.thomas@LIGO.ORG - 00:52, Sunday 29 November 2015 (23794)
Trying to lock X arm on IR for INPUT_ALIGN. Put IM1 and IM2 back.
patrick.thomas@LIGO.ORG - 00:53, Sunday 29 November 2015 (23795)
Got to INPUT_ALIGN.
patrick.thomas@LIGO.ORG - 00:58, Sunday 29 November 2015 (23796)
Moved IM1 in PITCH from 800 to 592 and moved IM2 in PITCH from 17980 to 17232 again. IR in x arm dropped briefly but then recovered.
patrick.thomas@LIGO.ORG - 01:12, Sunday 29 November 2015 (23797)
Got to SRC_ALIGN. Had to move SRM by hand.
patrick.thomas@LIGO.ORG - 01:16, Sunday 29 November 2015 (23798)
Finished initial alignment.
patrick.thomas@LIGO.ORG - 01:29, Sunday 29 November 2015 (23799)
DRMI locked!
patrick.thomas@LIGO.ORG - 01:30, Sunday 29 November 2015 (23800)
Lost lock on DRMI locked.
Displaying reports 59961-59980 of 83146.Go to page Start 2995 2996 2997 2998 2999 3000 3001 3002 3003 End