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

STATE of H1:   Locked for last 10+hrs at 80Mpc

Incoming Operator:   Jeff B.

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

Quick Summary:

Fairly quiet shift for H1.  Environment is somewhat quiet with LVEA useism at 0.4um/s & winds under 10mph.  

Thomas noticed the EX HEPI Pressure flashed a few times on OPS_Overview (but trends didn't show much).  

EX (& MX) Camera is noisy (think this is a known issue).

Shift Activities:

• ETMy Saturations:  18:34, 19:11, 19:47, 21:16, 21:20
• Flurry of injection Verbal Alarms (What 
• 22:27 GRB (LLO contacted)
• 22:59 GRB (LLO contacted)
• 23:05 - 23:26 CP3 Overfill at MY (Gerardo)

After notifying the operator I drove past CS @ 23:06 and arrived at Y-Mid station @ 23:11.
Started filling CP3 @ 23:14, opened the exhaust check valve bypass valve, then opened LLCV bypass valve 1/2 turn, closed the flow 90 seconds later.  6 minutes later I closed the exhaust check valve bypass valve.

Started driving back from Y-Mid @ 23:21, arrived at the CS @ 23:27.

This is a report on comparing two most recent DARMOLGTF and PCAL2DARMTF measurements taken on December 1st (LHO alog 23883) and December 21st (LHO alog 24363) against earlier measurements during ER8/O1.

Kappa values used in the κ_tst and κ_C corrected parameter file for Dec 01, H1DARMparams_1133051601_kappa_corr.m are

% An hour average (30 minutes) kappas starting at GPS time 1133053680
par.kappa_tst = 1.040826;
par.kappa_pu = 1.023252;
par.kappa_A = 1.027452;
par.kappa_C = 0.986240;
par.fc = 334.808296; % [Hz]

Kappa values used in the κ_tst and κ_C corrected parameter file for Dec 21, H1DARMparams_1133051601_kappa_corr.m are

% An hour average (59 minutes) kappas starting at GPS time 1134764580
par.kappa_tst = 1.051995;
par.kappa_pu = 1.022335;
par.kappa_A = 1.037174;
par.kappa_C = 0.990362;
par.fc = 335.746785; % [Hz]

The comparison showed that actuation function residuals mostly remain under about +/- 1% in band [30 .. 500] Hz; sensing function redisuals are under +/- 1% upto 1 kHz.

The parameter files for these measurements were committed to CalSVN at

/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1133051601.m
/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1133051601_kappa_corr.m
/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1133051601_kappa_corr_full.m
/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1134769815.m
/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1134769815_kappa_corr.m
/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/H1DARMparams_1134769815_kappa_corr_full.m

The comparison script and plots were committed to SVN at (r2067)

/trunk/Runs/O1/H1/Scripts/DARMOLGTFs/CompareDARMOLGTFs_O1.m
/trunk/Runs/O1/H1/Results/DARMOLGTFs/2015-12-21_H1DARM_O1_cmp_*.pdf

Have received quite a few Injection Verbal Alarms over the last few minutes this morning for CW & TRANS (see attached snapshot).  Do operators need to do anything about this?  I talked with Tom E (L1 Operator) & they did not receive any alarms regarding these injections.

I brought up the CAL_INJ_CONTROL medm and looked at the Continuous Signal section of this window and have not seen anything change (and trended channels for CW and also don't see anything out of the ordinary).

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.

O1 day 103

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

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).

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.

80Mpc

13:20UTC

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.

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.

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.  

   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.  

     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

Jeff, Sheila

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

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:

• ETMy Saturations:  17:13, 22:48
• MAINTENANCE ITEMS:
  • Per Ops Checksheet Tues Activity:  Checked that HEPI WD Counters were all zero (no need to clear)
  • 16:35-16:50 Bubba dropping off snow blower (out at woodshop building)
  • 17:00 GRB Test acknowledged.  This is the only 
  • 17:47-18:52utc:  Kissel performing Charge Measurement (~1hr)
  • 17:53-17:57utc:  Gray Reset PSL Watchdog at 17:55 (~5min)
  • 18:15- ~20:00 LN2 truck on-site (MY CP3)
  • 18:35-18:41 VPW Water heater check (Bubba)
  • 18:56 US Linen delivery (30-60min)
  • NO LVEA SWEEP was performed since there were no VEA entrances
• 17:45 H1Lockloss!
• 18:53-19:31 Initial Alignment
• 19:57-20:25 Kyle heading to MY (offsite at 20:48)
• 20:49 Undisturbed

We've been cleaning up the scripts used to present the various calibration measurements against the model and each other.

A longer description of script locations and cleanup is LLO alog 23558.

This is basically the same as  LHO alog 21280, except comparing against the O1 model (H1DARMparams_1124827626.m) and trying to use more generic scripts for both sites.

The attached pdfs are results, and can also be found in the aligo calibration svn under:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Results/

The first 3 all measurement types (Free swinging Michelson, ALS DIFF, PCAL) from 3 different days plotted against each other and the O1 model.

The second set of 3 are just the PCAL measurements against the model.

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).