J. Kissel

I've made a second, better attempt at tracking the long-time-scale thermalization of the IFO for the first few hours of a nominal low noise stretch -- originally attempted in LHO aLOG 53824. 

The data analysis will take some time, but here're are the measurement details. (All times are UTC on 2019-Dec-17)

    21:22 Test Start
    21:23 All lines on at conservative amplitude, SEI conf = USEISM, with SEI DIFF ON
    21:24 Hit Nominal Low Noise, all lines visible in DELTAL_EXT
    21:26:(15-30) Accidental brief turn off of (specifically) DARM lines
    21:40 Begin increase in line strength, and turn OFF of SEI DIFF
    22:03 Increase in some PCALY line heights to increase coherence
    23:20 All lines OFF, test done.

Hopefully, with all the changes in the lines during the measurement, the only effect will be that the coherence in the transfer function improves with time. During today's measurement, the microseism was well above the 90th percentile, in the ~1 um/sec range, so the 15 - 50 Hz data was rather glitchy, full of scattering arches.

Here're the list of frequencies driven (exactly, in Hz, bold frequencies are standard calibration lines):
    freqlist_darmx = [5.625,    7.45,    9.1,   18.9]
    freqlist_pcalx = [  5.45,    5.8,   7.25,  7.625,    8.9,  9.275, 18.725,  19.1, 49.775]
    freqlist_pcaly = [17.100, 410.30, 1083.7, 23.525,   25.3,  30.85, 49.625, 84.65,161.625]

Script to turn on PCAL EXC lines:
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Scripts/CALCS_FE/setup_sensingfunction_callinecombs.py

DTT template to turn on DARM EXC lines:
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/2019-12-17_H1DARMEXC_SpringMonitoring.xml

(To turn off all the extra lines, I just hit Abort on the DTT template, and used SDF to revert all the PCAL settings. The only thing that *didn't* work for was the PCALX high frequency roaming line frequency, which I had to restore by hand at it's current sweep point, 3001.3 Hz).

TITLE: 12/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Microseism is still fairly high, so staying in the USEISM state.  

Maintenance Activities were complete at 20:20utc (12:20pm).  Went straight into locking immediately at 20:24utc & made it to pseudo-NLN at 21:23utc (1:23pm) on the first lock!  Then JeffK took H1 for ~2hrs of calibration measurements.

Wind Fence work has been going on all day first at EX & then at EY.  There has been small moves with the manlift for this fence work (Heard that Robert says this noise is observable in DARM).
LOG:

• Contractors:  16:27 Ace toilets, 11:30-20:12 pepsi
• 15:58 PEM injection run 
• 16:04 SEI_CONF from USEISM to SC_OFF_NOBRSXY
  • H1 broke lock within seconds of this transition (related?)
• 16:10-17:54 EY PCal meas (Niko, Ethan)
  • Laser Hazard only during their activity.
• 16:20 Forklifting/craning in LVEA/Hibay (Tyler, Chris)
• 16:25 EX Core Drilling (Kyle)
• 16:25-19:56 HAM chamber transport tooling (Hugh, Scott)
• 16:27-16:42 EX fire alarm panels & batteries (Richard)
• 16:29 PSL FSS tune up in PSL room (Jason, Rick)
  • 16:33-17:27 Dust monitor maintenance (zero counts /flow rate check) (JeffB)
  • 17:03 IMC_LOCK taken to OFFLINE .  
  • 17:35-20:20 photos & scattered light check for PSL IO path (Cheryl, Jason)
• 16:30-17:34, and 17:53-18:28  Looking at EX RGA (Chandra)
• 16:41-20:02 CER ISC Cabling (fil)
  • possibly Marc assisting
• 17:04 Watchdog trip for ITMx ISI.  Untripped and taken to DAMPED (there is craning/forklifting in the area).
• 17:47 Move squeezer crystal to new spot (Daniel)
  • possibly Marc assisting
  • Squeezer bay was transitioned to Hazard and Safe.
• 17:50 LN2 to tank# "80" (aka EX's CP8)
• 18:01 Net Services beginning journey (@4mph) in manlift from corner to EX for Wind fence work (@MX at18:26, @EX at ~18:45)
• 18:16 LN2 to tank# "77" (aka MX's CP5)
• 19:10 DAQ restart complete (Dave)
• 19:33 EY Camera and viewport work (Robert)
• 20:11 LVEA Sweep (Betsy)
• 20:18 SEI_CONF to USEISM
• 20:24 Begin locking
  • 21:10 There was a manual intervention at ENGAGE_DC_VIOLINS!  Jason happened to walk in at this point coinincidentally, too!  He asked me to turn ON the ISS Autolocker (he forgot to turn this ON after their FSS work.  I was able to turn this ON, H1 remained lock, and Guardian then continued on to INCREASE POWER.
• 21:22 ISC_LOCK at CLOSE_BEAM_DIVERTERS:  Recovered from Maintenance & handed over to JeffK for CALIBRATION
  • Observatory Mode switched to CALIBRATION
  • 21:22 Jeff begins ~2-hrs of Calibration measurements
• 21:34 VIOLIN_DAMPING node LOAD was run (Rahul, Cheryl)
• 21:45-23:24 Robert to EY for camera/viewport work
• 22:09 Kyle to MY
• 23:20 CALIBRATION measurement ends (JeffK)
• 23:20-23:36 Switch to COMMISSIONING time for Measurement (Sheila/Sudarshan)
• 23:24 EY swept & returning (Robert)
• 23:39 OBSERVING!
• 23:39 Wind fence person begins manlift trip back to the corner station from EY.  Probably take about 45min.

The DBB, which is not currently on the PSL, was blocking some stray light, so a black metal panel was added to catch the llight instead.  A reflection from a PD has shifted, and a razor blade dump was added to catch some light that was hitting the edge of a lens, where the beam is dumped on the lens mount (IO EOM pickoff).   Image attached is of the new razor blade beam dump.

R. Savage, J. Oberling

This morning we tuned up the FSS RefCav beam path in advance of the holiday break.  The TPD had been trending down over the last couple of weeks, so we wanted to get things tuned up to hopefully avoid the TPD falling too low in the middle of the break.  This work was done with the ISS OFF.

We began by performing a power budget to look for any areas where it was obvious we were losing power.

• WP04 Input: 148 mW
• AOM Input: 145 mW
• AOM Output (measured at face of M25): 100 mW
• EOM Input: 59 mW
• EOM Output: 59 mW

With the above powers we find that the AOM diffraction efficiency is lower than it generally is.  On the first pass (AOM Output/AOM Input) we have a 69% diffraction efficiency; on the 2nd pass (EOM Input/AOM Output) we have a diffraction efficiency of 59%.  To improve this, the AOM alignment is adjusted to peak up the AOM Output, then M25 adjusted to peak up the EOM input.  We were only able to increase the AOM Output by ~1 mW by adjusting the angle of the AOM, but gained ~13 mW by adjusting the vertical position of the AOM higher (~1/4 - 1/2 turn on the vertical adjustment knobs, so not much adjustment needed at all).  This was the most we could get with AOM adjustments; the AOM output power increased to 114 mW, therefore increasing our 1st pass diffraction efficiency to 78.6%.  We measured this at 75.5% in November, so we're good to go here.  We now had 34 mW input into the FSS EOM, which is lower than when we started; this makes sense, as we adjusted the position of the AOM to peak the 1st pass diffraction efficiency but had not yet realigned the 2nd pass.  Mirror M25 was adjusted to peak up the power incident into the EOM.  When finished we had 85 mW incident on the EOM, which gives a 2nd pass diffraction efficiency of 74.6%.

At this point Rick noticed that the beam spot on the viewer card we were using looked odd, almost like a HG01 mode.  We traced the beam back through the beam path, looking for dirty optics along the way.  We noticed that the 2nd FSS mode matching lens, L10, looked really dirty.  We attempted to clean it in situ, but that didn't work out so well so we removed the lens and cleaned it.  We also noticed some spots on WP05 and M25, so we cleaned these optics as well (done in situ).  This complete, the beam on the card looked a good deal better but still had a bit of HG01 look to it.  Pressed for time, we decided to move on and see how the RefCav locked before persuing this more.  Before relocking the RefCav, the beam alignment through the EOM was checked and found to be a little off horizontally on the EOM output aperture.  An iterative alignment between mirror M26 and the EOM itself was used to fix this; this was done to hold the beam near the center of the RefCav Refl camera, our rough alignment reference.  That complete, we used the autolocker to lock the RefCav, which locked with no issues.  The picomotor-controlled mirror mounts were used to peak up the TPD; when done, we had a RefCav TPD of 5.58 V.  To finish, we measured the TF of the FSS, see attachment (if the phase plot looks weird, that's only because it was unwrapped).  With the gains unchanged (common gain at 20, fast gain at 16), we have a UGF of 487 kHz, so no gain adjustment was needed (recall that the UGF of the FSS is measured at a magnitude of -10dB due to the electronics of the 2nd gen TTFSS we currently use).  This completed the FSS tune-up.  As of right now, the RefCav TPD is reading 5.66 V.

Finally, I turned both power watchdogs ON (we turn them off when working in the enclosure) at 20:30 UTC (12:30 PST), thereby completing FAMIS 10741.

I do want to note one interesting thing.  We forgot to turn the ISS 1st loop back ON when we were done.  Once I remembered to do this IFO recovery had already started, and Guardian was at the INCREASE POWER stage.  This means the locking sequence survived all the way to INCREASE POWER with no 1st loop ISS engaged (the 2nd loop is generally engaged shortly after DRMI acquisition, I did not notice if it was engaged with no 1st loop); DARM did have a fairly ugly, and expected, high-frequency noise hump.  The 1st loop engaged with zero issues, didn't even break the lock.  The noise hump went away and Guardian continued on its merry way like nothing had happened.  Huh.  *nods head sagely*

Niko, Ethan

Today (12/17/19), a standard PCal endstation calibration measurement was undertaken. The results of the calculation are consistent with previous calibration measurements of the endstation. Some attached documents are the procedure document (with the measurement times), the trends documents with the final datapoint in each plot corresponding to today's measurement, WS/GS responsivity trends document, and the pictures of the alignment of the beams on the RX PD. The alignment seems similar to the last time it was checked (alog 53373). 

Some things to note:

1. Jeff K was inadvertently changing the gain on the optical follower servo at EY during the calibration. The times for this are

• OFS gain offset changes introduced: 2019-12-17 17:05:40 UTC => GPS time 1260637558.874
• OFS gain offset changes reverted: 2019-12-17 17:09:20 UTC => GPS time 1260637778.187

These times align with one of the sets of measurements at the endstation, labelled measurement 2, when the WS is in the outer beam of the TX module. This is seen in the data during the measurement, see the middle two panels of attached WS_at_TX.png. However, this has no effect on the calibration, as these two timeseries are taken as a ratio. It does, however, affect the measurement of the power imbalance (not used in the calibration), see power_imbalance.pdf. 

2. The portable temperature probe was moved from the TX module to the RX module. This is seen in the attached photos labelled temperature_probe_*.png. The reason for moving the probe is to coordinate reducing uncertainty in the RX PD responsivity due to temperature, as this is the photodetector used for IFO calibration.

Sheila Marc Daniel

We changed the OPO crystal position by a random amount.

New OPO parameters:

• T = 33.316°C (before 33.296°C)
• OPO REFL DC unlocked = 2.1 mW
• OPO REFL DC locked = 0.53 mW (25%)
• SHG Launch ~ 5.3 mW

Before the crystal move we were at the maximum SHG launch power of 20mW with 2.6 mW on OPO REFL DC  and weren't able to maintain the OPO green pump power anymore.  We now need 4x less power.

The DMT production computers have been patched and rebooted to bring in the latest security patches and production updates from lscsoft. The GDS and calibration software on the DMT were not changed. Everything on the DMT is working and this completes WP #8497.

J. Kissel, D. Barker, T. Shaffer,
WP 8500

I've instantiated the IFO_CALIB guardian for general use of automatic calibration measurements in the future. The node was originally constructed by Timesh at LLO, e.g. LHO aLOG 44318.

The source code lives in 
    /opt/rtcds/userapps/release/cal/h1/guardian/IFO_CALIB.py
At the moment, it only parameter file it references is
    /opt/rtcds/userapps/release/isc/h1/guardian/lscparams.py

TJ has added this node to the guardian overview screens, as indicated in LHO aLOG 53933.

I'm not yet confident that this has been added to the list of guardians to check the happiness of before observing. We'll check that later.

guardutil print IFO_CALIB     # check for gross syntax errors or bad references before starting
guardctrl enable IFO_CALIB    # instantiate the channel space for the node
guardctrl start IFO_CALIB     # start the node

Instantiating the channel space requires a DAQ restart, which has been done.

I have semi automated the analysis of the high frequency roaming lines. The timestamp for these roaming lines can be found here: LHO alog 53624

The scripts used to obtain the data and convert it into appropriate format for processing lives here:  svn/aligocalibration/trunk/Runs/O3/H1/Scripts/HighFrequency/

The results are saved at the following location: svn/aligocalibration/trunk/Runs/O3/H1/Measurements/HighFrequency/

The instructions on how to run the code can be found in README file here: svn/aligocalibration/trunk/Runs/O3/H1/Scripts/HighFrequency/README

TITLE: 12/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    SEI_CONF state: SC_OFF_NOBRSXY
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.90 μm/s 
QUICK SUMMARY:

Well into Maintenance!!!
H1 broke lock as soon as I transitioned to SC_OFF_NOBRSXY....ending a 55hr36min lock.

TITLE: 12/17 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Microseism is pretty high
LOG:

8:25 Knocked out of observe for about a minute by transitioning SEI_CONF to USEISM, I was able to catch the filter banks and unmonitor, this shouldn't happen again

TITLE: 12/17 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 108Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Quiet shift with the useism still climbing. 47.5 hour lock.
LOG:

• 0144 Out of Observing, accidental template opening
• 0144 Back to Observing

I added the IFO_CALIB node to the two guardian overviews in preparation for the addition of this node tomorrow.

Since the node hasn't been created or started yet, it will be white until then.

Sheila pointed out that we're having a lot of scattered light for the microseism level we've got, and at the Commish meeting asked about our sensor correction / seismic configuration.

Since the CPS differential is designed to help at the wind and earthquake band, it makes some sacrifices of isolation performance in the microseism band.  As a test, I've turned off the CPS differential system by ramping down the final output gain (H1:ISI-DIFF_CONTROL_BIT to zero, ramping down over 10 seconds), and we'll see if we see a bit less scattering. 

I took the IFO out of observing for a few minutes to make the transition, accepted the SDF diff, and went back to observing.  Note that I left the SEI_DIFF guardian in its nominal state which might make one think that it's on, but since the Run state does nothing but return True, it is not writing to that EPICS channel.  I didn't want to edit the guardian's nominal state, which is why I've left it alone.

• LHO completes 113+ hour lock stretch! With only brief periods outside of observing mode, ending for Tuesday maintenance (shortly after 1260000000 turn-over): alog 53781 , alog 53788
• PSL chiller leak brought down the PSL for much of Wednesday (~16 hours) - alog 53831, alog 53846
• Duty cycle: 80.5% (low noise, ISC_LOCK_NOMINAL), 78.7% (Observing).
• Range: Steady at 110-115 Mpc throughout observing time.
• ETMY violin modes 18 & 20 (at 1kHz) were ringing up; much effort put into damping them. It produced lots of omicron glitches at 1 kHz, through Wednesday Dec 11. Much reduced after PSL chiller recovery.
• Lock stretches on Thursday through Saturday (Dec 12-14) had greatly elevated noise and glitchiness in the 20-35 Hz band (around ASC dither system (ADS) lines), associated with high microseism -induced scattering arches.
• Lock losses on Thursday, Friday and Saturday; cause unknown. Lock loss on Sunday due to mag 6.9 EQ in Phillipines. All four recovered low noise in ~2 hours.
• Readout of squeezer BP3 (500-900 Hz) still corrupted by excess noise.
• Four CBC public alerts, two were retracted. S191215w is a nice BBH.
• EX wind fence complete, pics in alog 53826.
• For more information see https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20191209

Following up from the last alog.

With the UIM dyanamics filter ready I propagated it through a set of new tagged sus models. I made a set of three to help make an informed decision on how to treat the new UIM dynamics - the complication being that there appears to be dynamics around the violin modes. I have split off a second tagsusdynamicalmodel.m so I don't interfere with livingston using the file.

I have created the following files using /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/tagsusdynamicalmodel_h1.m

/ligo/svncommon/SusSVN/sus/trunk/Common/SusModelTags/Matlab/

quadmodelproduction-rev9944_ssmake4pv2eMB5f_fiber-rev8442_h1etmx-rev10093_h1etmx_options-rev10093_released-2019-12-12.mat
quadmodelproduction-rev9944_ssmake4pv2eMB5f_fiber-rev8442_h1etmx-rev10090_h1etmx_options-rev10090_released-2019-12-12_noUIMdyn.mat
quadmodelproduction-rev9944_ssmake4pv2eMB5f_fiber-rev8442_h1etmx-rev10093_h1etmx_options-rev10093_released-2019-12-12_noviolins.mat

And from these I have generated the following files using /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/pyDARM/matlab_scripts/export_AAAI_SUS.m:

/ligo/svncommon/CalSVN/aligocalibration/trunk/Common/pyDARM/matlab_scripts/

H1susdata_O3_new.mat
H1susdata_O3_new_noUIMdyn.mat
H1susdata_O3_new_noviolins.mat

Using these I can compare before are afters, namely:

In the case when I plotted against no violins, the MATLAB removes the highest most zero in the UIM dynamics, making the TF look like its going down more than it should be (an effective extra 1/f term). This is a problem in the current workflow that takes the tagged model and splits it up into low frequency terms and the violin terms, where I'd need to add a separate operation that takes the tagged model that has no violin modes to split off these dynamics. Looks like I will have to rethink.

Also the low frequency features are being changed by a bit - seems even matlab has its limits of tolerance when it comes to how many poles and zeros it can play with at a time.

I think a better approach is to have the dynamics added into the "H1susdata_O3" matrix directly by export_AAAI_SUS.m, and make no changes to the tagged susmodels as they stand. At the end of the day I am always drawing from the same file into which I have saved my dynamics... I can just do that later down the line even for the foton file.

Vlad and Jenne,

From the summary pages, as of 0200 UTC 20191204, the 3rd bandpass region of the sqeezing has beern reporting increasingly degrading squeezing starting at near -2dB, to sitting at above +2dB currently.

Jenne nagivated the the sitemap to find that this band corresponds to the region between 500-900 Hz, and suggested I run a BruCo before this happened, as well as more recently to help find an issue, to hopefully spot a noise contributor to DARM in that band.

I am currently running a BruCo - and should be able to inspect the data tomorrow.

In the attachments you can see the relevant plot of this band creeping up over the last two days. (its the green one)