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. 

J. Kissel for D. Tuyenbayev

Darkhan turned on both a PCALY and SUSETMY L3 calibration line at 30.1 Hz yesterday night. The idea is that these lines, driven at the same frequency but exactly opposite in phase, will cancel each other out and not cause any impact on the sensitivity. The hope is that we can use this scheme in the future -- tracking the residual of cancelling PCAL and ETM actuator lines, instead of driving them very loudly right next to each other.

We plan to leave this line in for a few days, and then we'll turn it off.

Currently -- because we haven't had too many long lock stretches, the phases of each line are not tuned well, so there may still be a pretty large residual. We'll continue to work on it as the duty cycle improves. Your patience is appreciated.

I have epoxied the final Newtonian noise L4C to the ground.  Note that it is in the walking path from the door to the LVEA over to the HAM6 area, so please be careful.  There is some tape, and a cone to help make it easier to see.

Corey, Sheila

We used to average the value of the POP QPD before engaging the loop that feeds it back to PRM, and not engage the loop if the value was too large.  We have occasionally been getting bogus values from cdsutils average in guardian (30831), which was causing guardian to get stuck here and not engage the loop. 

Since we had set the thresholds to be +-1 anyway, I just removed the averaging and checking from the guardian completely, so this shouldn't happen anymore. 

TITLE: 11/15 EVE Shift: 0:00-08:00 UTC (16:00-0:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind:  Gusts up to 20mph
    Primary useism:  Has been trending slowly up over last 24hrs (not to worrisome levels yet)
    Secondary useism:  --
QUICK SUMMARY:

Received handoff from TJ/Kissel.  And looks like we have a few items on the docket:

• Investigating SRC1 P/Y loops (noticed possible issue last night).  (Sheila)
• ITMy ISI config change to help damp ITMy suspension after locklosses (we are now restored, since we had a lockloss and DOWN script restores us).  Warner notifed me of this.
• ITMy SUS Oplev Open Loop Gain (OLG) measurement being run after lockloss (per Kissel request)
• We had been at the INCREASE POWER state for a while and then PI Modes rang up (28 & then 27).  27 rung up to a point we couldn't damp, so we took the power down to 24W, but unfortunately, H1 dropped out of lock.
• ITMy oplev OLG Run
• Back to the drawing board.

We've set the PI verbal alarm to trigger at 3 now that we're sitting at a lower power. Let me know if that's low enough for damping response time and/or if it's too low and getting triggered unnecessarily. 

WP6314 h1oaf0 stability

Richard, Fil, Daniel, Jim, Dave:

h1oaf0 has been stable since 12:46 Mon 14th PST, no further work was done on this system

WP6312 adding new MD5 DAQ epics channels to the DAQ

Dave:

A new H1EDCU_DAQ.ini file was generated and installed during a DAQ restart at 12:11PST.

WP6315 updated frame-cpp on frame writers

Jim, Jonathan, Dave

The new code (which has been running on h1fw2 for the past week) was installed on h1fw0. Jonathan has test code to look at frames written by fw0 (new) and fw1 (old) to check they are identical. We will test for several days before the decision to upgrade fw1 is made.

WP6318 bug fix in h1susauxb123 model

Jeff:

New code for h1susauxb123.mdl to fix a bug. No DAQ restart required.

WP6324 Extend Remote Access controls to 24/7

Jonathan:

The RACCESS system is now operational 24/7 for the duration of ER10 and O2.

Testing new Hardware Injection data injestion

Keith, Dave, Jim:

New configurations of h1hwinj1 and h1guardian0 permit hw-injection users on h1hwinj1 to svn check-out the injection waveforms and schedules such that the guardian INJ_TRANS node can perform these injections. We had a minor local modification to the INJ_TRANS.py file which was removed and the guardian node code was updated to the latest SVN version. We discovered a slight discrepancy between the code and the schedule file which was resolved. System is ready for injection team to test.

It was found that the default UMASK on the newer Debian workstations were different from the Ubuntu12/14 machines (022 on debian, 002 on ubuntu). This meant that the default file permissions for new files on debian were 644 (rw-r--r--) and therefore not group writable. We are changing the default umask for user-type accounts to be 002 on all machines (via  pam_umask), and I have appended a line to everyone's .bashrc file to set "umask 002" as an OS-agnostic method of ensuring correct permissions.

If you want to check if your account is setup correctly, first check your umask setting by  typing the umask command

david.barker@zotws2: umask
0002

As a further check, create a new file and verify the correct permissions (rw-rw-r--)

david.barker@zotws2: touch testfile
david.barker@zotws2: ls -al testfile
-rw-rw-r-- 1 david.barker controls 0 Nov 15 16:15 testfile
 

and finally verify you belong to the controls group as your secondary group

david.barker@zotws2: groups
david.barker controls
 

WP 6323

The following items were removed from temporary power supplies and connected to 24V DC rack power:

1. Baffle Photodiode Amplifier Units (ITMX/ITMY)
2. RGA unit next to HAM4
3. EtherCAT hub - CU1128

WP 6292

A safety system controls chassis was installed at each end station. As of now, units are not powered on.

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.

J. Kissel

Though it's been a struggle between all of the H1OAF computer crashing, I've managed to squeak out one more round of calibration measurements today. The data's location is below; analysis to come.

The data lives here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/
(1a) DARMOLGTFs/2016-11-10_H1_DARM_OLGTF_4to1200Hz_fasttemplate.xml
(1b) PCAL/2016-11-10_H1_PCAL2DARMTF_4to1200Hz_fasttemplate.xml

(2)
FullIFOActuatorTFs/2016-11-10/2016-11-10_H1SUSETMY_L1_iEXC2DARM.xml
FullIFOActuatorTFs/2016-11-10/2016-11-10_H1SUSETMY_L1_PCAL2DARM.xml
FullIFOActuatorTFs/2016-11-10/2016-11-10_H1SUSETMY_L2_iEXC2DARM.xml
FullIFOActuatorTFs/2016-11-10/2016-11-10_H1SUSETMY_L2_PCAL2DARM.xml
FullIFOActuatorTFs/2016-11-10/2016-11-10_H1SUSETMY_L3_iEXC2DARM.xml
FullIFOActuatorTFs/2016-11-10/2016-11-10_H1SUSETMY_L3_PCAL2DARM.xml

J. Kissel

I've taken the first round of all swept sine measurements typically done before an observing run:
(1) Sensing function, C
    (a) DARMOLGTF and Loop Suppression (IN1/IN2 and IN2/EXC); G and 1/(1+G)
    (b) PCAL2DARM (and PCAL2DELTAL); (C/1+G) and [m/m]
(2) Actuation Function, A
    (a) L1 to DARM & associated PCAL2DARM; (C A_uim)/(1+G) and (C/1+G)
    (b) L2 to DARM & associated PCAL2DARM; (C A_pum)/(1+G) and (C/1+G)
    (c) L3 to DARM & associated PCAL2DARM; (C A_tst)/(1+G) and (C/1+G)
where I've taken a separate PCAL2DARM or C/1+G transfer function with every corresponding excitation to destroy any covariance that had plagued us during O1. Also, I've worked to
    (i) reduce the template's measurement time by maximizing drive, 
    (ii) reducing the number of points over all, and
    (iii) keeping integration time in check,
such that each template only takes about 15 minutes. I've also modified the frequency vectors of the actuation functions to go out to 1 kHz, as LLO did for their O1 data sets. In doing so, I made sure to use frequency points that avoided any known high-frequency resonances from wire violin modes (characterized in LHO aLOG 24917). 

There's still some improvements to make, which I'll shoot for in the next round (so don't use/take these templates as cannon yet), but thanks to the high-duty cycle of the IFO, I had the opportunity to make really well-balanced templates tonight.

The data lives here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/
(1a) DARMOLGTFs/2016-11-07_H1_DARM_OLGTF_4to1200Hz_fasttemplate.xml
(1b) PCAL/2016-11-07_H1_PCAL2DARMTF_4to1200Hz_fasttemplate.xml

(2)
FullIFOActuatorTFs/2016-11-07/2016-11-07_H1SUSETMY_L1_iEXC2DARM.xml
FullIFOActuatorTFs/2016-11-07/2016-11-07_H1SUSETMY_L1_PCAL2DARM.xml
FullIFOActuatorTFs/2016-11-07/2016-11-07_H1SUSETMY_L2_iEXC2DARM.xml
FullIFOActuatorTFs/2016-11-07/2016-11-07_H1SUSETMY_L2_PCAL2DARM.xml
FullIFOActuatorTFs/2016-11-07/2016-11-07_H1SUSETMY_L3_iEXC2DARM.xml
FullIFOActuatorTFs/2016-11-07/2016-11-07_H1SUSETMY_L3_PCAL2DARM.xml

While it'll be days before we have a model and a complete, traceable uncertainty budget, preliminary results show the *mean* of *one measurement* of PCAL's estimated displacement agrees with the front-end calibrated sensitivity to roughly 5% and 5 [deg]. This confirms that the > 50 Hz discrepancies between PCAL and DELTA L EXTERNAL seen while we were at 50 [W] (e.g. LHO aLOGs 30391 and 30431) were likely a function of the poorly controlled signal recycling cavity, and therefore time-dependent RSE cavity pole that was quite low.
Recall that the uncertainty of the PCAL estimation is around 1%. 

We're right on schedule, and things are looking up. We'll see how the modeling goes...