In hopes to not lose the lock and with approval from MLandry, we increased the limits from 500 to 700um.  These are the limits changed:

H1:HPI-ETMX_ISCINF_LONG_LIMIT

H1:HPI-ETMY_ISCINF_LONG_LIMIT

H1:LSC-X_TIDAL_CTRL_LIMIT &

H1:LSC-Y_TIDAL_CTRL_LIMIT

The post change trend looks like we may be out of the woods as the attached plot shows a turn over and the tide may pull us back.  If we last another 6 to 12 hours, we'll really know something.

The first attachment shows the RF45_AM_CTRL_OUT (and RF9) to DARM coherence when RFWhen RF45 AM was not glitching. Left column is after we pulled RFAM measurement unit and coupler out of the PSL room, right is before we installed RF AM measurement unit and coupler, but the distinction between left and right is not that important.

There are two things worth noting:

1. When it's not glitching, there's some coherence between RFAM and DARM at around 170-190Hz, 540-580Hz, and 810-860Hz.

The coherence is almost common to both RF45 and RF9 (which is monitoring RF45 in CER), so this is probably the harmonic generator or some common environmental noise coupling into two different distribution amplifier outputs.

Seems like the shape of the noise bumps in RF45_AM_CTRL_OUT_DQ is not stable over time. Also, this might have become somewhat worse over time.

2. Wandering peak between 600 and 700 Hz (and its second harmonic) that comes and goes.

It's apparent in the right column, but there's also one trace in the left (black trace, Nov/22).

In my plot the measurement time was arbitrary and very very sparsely chosen, so it's not clear if the peak is gone after Nov/22. The peak was not present in Nov/07 data point either (right, brown traces).

Coherence between CARM and both RF45 and RF9 control outputs are very high for this peak.

I can see the second harmonic but not 3rd and higher (second attachment).

The peak also seems to be visible in FOM reference trace from 2015/Oct/14 (third attachment).

I wonder if detchar identified the cause of this.

Activity Log: All Times in UTC (PT)

16:00 (08:00) Take over from JT
17:10 (09:10) Bubba – Finished with tractor clearing the roads
18:27 (10:27) CW Injection running alert
18:30 (10:30) CW injection inactive alert
19:55 (11:55) Kyle & Gerardo – Going to X2-8 
20:03 (12:03) Out of Observing for vacuum work at X2-8 (WP #5632)
20:16 (12:16) Kyle & Gerardo – Finished at X2-8, coming back to CS. IFO back to Observing
20:47 (12:47) Bubba – Going to Mid-X to work on actuators
21:11 (13:11) John- Going to Mid-X
21:57 (13:57) John & Bubba – Back from Mid-X
00:00 (16:00) Turn over to Travis


Shift Summary:

Support: None needed
 
Incoming Operator: Travis

Shift Detail Summary: IFO has been locked in Observing mode for almost 24 hours. Switched to Commissioning mode for 13 minutes, while Kyle & Gerardo were performing vacuum work at X2-8 (WP #5632). The range has generally been over 80Mpc for most of the shift. There were 8 ETM-Y saturations during the shift. Did not observe any RF45 glitches associated with the ETM-Y saturations. Wind has been building and is now a light to gentle breeze (4 to 12mph). Seismic has been flat all shift (around 0.03um/s). Microseism has a slight upward slope and is centered around 0.3um/s.

Resulting pressure reduction at nearest BT gauge is as expected, i.e. reduced by a factor of ~2.5.   

Also, there is now a large error in pump current converted pressure at the ion pump controller vs. independent gauge voltage -> gauge voltage converts to 2e-9 torr, ion pump controller indicates 1e-10 torr (converting 3 uAmps) -> 20 hour pump down curve of captured gauge data prior to opening valve is as expected -> ignoring pump current converted pressures at these small values

In 24 hours, the lock stretch has already used 80% of the doubled range on the HEPI bleed off.  This is not 'tidal.'  The attached plot shows the trends of the bleed to HEPI and LVEA and RefCav temps.  It looks very coincident on this 3 day trend with a big dip on the LVEA temp and the step run up on the HEPI drive. But, if this increase in LVEA temp is getting to the refcav increasing its length, the sign is wrong at HEPI.  An increase in length will lead to an increase in length.  Also, while not know with certainty, the mechanism of getting a temp change into the refcav certainly has a pretty large delay.  Any thoughts?

If this trend does not turn around soon, the lock will be lost unless we further increase the limit.  If the drive hits 0.7mm, angular integrity will start to be compromised as the IPS on HEPI reaches its linear limits

Posted are the November data for the 3IFO desiccant cabinet in the LVEA and the two Dry Box storage cabinets in the VPW. No interesting or disturbing trends are apparent.   

 Laser Status:

18:27 (10:27) Alert - "CW Injection running"
18:30 (10:30) Alert - "CW Injection inactive" 

20:03 (12:03) Out of Observing for vacuum work at X2-8 (WP #5632)
20:16 (12:16) Kyle & Gerardo – Finished at X2-8, coming back to CS. IFO back to Observing mode

   Good observing shift so far. IFO locked in Observing mode for past 19 hours (less aLOGed drops to Commissioning mode), with a range around 80Mpc. Environmental conditions remain good. There have been 3 ETM-Y saturations.

This work was done on Tuesday Dec. 1 2015.

The following EPICS channels were created and added to the DAQ:

X2-8:

H1:VAC-EX_X6_PT527_PRESS_OVERRANGE

H1:VAC-EX_X6_PT527_PRESS_SENSOR

H1:VAC-EX_X6_PT527_PRESS_TORR

H1:VAC-EX_X6_PT527_PRESS_TRIP

H1:VAC-EX_X6_PT527_PRESS_UNDERRANGE

H1:VAC-EX_X6_PT527_PRESS_VALID

Y2-8:

H1:VAC-EY_Y6_PT427_PRESS_OVERRANGE

H1:VAC-EY_Y6_PT427_PRESS_SENSOR

H1:VAC-EY_Y6_PT427_PRESS_TORR

H1:VAC-EY_Y6_PT427_PRESS_TRIP

H1:VAC-EY_Y6_PT427_PRESS_UNDERRANGE

H1:VAC-EY_Y6_PT427_PRESS_VALID

h1ecaty1

ran svn update of C:/SlowControls (see h1ecaty1_update.png for updates (the updates not shown were TwinCAT3 related))
made changes to C:/SlowControls/TwinCAT/Source/Current/Interferometer/End/Plc1.pro to add variables for X2-8 and Y2-8 vacuum gauges and commited changes to svn (revision 2553)
ran svn update of C:/SlowControls

LIGO TwinCAT Target Configuration: H1ECATY1: SYS, PLC1, PLC2, PLC3: Update from source

C:/SlowControls/Target/H1ECATY1/H1ECATY1.tsm:
PLC - Configuration: PLC1: ReScan
Undisabled Vacuum Gauge NEG (BPG 402)
Saved

LIGO TwinCAT Target Configuration: H1ECATY1: SYS, PLC1, PLC2, PLC3: Compile

C:/SlowControls/Target/H1ECATY1/H1ECATY1.tsm:
PLC - Configuration: PLC1: ReScan
Saved
PLC - Configuration: PLC2: ReScan
PLC - Configuration: PLC3: ReScan
Saved

Put TwinCAT into configuration mode and scanned for devices
Found new vacuum gauge and 2 fiber converter boxes
Added the new vacuum gauge and fiber converter boxes to the configuration

Put into free run
Changed pressure readout for the new vacuum gauge to torr and saved to nonvolatile memory

Linked the variables for the new gauge
Changed the name of the new gauge and fiber converter boxes
Generate Mappings
Check Configuration
Activate Configuration
Put into run mode
Saved, copied to C:/SlowControls/Scripts/Configuration/H1ECATY1/SYS, commited to svn
Ran svn update on C:/SlowControls

(see h1ecaty1_config.png for picture of system manager configuration)

Stopped running EPICS IOC
LIGO TwinCAT Target Configuration: H1ECATY1: SYS, PLC1, PLC2, PLC3: Everything
PLC1 and PLC3 did not run, had to open by hand, login and run

burtrestored all PLCs to 6:10 AM (local time)
 

h1ecatx1

ran svn update of C:/SlowControls (see h1ecatx1_update_1.png, h1ecatx1_update_2.png, h1ecatx1_update_2.png for updates)
LIGO TwinCAT Target Configuration: H1ECATX1: SYS, PLC1, PLC2, PLC3: Update from source

C:/SlowControls/Target/H1ECATX1/H1ECATX1.tsm:
PLC - Configuration: PLC1: ReScan
PLC - Configuration: PLC2: ReScan
PLC - Configuration: PLC3: ReScan
Saved

LIGO TwinCAT Target Configuration: H1ECATX1: SYS, PLC1, PLC2, PLC3: Compile

C:/SlowControls/Target/H1ECATX1/H1ECATX1.tsm:
PLC - Configuration: PLC1: ReScan
PLC - Configuration: PLC2: ReScan
PLC - Configuration: PLC3: ReScan
Saved

Undisabled Vacuum Gauge NEG (BPG 402)
Saved

Put TwinCAT into configuration mode and scanned for devices
Found only fiber converter box
Tried a few more times, eventually found new vacuum gauge and 2 fiber converter boxes
Added the new vacuum gauge and fiber converter boxes to the configuration

Changed the name of the new gauge and fiber converter boxes

Put into free run
Changed pressure readout for gauge to torr and saved to nonvolatile memory

Linked the variables for the new gauge
Generate Mappings
Check Configuration
Activate Configuration
Put into run mode
Saved, copied to C:/SlowControls/Scripts/Configuration/H1ECATX1/SYS, commited to svn
Ran svn update on C:/SlowControls

(see h1ecatx1_config.png for picture of system manager configuration)

Stopped running EPICS IOC
LIGO TwinCAT Target Configuration: H1ECATX1: SYS, PLC1, PLC2, PLC3: Everything
PLC2 and PLC3 did not run, had to open by hand, login and run

burtrestored all PLCs to 6:10 AM (local time)
 

Attached is a plot of the reference cavity transmission and room temperature.  Also plotted are
the quadrant signals from the quadrant photodiode in the ISS box.  The transmission didn't
deteriorate too badly after yesterday's tweak.

The second plot shows the pre-modecleaner temperature and the output of its heater.  Whilst the
heater's job is to keep the pre-modecleaner PZT voltage within its range, it does appear that
the lengthening of the body couples to the pitch (mostly) of the output beam.  THis might be due
to the way the pre-modecleaner body is clamped to its container.

O1 day 75

model restarts logged for Tue 01/Dec/2015
2015_12_01 12:32 h1dc0
2015_12_01 12:33 h1dc0
2015_12_01 12:34 h1broadcast0
2015_12_01 12:34 h1dc0
2015_12_01 12:34 h1nds0
2015_12_01 12:34 h1nds1
2015_12_01 12:34 h1tw0
2015_12_01 12:34 h1tw1
2015_12_01 12:37 h1dc0
2015_12_01 12:44 h1nds0
2015_12_01 12:46 h1dc0
2015_12_01 12:47 h1dc0
2015_12_01 12:51 h1dc0
2015_12_01 12:56 h1dc0
2015_12_01 12:58 h1nds0
2015_12_01 13:00 h1broadcast0
2015_12_01 13:00 h1nds1
2015_12_01 13:00 h1tw0
2015_12_01 13:00 h1tw1

Maintenence day. Beckhoff and FMCS changes. Initial DAQ restart failed due to monit respawning too rapidly and over-populating the running configuration directory.

O1 day 74

model restarts logged for Mon 30/Nov/2015 No restarts reported

Add 125ml water to crystal chiller. Diode chiller level is OK.

At 15:06 UTC Bubba told me that he was headed out to clear the parking lots of snow. Since then there has been about a 5Mpc drop in range. Coincidence?

J. Kissel

I've taken new DARM Open Loop Gain and PCAL2DARM transfer functions for the bi-weekly(-ish) full-frequency-span confirmation of the time variation in calibration / IFO parameters. As a by-product of these two transfer functions, we're able to confirm that the front-end, CAL-CS, DELTAL_EXTERNAL calibration (and therefore the low-latency GDS pipeline output) is still within the desired precision. I attach screenshots of the measurements. They will be processed in greater detail tomorrow, once we have the evening's kappa values (i.e. what the calibration lines are telling us the systemaic errors are in the model parameters). Stay tuned, but things continue to look exquisite. Great job CAL team!

DARM OLGTF Template:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/2015-12-01_H1_DARM_OLGTF_7to1200Hz.xml

Corresponding Exports:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/DARMOLGTFs/
2015-12-01_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_coh.txt
2015-12-01_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKEXC_tf.txt
2015-12-01_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_coh.txt
2015-12-01_H1_DARM_OLGTF_7to1200Hz_A_ETMYL3LOCKIN2_B_ETMYL3LOCKIN1_tf.txt

PCAL2DARM TF Template:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Measurements/PCAL/2015-12-01_PCALY2DARMTF_7to1200Hz.xml

Corresponding Exports:
2015-12-01_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_coh.txt
2015-12-01_PCALY2DARMTF_7to1200Hz_A_PCALRX_B_DARMIN1_tf.txt

J. Kissel, S. Karki, B. Weaver, R. McCarthy, G. Merano, M. Landry

After gathering the weekly charge measurements, I've compared H1 SUS ETMY ESD's relative Pitch/Yaw actuation strength change (as measued by the optical levers) against the Longitundinal Actuation Strength (as measured by PCAL / ESD calibration lines). As has been shown previously (see LHO aLOG 22903), the pitch/yaw strength's slope trends very nicely along with the longituinal stength change -- if you take a quick glance. Upon closer investigation, here are things that one begins to question:
(1) We still don't understand why the optical level actuation strength assessments are offset from the longitunidal strength assessment after the ESD bias sign flip. 
(2) One *could* argue that, although prior to the flip the eye-ball-average of oplev measurements trackes the longitudinal strength, after the flip there are periods where two quadrants (magenta, in pitch, which is LR, from Oct 25 to Nov 8; black, in yaw, which is UR, from ~Nov 11 to Dec 06) track the longitudinal strength. As such, one *could* argue that the longitudinal actuation strength trend is dominated by a single quadrant's charge, instead of the average. Maybe.
(3) If you squint, you *could* say that the longitudinal actuation strength increase rate is slowly tapering off, where as the optical lever strength increase *may* be remaining constant. One could probably also say that the rate of strength increase is different between oplevs and cal lines (oplev P/Y strength is increasing faster that cal line L strength).
All this being said, we are still unsure whether we want to flip the ETMY ESD bias sign again before the observation run is out. Landry suggests we either do it mid-December (say the week of Dec 14), or not at all. So we'll continue to track via optical lever, and compare against the longitudinal estimate from cal lines.

Results continue to look encouraging for ETMX -- ever since we've had great duty cycle, and turned off the ETMX ESD Bias when we're in low-noise and/or when the IFO is down, the charging rate has decreased. Even though the actuation strength of ETMX doesn't matter at the few % level like it does for ETMY (because ETMX is not used as the DARM actuator in nominal low-noise, so it doesn't affect the IFO calibration), it's still good to know that we can get an appreciable effect by simply reducing the bias voltage and/or turning it off for estended periods of time. This again argues for going the LLO route of decreasing the ETMY bias by a factor of 2, which we should certianly consider doing after O1.

---------------
As usual, I've followed the instructions from the aWiki to take the measurements. I had much less trouble today than I had last week gathering data from NDS, which is encouraging. One thing I'd done differently was wait a litle longer before requesting the gathering and analysis (I waited until the *next* measurement had gone through -9.0 and -4.0 [V] bias voltage points and started the 0.0 [V] point, roughly 5 minutes after the measurement I wanted to analyze ended). As such, I was able to get 6 and 4 oplev data point to compose the average for ETMX and ETMY, respectively (as opposed to the 3 and 1 I got last week; see LHO aLOG 23717).

Once all data was analyzed, I created the usual optical-lever-only assessment using 
/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts/Long_Trend.m
and saved the data to here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Results/CAL_PARAM/2015-12-01_H1SUSETMY_ChargeMeasResults.mat

However, I'd asked Sudarshan to gather the latest calibration line estimates of the ESD longitudinal actuation strength (aka kappa_TST), which he gathered from his matlab tool that gathers the output of the GDS function "Standard Line Monitor." (He's promised me an updated procedure and an aLOG so that anyone can do it). This is noteably *not* the output of the GDS pipeline, but the answers should be equivalent. His data lives here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Results/CAL_PARAM/2015-12-01_Sep-Oct-Nov_ALLKappas.mat

Finally, I've made the comparison between oplev and cal live strength estimates using
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Scripts/CAL_PARAM/compare_chargevskappaTST_20151201.m

Calibration parameter updates that includes data until Nov 11.

Kappa_tst is slowly trending up after the bias sign flip on Oct 16  and rest of the paremeters show normal variations that we have seen in the past.

The first plot contains all the parameters that we calculate. 

The second plot highlights kappa_tst, kappa_C and cavity pole of which the kappa_tst and kappa_C will be applied to h(t).

This data is filtered for locked state using GDS state vector and thus contains some outliers at times when the IFO is locked but not in anlaysis ready state. In  future, we plan to use GDS state vector which will give us the flexibility to only use analysis ready data.