Displaying reports 61741-61760 of 85666.Go to page Start 3084 3085 3086 3087 3088 3089 3090 3091 3092 End
Reports until 11:23, Wednesday 30 December 2015
H1 DetChar (DetChar, ISC)
gabriele.vajente@LIGO.ORG - posted 11:23, Wednesday 30 December 2015 (24566)
Range variations over the last days

Triggered by Jeff and the quite large variation of the range, I tried to see if there was any correlation with beam motion, especially as sensed by the TRANSMON QPD.

The plot attached shows the variation of the BNS range over the last week, togeher with the best fit obtained with a linear combination of the 8 TRANS QPD signals (X/Y, A/B, PIT/YAW). 

The reconstruction is not paritcularly good, but my feeling is that there might be something interesting here. It's likely that at least some part of the range variation can still be caused by a slighly different alignment state of the IFO.

Images attached to this report
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 09:48, Wednesday 30 December 2015 (24564)
CDS model restart report Tuesday 29th December 2015

O1 day 103

model restarts logged for Tue 29/Dec/2015 'Maintenance-lite' day, no restarts reported

LHO General
corey.gray@LIGO.ORG - posted 08:15, Wednesday 30 December 2015 - last comment - 09:57, Wednesday 30 December 2015(24561)
Transition to DAY Shift Update

TITLE:  12/30 DAY Shift:  16:00-00:00UTC (08:00-04:00PDT), all times posted in UTC     

STATE of H1:   NLN at a solid 80Mpc

Outgoing Operator:  Ed

Quick Summary:

I talked to Ed while driving in to get the low-down of his shift.  Sounds like he had some issues with various things (i.e. ALS alignment, no Dark Michelson [known], OMC troubles @ DC READOUT, etc.)---making me scared of a lockloss!  At any rate, smooth sailing now with LVEA useism at 0.38um/s & minimal winds.

RED Timing error for H1OAF on CDS Overview.  I can not remember if hitting "DIAG RESET" will drop us out of Observing, so I will hold off on hitting that button (but will send an email to Dave/Jim).

Comments related to this report
david.barker@LIGO.ORG - 09:06, Wednesday 30 December 2015 (24563)

The h1oaf model's cpu max is 63uS which is right at the alarm level. It would be best to keep checking it does not go above 63 while in observing mode and perform at DIAG_RESET next time we are out of observing.

corey.gray@LIGO.ORG - 09:57, Wednesday 30 December 2015 (24565)

Will hold off on hitting the DIAG RESET button for h1oaf (since we're not 100% hitting DIAG RESET buttons drop us out of Observing.  Do not think it's been tested and haven't seen anything in the alog).  Dave says we should keep an eye on this though.  He would be worried if it was in the high 60s.  Looking at last 60days, this is the highest it has gotten though (see attached plot).

NOTE:  Would be nice to test whether we can hit this button and STAY in Observing at some point.

Non-image files attached to this comment
H1 General
edmond.merilh@LIGO.ORG - posted 07:55, Wednesday 30 December 2015 (24560)
Shift Summary - OWL

TITLE: Dec 30 OWL Shift 08:00-16:00UTC (00:00-08:00 PDT), all times posted in UTC

STATE Of H1: Observing

SUPPORT: Kiwamu

INCOMING OPERATOR: Corey

SHIFT SUMMARY: IFO locked at 80-83Mpc. All the action was in my last log. Winds calm. EQ seismic bands nominal. µSei is below the 90th percentile mark. Looking good to hand off to Corey.

H1 General
edmond.merilh@LIGO.ORG - posted 05:20, Wednesday 30 December 2015 (24559)
H1 Locked at Nominal Low Noise - Observation Intent Bit set

80Mpc

13:20UTC

H1 General
edmond.merilh@LIGO.ORG - posted 04:52, Wednesday 30 December 2015 (24558)
Mid-Shift Summary - OWL

Mid-SHIFT SUMMARY: No locking since the beginning of my shift. For having nothing  tripped after the Victoria quake which barely showed us anything on the eq bands, I had a heck of a time with optics that needed to be trended and re-aligned. Y-Arm gave me a ton of grief and then I re-visited PRM. SRC was a mess but I moved on to locking PRMI so that I could get the alignment there maximized. I then had to revisit IA to re-align  SRM and SR2 by hand so that I could move on to DRMI. IFO was locked at DC_READOUT_TRANSITION for over an hour and OMC wouldn’t engage and lock so I spent ≈ 1 hr on the phone with Kiwamu until the lock was lost. Since then locking has been less than successful despite good alignment (in my opinion). There was a small earthquake that gave me a little grief. The struggle continues. If I achieve the level of lock that I had before, I only hope that the OMC behaves as it should at that point. Fingers crossed.

H1 General
edmond.merilh@LIGO.ORG - posted 00:14, Wednesday 30 December 2015 (24557)
Shift Summary - OWL Transition

TITLE: Dec 30 OWL Shift 08:00-16:00UTC (00:00-08:00 PDT), all times posted in UTC

STATE Of H1: Locking

OUTGOING OPERATOR: Jeff

QUICK SUMMARY: Recovering after Canadian quake.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:04, Wednesday 30 December 2015 (24556)
Ops Evening Shift Summary
Activity Log: All Times in UTC (PT)

00:00 (16:00) Take over from Corey
03:09 (19:09) Restarted VerbalAlarm 
07:40 (23:40) Lockloss – Possible EQ in Victoria, CA.
End of Shift Summary:

Title: 12/29/2015, Evening Shift 00:00 – 08:00 (16:00 – 00:00) All times in UTC (PT)

Support:  Kiwamu, Mike L.
 
Incoming Operator: Ed

Shift Detail Summary: Good Observing shift until 07:40 (23:40) when lost lock possibly due to EQ in Victoria, CA. Started relocking when Ed came on shift.  

H1 General
jeffrey.bartlett@LIGO.ORG - posted 20:05, Tuesday 29 December 2015 (24555)
Ops Evening Mid-Shift Summary
   In general a good first half of the shift. IFO status and environmental conditions remain as they were at the start of the shift. There were a couple of EQs that passed without any apparent issues. 

   VerbalAlarms stopped working around the start of the shift (00:00 (16:00)). I restarted it (at 03:09 (19:29)) and notified the support group.  
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:28, Tuesday 29 December 2015 (24553)
Ops Evening Shift Transition
     Transition Summary:
Title:  12/29/2015, Evening Shift 00:00 – 08:00 (16:00 – 00:00) All times in UTC (PT)
	
State of H1: 00:00 (16:00), The IFO has been in Observing mode for the past 3.5 hours, with power currently at 21.8W, and range at 80Mpc.  Environmental conditions are good. The wind is up to a light breeze (2- 7mph). Seismic is flat at approximately 0.03um/s; microseism is also flat and centered around 0.3um/s.      

Outgoing Operator: Corey
H1 General
sheila.dwyer@LIGO.ORG - posted 16:16, Tuesday 29 December 2015 (24552)
modified range integrand FOM

Jeff, Sheila

We updated the Range integrand FOM, updating the reference which has been out of date for a while, and changed the scale.  

LHO General
corey.gray@LIGO.ORG - posted 16:09, Tuesday 29 December 2015 (24542)
DAY Ops Summary

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

STATE of H1:   NLN for 3+hrs at 80Mpc

Incoming Operator:  Jeff B.

Support:  Kissel on-site fellow, Sheila (Locking Commissioner)

Quick Summary:

Fairly light Maintenance Day (which occurred only because H1 dropped out of lock).  Current lock looks noticeably less ratty (why??).

Shift Activities:

LHO FMCS
john.worden@LIGO.ORG - posted 14:50, Tuesday 29 December 2015 (24551)
LVEA Temperature control

LVEA is still too warm and not under control. So I have set HC3B to off (4ma).

Images attached to this report
H1 General (OpsInfo)
corey.gray@LIGO.ORG - posted 13:13, Tuesday 29 December 2015 (24549)
Maintenance Mid Shift Summary: H1 Out ~3hrs

Maintenance Summary:  17:45 Lockloss -->  20:49 Undisturbed

Not clear why we had the lockloss (LN2 truck came 30min after lockloss).

17:47 - 18:53:  Charge measurement, PSL WD Reset, LN2 at MY CP3

18:53 - 19:31: Initial Alignment.  Here are two notable:

  1. ALS Alignment:  After GREEN WFS OFFLOAD, ETMy had output of 39 in yaw, so I tweaked ETMy yaw to get it down to 4 (is that worth doing?).  Also tweaked PR3 to take COMM Beatnote from 3.8 to 4.8.
  2. Dark Michelson:  This was straightforward, EXCEPT for not being able to lock a Dark Michelson.  After tweaking BS & also SR2 (while looking at AS_C QPD) to no avail, restored those optics and moved on.  

19:32 - 20:34:  Lock Acquisition.  Notes below:

Since I didn't get to align BS in MICH_DARK_LOCK, I selected LOCK_PRMI in ISC_LOCK guardian, but this apparently doesn't work.  Sheila mentioned I should have selected PRMI_LOCKED instead.  Sheila looked into making the guardian script handle what I did better, but DRMI eventually locked on its own!  SOOOOO, I did NOT get to touch the alignment of the BS during Initial Alignment or PRMI.  

For DC READOUT (or around there), we received a "Wrong Mode" message.  It eventually went away on its own, but will need to figure out what an Operator should do if this message holds us up in the future.

20:41 - 20:48:  Ran A2L (per Tues Regular Mainteance) & it took ~7min.

LHO VE
kyle.ryan@LIGO.ORG - posted 12:38, Tuesday 29 December 2015 (24548)
Daily manual over fill of CP3
~1205 hrs. local 

Performed the daily manual overfill of CP3 (minutes after NORCO truck left site following LN2 delivery to CP3's dewar) -> Dewar vapor pressure ("head" pressure) after NORCO delivery has remained near nominal value of ~15 - 18 psi. -> CP3 exhaust line was exhausting GN2 when I arrived as if delivery (increase in LN2 column height in dewar) hadn't resulted in an over fill on its own though the exhaust line pressure was elevated when I arrived (1.5 psi) -> I reviewed the response of the LLCV %open from the previous NORCO delivery and have decided to leave the current manual %open value of 15% as is for now -> I may come in tonight to verify that CP3 isn't over filling on its own and adjust the manual LLCV %open value if needed.
H1 CAL (SUS, SYS)
jeffrey.kissel@LIGO.ORG - posted 12:05, Tuesday 29 December 2015 (24547)
Charge Measurement Update; We Can Make It To the End of the Run; When Should We Make a Change?
J. Kissel,

With only one more week to go on O1 "proper," (see JRPC Wiki), I think we've made the right gamble on not flipping the bias sign (as decided in the last two weeks, see LHO aLOG 24241, and 24383) -- the acceleration of the H1 SUS ETMY ESD's relative actuation strength accumulation in longitudinal is sufficiently negative that we will stay under the desired 10% systematic error in the calibration for at least another week or two (without correcting for the change, which we will do in the future). As usual, H1 SUS ETMX, (though inconsequential) shows a completely tolerable level of charge, and hasn't really moved since we've begun turning OFF the EX ESD Bias Voltage when its not needed. See attached trend plots. 

The new question is now "when and in what order do we make changes to the DARM loop?" We know we want to do the following (see G1501372):
    - Clean up the QUAD's longitudinal hierarchical control filters -- converting them all the distributed, and then chosing a better frequency distribution such that we don't need nearly as many violin mode notches, and which ever we do need don't impact the shpae of the over-all super actuator. 
    - Jack up the boost on the DARM filter to get more low frequency suppression.
    - Reduce the EY Bias Voltage by 2 to reduce the rate of charge accumulation.
    - Flip the EY Bias to reduce whatever chare has accumulated over the course of the run, such that we hit zero at the start of O2 and stay there.
    - (maybe move to a true DARM drive?)
Each of these tasks, once complete, will require a re-assessment of how close we are to saturations at each isolation stage. Further we should be sure to perform these changes slowly and methodically such that we understand the impact at every step and ensure that we retain IFO robustness (and *maybe* try to keep the DARM loop model and calibration up to date, if it's not too arduous). Part of slow and methodical is asking in what order we perform the above steps, and how much time should we use to reassess robustness in betweeen each step. Given that O2 prep is slated to begin mid-July (see G1501561), I think we can do these 4 (or 5) tasks over the course of a month and still have plenty of time to assess robustness. Further, since 
    - it's unclear how much up-time we'll have during the commissioning period to measure the longitudinal strength change via PCAL, 
    - there are also plans to make changes to the tracking of longitudinal actuation strength (see, e.g., Integration Issues 1138, 1170, and 1155)
    - making changes to the DARM loop as described above will mean that we'll need to get a new DARM model up and running before valid kappa's can be produced
I suggest we continue to make these charge measurements once a week throughout the commissioning period. Though we've (sadly) shown that the optica lever charge assessments are not exactly proportional to the longitudinal assessments from PCAL, the assessment is still close enough that it'll do.
Images attached to this report
Non-image files attached to this report
H1 OpsInfo
sheila.dwyer@LIGO.ORG - posted 11:49, Monday 07 December 2015 - last comment - 18:27, Tuesday 29 December 2015(24031)
PRMI to DRMI transitions

My previous entry about the PRMI branch in the ISC_LOCK guardian isn't as clear as it could be, so here is a newer version.

If you find that DRMI won't lock and seems to be missalinged (you see a lot of higher order modes on the AS camera, POP90 and POP18 flashes are low) you may want to lock PRMI to adjust alignment manually:

  1. with ISC_LOCK in the state LOCK_DRMI_1F (or any earlier states), request LOCK_PRMI
  2. Once PRMI is locked, manually adjust the alignment of BS and PRM to increase the POP18 and POP90 buildups. (POP18_I_NORM_MON around 50 counts and POP90_I_NORM_MON around 80 counts, should be stable).
  3. Once you are happy with the buildups, request DRMI_LOCKED.  Either it will smoothly make the transition or it will break the PRMI lock and go back to trying to lock DRMI. 

The transition from PRMI to DRMI only works sometimes, so this is probably best used only when the alignment is bad for now.  (Its not a reliable way to speed up DRMI locking).

Comments related to this report
sheila.dwyer@LIGO.ORG - 13:14, Tuesday 29 December 2015 (24550)OpsInfo

The above instructions have changed, only in that the name of the state to request is now PRMI_LOCKED:

If you find that DRMI won't lock and seems to be missalinged (you see a lot of higher order modes on the AS camera, POP90 and POP18 flashes are low) you may want to lock PRMI to adjust alignment manually:

  1. with ISC_LOCK in the state LOCK_DRMI_1F (or any earlier states), request PRMI_LOCKED
  2. Once PRMI is locked, manually adjust the alignment of BS and PRM to increase the POP18 and POP90 buildups. (POP18_I_NORM_MON around 50 counts and POP90_I_NORM_MON around 80 counts, should be stable).
  3. Once you are happy with the buildups, request DRMI_LOCKED.  Either it will smoothly make the transition or it will break the PRMI lock and go back to trying to lock DRMI. 

The transition from PRMI to DRMI only works sometimes, so this is probably best used only when the alignment is bad for now.  (Its not a reliable way to speed up DRMI locking).

edmond.merilh@LIGO.ORG - 18:27, Tuesday 29 December 2015 (24554)
I'll check the wiki against these new instructions.
Displaying reports 61741-61760 of 85666.Go to page Start 3084 3085 3086 3087 3088 3089 3090 3091 3092 End