After a week's worth of struggle with the h1oaf computer, and alignment loop instabilities, we've been blessed with another 16 hour lock stretch. As such, we've got sufficient amount of data for the roaming calibration line to move it from 4001.3 Hz to 4301.3 Hz. 

Though the line has been at 4001.3 Hz for 5 days, I recommend only using data from the two long lock stretches in that time from Nov 12 2016 05:00:00 UTC to Nov 12 2016 21:00:00 UTC and Nov 16 2016 06:00:00 UTC to Nov 16 2016 22:00:00 UTC. However, note that the mean laser power is different from the one lock stretch to another -- 29.5 [W] for the Nov 12 stretch, and 31.1 [W] for the Nov 16th stretch.

Current Schedule Status:
Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC                                  
4501.3       40k                      10:00
4801.3       40k                      10:00  
5001.3       40k                      10:00

Began replacing the Anemometers on the weather stations.  Taking longer than anticipated as the stations are not in the same orientation as they were pre roofing.
The corner station is done and EndX is complete.  I had to rotate the mounting hardware so the Anemometer could point in the proper direction for 0deg.
Everything seems to be functioning.  This may also explain the complaints about the wind direction being broken in previous posts.

Here's a BruCo scan for last night lock:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_lho_1163325617/

Focusing on the band between 20 and 50 Hz, there isn't any large coherence. However:

• angular controls show a bit of coherence (MICH_Y and CHADR_Y).
• there is coherence with the input beam control (INP1_Y) which also shows up with the ISS second loop QPD
• SRCL is still the largest longitudinal control, but coherence isn't very high.

I've added a Weeklies screen to the Sitemap to make it easier for the operators to do FAMIS tasks. It can be found under the OPS tab. Pretty simple, there are a number of buttons that launch different scripts for different FAMIS tasks, so operators don't have to navigate from the command line. Operators and detector engineers should feel free to add tasks to this screen, I added the ones I could think of. Hopefully we can rely on this screen to make sure that operators use 1 version of a script, and give cognizant engineers some control over which version is used.

I also encourage anyone with any artistic inclinations to make it look nicer. I got nothin'.

model restarts logged for Tue 15/Nov/2016
2016_11_15 10:06 h1fw0
2016_11_15 11:45 h1susauxb123
2016_11_15 12:13 h1broadcast0
2016_11_15 12:13 h1dc0
2016_11_15 12:13 h1fw0
2016_11_15 12:13 h1fw1
2016_11_15 12:13 h1fw2
2016_11_15 12:13 h1nds0
2016_11_15 12:13 h1nds1
2016_11_15 12:13 h1tw1

Maintenance day. new frame-cpp version on fw0, new auxb123 model, daq restart.

model restarts logged for Mon 14/Nov/2016 - Thu 10/Nov/2016

Many h1oaf0 model restarts. Please see attached log text files for details.

model restarts logged for Wed 09/Nov/2016 No restarts reported

model restarts logged for Tue 08/Nov/2016
2016_11_08 08:24 h1iopoaf0
2016_11_08 08:24 h1oaf
2016_11_08 08:24 h1odcmaster
2016_11_08 08:24 h1pemcs
2016_11_08 08:24 h1tcscs
2016_11_08 08:25 h1calcs
2016_11_08 08:25 h1iopoaf0
2016_11_08 08:25 h1ngn
2016_11_08 08:25 h1oaf
2016_11_08 08:25 h1odcmaster
2016_11_08 08:25 h1pemcs
2016_11_08 08:25 h1susprocpi
2016_11_08 08:25 h1tcscs
2016_11_08 09:51 h1iopoaf0
2016_11_08 09:56 h1iopoaf0
2016_11_08 09:56 h1tcscs
2016_11_08 09:58 h1calcs
2016_11_08 09:58 h1oaf
2016_11_08 09:58 h1odcmaster
2016_11_08 09:58 h1pemcs
2016_11_08 09:59 h1ngn
2016_11_08 10:00 h1susprocpi
2016_11_08 10:06 h1pemex
2016_11_08 10:11 h1fw2
2016_11_08 12:32 h1iopoaf0
2016_11_08 12:34 h1calcs
2016_11_08 12:34 h1iopoaf0
2016_11_08 12:34 h1ngn
2016_11_08 12:34 h1oaf
2016_11_08 12:34 h1odcmaster
2016_11_08 12:34 h1pemcs
2016_11_08 12:34 h1susprocpi
2016_11_08 12:34 h1tcscs
2016_11_08 12:39 h1iopoaf0
2016_11_08 12:39 h1oaf
2016_11_08 12:39 h1pemcs
2016_11_08 12:40 h1calcs
2016_11_08 12:40 h1ngn
2016_11_08 12:40 h1odcmaster
2016_11_08 12:40 h1tcscs
2016_11_08 12:41 h1calcs
2016_11_08 12:41 h1iopoaf0
2016_11_08 12:41 h1ngn
2016_11_08 12:41 h1oaf
2016_11_08 12:41 h1odcmaster
2016_11_08 12:41 h1pemcs
2016_11_08 12:41 h1susprocpi
2016_11_08 12:41 h1tcscs
2016_11_08 13:00 h1dc0
2016_11_08 13:00 h1fw0
2016_11_08 13:00 h1nds1
2016_11_08 13:02 h1broadcast0
2016_11_08 13:02 h1fw1
2016_11_08 13:02 h1fw2
2016_11_08 13:02 h1nds0
2016_11_08 13:02 h1tw0
2016_11_08 13:02 h1tw1
2016_11_08 19:35 h1calcs
2016_11_08 19:35 h1iopoaf0
2016_11_08 19:35 h1oaf
2016_11_08 19:35 h1odcmaster
2016_11_08 19:35 h1pemcs
2016_11_08 19:35 h1tcscs
2016_11_08 19:36 h1ngn
2016_11_08 19:36 h1susprocpi

Maintenance tuesday. New frame-cpp code for fw2. ADC install in h1oaf0 starts the instabilities. DAQ restart.

model restarts logged for Mon 07/Nov/2016 - Fri 04/Nov/2016 No restarts reported

After switching to the down to check things and then going back to the OBSERVE, e-16 differences pop up that reflect the precision difference of the file and front end.  This will really hobble the commissioners/operators and jeopordize the configuration and IFO lock.  I know this is not a new problem.

The safe (for the lock) solution is to Accept the values in the FE to the file; but, this is temporary: the FE thinks the value in the file is the same even though it can not write that precision.  Next time the FE reads the file, the problem returns.  A more permanent fix is to revert the FE to the file but this requires the FE to change its value and potentially (maybe pretty small) break a lock.  Some argue we just not monitor these channels but I say that is risky for the configuration as we stop seeing actual problem channel changes.

The real solution is to have the FE code (RCG?) actually write the file at the precision of the FE so all these problems go away.

This channel will be different each lock (PerComm-JWarner.)

Here is the snap of the current 3 differences with the mask removed.

We already know that the BRS's help us out, but here is a nice screenshot from yesterday of the ALS arm power in 40mph winds. Xarm (blue) has BRS sensor correction on and Yarm (green) had it turned on at around -50. The immediate difference really amazed me and I had to share.

Long lock, steady, looks like a good setting to call good.  This is not the safe, just the OBSERVE.

Attached are all the differences, even the not monitored channels.

SEI - No real issues, testing sensor correction and blends on HAMs with opportunities.

SUS - Working.

CDS - Yesterday changed power supplies for ITM blaffle PDs, OAF running steady since Mon. afternoon. The fear is that it was the optical fiber transmiters going bad.

PSL - 70W testing ongoing in Germany.

HWINJ - Testing coming soon.

Vac - Yesterday Kyle prepped for a bakeout on PT180, they will need a 24hr period before 02 to do the baking.

Fac - Removed the last sock on the HAM6 clean room. Water leak still a mystery.

Site meeting at 3:00

TITLE: 11/16 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  Locked at NLN for my entire shift.  Darkhan doing some PCal line work for the first half of the shift.  Observing for the second half.
LOG:

11:53 Turned off PCal lines. Start Kissel's PCAL2DARM measurement.

Saved as /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/PCAL/2016-11-16_H1_PCAL2DARMTF_4to1200Hz_fasttemplate.xml

12:08 Start Kissel's DARMOLGTF measurement.

Saved as /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/DARMOLGTFs/2016-11-16_H1_DARM_OLGTF_4to1200Hz_fasttemplate.xml

12:28 Turned PCal lines back on.

12:57 Observing.

IFO has been locked at NLN since before the beginning of my shift.  I have re-taken a couple of measurements at Kissel's request.  Other than that, rolling along smoothly.

Overview

We will test silent calibration lines over several days to see if we can extract temporal variation in UIM, PUM and TST actuation strengths with the help of cancelled calibration lines. Currently we set up three cancelled calibration lines, one for each of the actuation stages. This will help us to test possibility of using silent lines for tacking calibration of the actuation stages.

Details

Earlier we tried to inject a line from TST actuation and cancel it using PcalY (see LHO alog 31526), but the line still appeared in the ΔL_ext. Today we adjusted amplitude and phase both in SUSETMY and PCALY. We also put lines into PUM and UIM stages and cancelled them with PCALY.

The oscillator settings have been accepted in SDF_OVERVIEW.

The settings for the cancelled lines are:

After the work on adjusting these lines was done Travis started taking PCALY2DARM and DARM OL TFs for which all of the calibration lines were turned off, including the cancelled ones.

TITLE: 11/16 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Travis
SHIFT SUMMARY:

Started the shift with numerous activities (ASC insvestigatinos, ISI ITMy investigations, PI observing, & ITMy oplev OLGs).  Eventually made it to a stable state & have been in Observing ever since.  Can take H1 to NLN, but might want to -manually- skip the CLOSE BEAM DIVERTERS state, so we can monitor AS90/POP90.  We have been locked for 2+hrs with the REDUCE_RF9_MODULATION_DEPTH step, so perhaps we are good here (and don't have to worry about opening SRC1 P & Y loops as Sheila mentioned).  

Had almost 1hr of double coincidence during the shift.

LOG:

• SRC Loop Investigations at beginning of shift
• 5:50 Undisturbed
  • A2L was NOT run since we looked good around 20Hz.
  • Before going to Undisturbed I was chasing Mode27 via phase changes and it went away
• 6:05 Restarted nuc5 because a Seismic FOM disappeared.
• 7:55 Commissioning:  Calibration work begins (Darkhan)

To Do List:

• PI work while locked:  Make note of time & adustments.
• Re-run Kissel's Calibration from last night (since now the SRC is better), BUT remember to turn OFF all (3) Cal lines during measurement, AND remember to turn them ON when done.
• Run A2L if noisy around 20Hz.

• CHARD P -I had previously made the CHARD cut off more aggresive, because in long locks where our spot positions move a little bit this noise will probably lead to the range fluctuating. I was concerned that this was too agresive, so I reverterd to the old cut off filter tonight and set the gain back up to -0.14, but we should try something intermediate once we have seen that the IFO is stable again.
• Patrick directed me to his conlog test machine (http://conlog-test-replica) and I checked for differences in ASC settings between now and saturday's long lock.  (Note that we have not has a stable long lock since Monday's accidental reboot of everything).  The most suspicous wrong settings were in the refl DC centering loops, I've reverted to the settings in the screenshot attached to 31382.  
• Corey and I did add back in the RF9 modulation depth increase, and locked on the AS36 signal for SRM, and it seems OK so far.  (before doing that we had a couple of locks were switching to AS36 clearly made the build ups worse) I suspect that the funky AS36 input matrix is sensitive to the RF9 modulation depth, so we either need to retune it if we are going to skip the reduction, or just put the reduction back in. 
• We were locked for about an hour like this, with PR3 controlled on POPX instead of REFL WFS.  When we tried to switch over the IFO unlocked. For tonight I am just suggesting that Corey skip the switch and leave the beam diverters open.  We will have to think about a real solution in the morning.  (We have tried measuring the matrix, which seemed to work short term anyway).  Other options would be to try to increase the recycling gain or to see if we can give the PRC2 loops more gain margin. 

Operator information:

I've added the Reduce RF9 modulation depth state back into the normal guardian path, but if you are having locklosses durring this state or right after you can try skipping it.  If you skip it, you might want to keep the beam diverters open so you can see that the SRC1 loops are OK (ie, the ratio of AS90/POP90 is staying reasonably high over the lock). You might need to open the SRC1 loops if you skip reducing RF9 modulation depth.  

I've also moved PR3 REFL WFS out of the normal path, so that it will be skipped for now if you just request nominal low noise. 

Related logs, 31303, 31371, 31403

Jeff, Kiwamu,

We have copied the actuator function plotting script from LLO and adopted for LHO. The code seems to run fine. It resides at

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Scripts/FullIFOActuatorTFs/actuatorCoefficients.m

The attached are the resulting pdf showing the three sets of measurements that Jeff took in the past few days. I did not do fittin yet. Below are several notes

• We have incorported the correction factors for the actuator functions (31369).
  • They are directly  writen in the interferometer dependent paramter file at /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/params/H1params.conf
• We are reminded that there is significant discrepancy between the measured and model in UIM at high frequencies (24197)
• TST and PUM seem fine both in magnitude and phase.
• We switched the suspension tag model
  • from quadmodelproduction-rev7995_ssmake4pv2eMB5f_fiber-rev3601_h1etmy-rev7915_released-2016-06-15.mat
  • to quadmodelproduction-rev7995_ssmake4pv2eMB5f_fiber-rev3601_h1etmy-rev7915_released-2016-03-01.mat
• However, in doing so, Jeff found what appears to be a bug in the suspension model which can impact on low frequency suspension resonances around 1 Hz. He is working on this at the moment.