I did some injections on HAM1, for comparison with 42694 and 42722

I reduced the amplitude compared to 44856, so these excitations aren't showing up in DARM, but people can look for them in the REFL WFS and table top L4Cs.  

The Z excitation started at 2:11:50 UTC, was stopped after a large glitch at 2:23 UTC Jan 15th. 

The X excitation started at 2:27 UTC, but there were several large glitches.  a relative glitch free time was from 2:37-2:44, the excitation continued until 2:44 UTC. 

The Y excitation started at 2:55 UTC, and was on until 3:06.  We had to turn the dither lines back on partway through that because the PRC1Y was slowly going unstable. 

J. Kissel

Since it looks like we're sticking with using ETMX for all stages of DARM actuation, I've switched the CAL lines for the UIM and PUM (L1 and L2) stages to being driven from ETMX. For now, I've left then at the same frequencies they were before (15.1 and 16.7 Hz), instead of the recommended line frequencies from Joe earlier today. After I 
    - get a new set of calibration sweeps to update the front-end calibration for a 30W IFO, and for full ETMX actuation (hopefully tonight)
    - update the front end
    - generate new EPICs records for the time-dependent correction factors
then I'll switch to the line frequencies Joe suggests.

I've accepted this into the SDF.

TITLE: 01/15 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY:
LOG:

• 14-01-19 16:10 Robert to ISCT1
• 14-01-19 16:14 Corey to TCS chiller to check , about 15 minutes
• 14-01-19 16:43 Bubba and Peter out of EY VEA
• 14-01-19 18:57 Nutsinee to ISCT6
• 14-01-19 19:08 Karen to Mid-Y
• 14-01-19 19:22 Terry out to LVEA around HAM6
• 14-01-19 19:33 Robert to ISCT1
• 14-01-19 19:58 Terry out of the LBEA
• 14-01-19 19:58 Nutsinee out of the LVEA
• 14-01-19 20:20 Robert back from LVEA
• 14-01-19 20:20 Robert to EX
• 14-01-19 21:46 Travis to optics lab
• 14-01-19 21:49 Rick Demitire Niko to Ey
• 14-01-19 22:33 Travis to LVEA to look for gold mirror
• 14-01-19 22:33 Fil back from the vault
• 14-01-19 23:36 I reengaged the BRSY after visits this morning
• 14-01-19 22:45 Cheryl to LVEA to adjust a camera
• 14-01-19 23:03 Marc to mid x, to flip on power supplies for readout of LEMI magnets
• 14-01-19 23:07 Cheryl out of the LVEA
• 14-01-19 23:42 Marc back

Schedule as of the end of the meeting, for 15 Jan 2019:  Tentative

• 7AM: SEI Proc & SEI ISI corner boots - Jim
• 8:30AM: Lock IMC
• 9AM: IO path on the PSL, IO_MB_M3, replace optic and damp the high Q
• 11AM: ASC Model/Boot
• DEFERED TO WED: Guardian Machine Swap

Activities:

• ASC Model Update
• SEI  corner ISI Model boots, sensor correction
• EY Pcal Meas
• CALEX model work
• TCS model update
• Temp Sensor fix on Pcal
• TEMP P.S. EX ESD
• HAM2 Handrail
• move HAM5/6 CR ~2'
• ISS 2nd loop QPD centering, per Gabriele's alog (done today, Monday)
• SRM SWC Setup @ HAM5
• EY HWS beam align - NEEDS EY optics, hardware, software, to be unchanged during this activity
• PEM inventory walkabout
• Table top FSS P.S.HDWR @ SQZ table
• ground measurements at EX
• Damp PSL/IO (2x) optics/mounts, and swap M3 optic
• HAM2/3 inspection measurements
• swap out TCSY chiller with spare
• RF/ground loop hunting
• Trend writer work

Images of the very full white board attached.

During the several hour lock over night, that I found the IFO in this morning there were some strange combs in the CARM signals. 

The particularly strange thing is that I see these spikes in the LSC-MCL signals for that lock first thing this morning, but haven't really seen them in any later locks today.  During the lock that the spikes are there, there are a few times that the spikes go away for 2-4 sec, but they always came back.  In the next lock, the spikes were almost never there, but did come in 2 or 3 times for 1-2 sec, but then went away again.  Between these 2 locks, I'm not aware that any configuration changes were made to the CARM system.

The SR785 was plugged in to the IFO common mode board, and the excitation input was enabled, so it's possible that the SR785 and whatever mysterious grounding problems we've been having are the culprit.  But, since the SR785 wasn't unplugged until much later in the day, I'm not so sure.  Anyhow, we're going to try to make a habit of unplugging any instruments from the ISC racks as soon as a measurement is complete, just in case.

It looks to me like there are 2 different combs, both very near 232 Hz, but they are drifting in time relative to one another.  See attached DARM spectrum with the giant comb, as well as ndscope screenshots from 2 different times during the same lock.  The ndscope screenshots also show that the IFO is in the same state (NomLowNoise) for both of these times.  No gain sliders in the common mode or IMC servo boards were being moved either.

As Danny reported on Friday 46382, the HAM2 motion coupling to DARM that Robert noticed 46373 is coupling through the ISS second loop, and there is also strong coherence with DARM below 30Hz.  

Dany and I used data from several different locks on Friday, and we couldn't make a good comparison of the low frequency noise in DARM because some of those locks had large scattering or other low frequency problems. This morning Keita Jenne and I got about 10 minutes of data with the ISS second loop in 4 different states while the interferometer was in low noise:

The attached DARM spectrum shows that the ISS was adding noise to DARM both at 25Hz and below and from 350-400Hz.  The coherence  of the ISS out of loop diodes with DARM is pretty much the same weather the second loop is AC or DC coupled.  REFL RIN also indicates that the intensity noise imposed by the second loop is the same for the AC coupled or DC coupled ISS.

Georgia and Danny have pico'd the array to fix this. 

J. Betzwieser, E. Goetz, J. Kissel

During the prep for install of all the new infrastructure for the O3-level calibration front-end model upgrades at LLO, they discovered another flaw / bug from me. This time, it's a copy-and-paste error with the smoothing process for the time-dependent correction factors. 

The *design* is to have every raw TDCF, computed in the simulink library
    /opt/rtcds/userapps/release/cal/common/models/CAL_LINE_MONITOR_MASTER.mdl
should be fed into three conditioning processes:
(1) a gate function,
    /opt/rtcds/userapps/release/cds/common/src/COH_GATE.c
(2) a median function,
    /opt/rtcds/userapps/release/cds/common/src/BUFFER_AND_MEDIAN.c
(3) and an average function,
    /opt/rtcds/userapps/release/cds/common/src/BUFFER_AND_AVERAGE.c

The way one sets these function calls is by changing the text inside the properties of the block. Like was the problem with the other user-created library parts (see LHO aLOG 46260), these blocks were renamed and -- until today -- the description was hidden, so it was easy for me to miss this copy and paste. Thus, I had mistakenly conditioned each of the TDCFs with Gate, Median, and Median, instead of Gate, Median, and Average.

The library has now been changed, the blocks are now annoted, the h1calcs model compiles successfully, and the above mentioned library part has been committed to the svn in the above descripbed location.

The intent is to install this fix tomorrow. It should not require a DAQ restart.

WP8040 New h1calinj model on h1oaf1

Jamie, Dave:

The new model was started this afternoon, it will be added to the DAQ during tomorrow's maintenance.

I have added it to the CDS overview (attached)

Since the calibration group is moving to run individual calibration for the L1, L2, and L3 actuators, in addition to the PCAL lines, we are adding an additional line frequency.

The following is a result of suggestions by Evan Goetz in LHO alog 44892, and some other constraints.

The LHO lines will become:
L1 (UIM) line: 16.7 Hz
L2 (PUM) line: 17.3 Hz
PCAL line: 17.9 Hz
L3 (TST) line: 19.1 Hz

PCAL sensing line: 433.7

Note this is slightly different from Evan's proposal after swapping 15.1 Hz and 17.3 Hz between LHO and LLO.

For comparison, LLO's is changing to:
L1 (UIM) line: 15.1 Hz
L2 (PUM) line: 15.7 Hz
PCAL line: 16.3 Hz
L3 (TST) line: 16.9 Hz

PCAL sensing line: 434.9 Hz

See LLO alog 42720

Jenne, Daniel, Jeff K., Sheila, Chris W., Patrick

I have created two scripts to aid with violin mode damping:

/opt/rtcds/userapps/release/sus/h1/scripts/violin_damping/filter.py

This is a GUI to aid in the creation of filter files for damping violin modes. Most notably it scripts the creation of the phase change filters for a given frequency. It is possible the method used here could be made more analytical, if someone has the time to look into how.

/opt/rtcds/userapps/release/sus/h1/scripts/violin_damping/settings.py

This is a GUI to aid in selecting the DOF, phase, and gain for damping violin modes. Most notably it turns on the correct combination of filter modules for a given phase, assuming that the filter modules are in the banks set by the filter.py script.

More details are in the comments at the top of each script.


I have also attached a log of the settings I have found to date for each frequency. These still need to be verified.

• IFO was in ENGAGE_ASC_FOR_FULL_IFO when I arrived - this is awesome!
• Tried hand-engaging SOFT loops, but PRC2 yaw started running away, as mentioned by TVo in alog 46387.  Turned off all ADS loops and CSOFT Pit, lock still okay.
  • Only engaged Pit3 and Yaw3 (PRM to ITM spot), seems fine.  Error signal on Yaw4 is really far off, which is probably why PRC2 is needing to follow so far.
  • Engaged Pit5 and Yaw5 (Yarm), which had error points close to zero, seems fine. 
  • Moved Yaw4 line frequency back to 22.3Hz, and switched to the old bandpass, and the ADS error signal agrees on the direction that Yaw4 is off.
  • Moved Yaw4 line frequency back to the new value of 8.65Hz (according to bandpass name, and Georgia's alog 46385), and the ADS error signal is of opposite sign.  The guardian puts the Yaw4 frequency to 8.70Hz, which has almost exactly 180deg difference in the bandpass phase from the correct frequency of 8.65Hz.  This is now fixed in the guardian.
    • The ADS OSC overview screens need to have more digits of precision on the displayed freqs.  We often set the freqs to 2 digits, but since the screens are only showing 1, perhaps the guardian-writer assumed that the correct value was 8.7Hz.  I have now done this for the ADS overview screen, and the oscillator locking screens. 
  • With the corrected Yaw4 freq, everything converges just fine.
  • There is a *huge* comb in all of the length degrees of freedom (MICH, PRCL, SRCL, DARM).  The ASC monitor lines that are not used in-loop are too large.  I had turned them off by hand (they'll still come on in guardian), but we need to turn them down.  The comb isn't from those lines.  The dithers are engaged right now (later lock), but no comb. The comb is from the weird MCL signals that you can see in the LocklossA.png below.
• Got to Nom LowNoise just fine, but lost lock after 4 min.  Fast lockloss, need to look into this one.
  • Looks like maybe a fast DARM ringup, but what is going on with the CARM / MCL signals??   See attached LocklossA.png.
  • The little spikes were there for the whole lock. 
• Next lock, acquiring easily.  Just a little PRM / SRM alignment tweaking after DRMI had caught lock (took ~5 min).
  • This time, lost lock after 13 min.  The spike things showed up in MCL_OUT_DQ at least once during this lock, but very briefly, then went away.  No sign of them being there long-term.
• May want to freeze ADS loops during COIL_DRIVERS state, looks like they get a kick while the transitions are happening.
• Running WFSreliefPast to the time last lock when we were at 2W DC readout, SOFT loops all converged.
• Another fast lockloss, but while powering up. 
• Later lock, looked at how long it takes the ADS loops to converge.  The answer is a really, really long time.  See attached ADS_slow_Convergence.png.  We should be able to speed this up by ~an order of magnitude.  We can have this low freq once we're locked, but we should get to our final pointing faster than 20 min.

PMC Trans is trending lower over the last week. Perhaps a remote alignment is in order.

For the record.

Addressed TCS Chillers (08:15-08:25 AM PST today)

• TCSy Chiller:  Had level reading of 0.7cm (almost empty)!  Needed 3.0 L to get it to 10.0cm.
• TCSx Chiller:  Had level of 29.0 cm & topped off to 30.0cm by adding 0.075 L.

Note:  TJ just informed me the spare chiller (which is staged next to other chillers) now looks like it works, so the plan is to swap it in for TCSy tomorrow during Maintenance.

Laser Status:
Front End Power is 32.22W (should be around 30 W)
70W Output Power is 70.16W
Front End Watch is GREEN
70W Watch is GREEN

PMC:
It has been locked 2 days, 19 hr 40 minutes (should be days/weeks)
Reflected power = 10.32Watts
Transmitted power = 54.45Watts
PowerSum = 64.77Watts.

FSS:
It has been locked for 0 days 0 hr and 10 min (should be days/weeks)
TPD[V] = 2.548V (min 0.9V)

ISS:
The diffracted power is around 2.6%
Last saturation event was 0 days 14 hours and 58 minutes ago (should be days/weeks)

Possible Issues:

TITLE: 01/14 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 9mph Gusts, 8mph 5min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.37 μm/s
QUICK SUMMARY:

• Jenne is relocking, made it to NLN twice
• Robert is getting ready for shaker tests

I have been wondering about the true input power, i.e. the input power incident on PRM, ever since the SRCL dither arm power measurement turned out so low.  

Conclusion
With an input power of 1.87 watts according to the PSL photodiode, we probably have around 1.55 watts incident on PRM, assuming an addition 21% unaccounted losses in the REFL A/B LF PD path.

Power Measurement Methods
I aligned PRM and the input optics, and misaligned the rest of the corner with 1.87 W reported from the PSL input power PD going into the IMC.

IM4 Trans
The easiest way would be to get Pinput would be via IM4 TRANS.  IM4 TRANS is calibrated into microwatts, IM4 (aka SM2) transmission is reported to be 2400 +- 200 ppm, and there's what I think is a 90:10 BS (ROM LH1) allowing 10% of the light going to IM4.  However, if we turn the crank here we end up with only 0.2 W, which is not possible.  This means that IM4 TRANS is not calibrated correctly, or the IM4 transmission path is actually around 8 times less transitive that I though.

REFL A/B LF
We believe that the REFL A/B LF PDs are correct based on the calibrated CARM shot noise.  We can use them to calibrate the correct input power.  The main issue here is if we use the REFL optical path (4 50:50 beamsplitters, 1 90:10 beamsplitter, one input faraday isolator, and one PRM) and assume no losses, we only get 1.19 W of true input power on the PRM.  This could be the case, but it's more likely that there are some unaccounted for losses on the REFL path.

PSL and IMC Transmission
If we trust the old numbers from P1500076 on the PSL and IMC transmission, we can make an estimate of the true input power.  We find that by varying the PSL and IMC transmission, we cannot reasonably recover the REFL A/B power levels we see.


PD Powers and Optic Transmissions Assumed
# Most taken from P1500076

# PD calibrated powers
PSL_INPUT = 1.87 # W
REFL_A = 7.3e-3 # W
REFL_B = 6.72e-3 # W
IM4_TRANS = 50.24e-6 # W

# PD uncertainties
dREFL_A = 0.04e-3
dREFL_B = 0.03e-3
dREFL_SUM = np.sqrt(dREFL_A**2 + dREFL_B**2)

# Transmissions
T50 = 0.5
T10 = 0.1
T_PSL = 0.953 # +- 0.013 PSL to MC1 transmission
T_IFI = 0.977 # +- 0.004 https://dcc.ligo.org/DocDB/0119/P1500076/003/Mueller16rsi-AdvIO3.pdf
T_IMC = 0.92  # +- 0.031
IMC_ModeMatching = 0.984 # 0.001
T_PSL_to_IFI = T_PSL * T_IMC * IMC_ModeMatching
T_IM4 = 2400e-6 # +- 200e-6 E070092
T_PRM = 0.031 #

# Trans Uncertainties
dT50 = 0.01
dT10 = 0.01
dT_PSL = 0.013
dT_IFI = 0.004
dT_IMC = 0.031
dIMC_ModeMatching = 0.001
dT_PSL_to_IFI = np.sqrt( T_PSL_to_IFI**2 * ((dT_PSL/T_PSL)**2 + (dT_IMC/T_IMC)**2 + (dIMC_ModeMatching/IMC_ModeMatching)**2) )
dT_IM4 = 200e-6