I will be carrying out coincident hardware injections into L1 and H1, right after the O2 run ends. I've updated the schedule file and uploaded it to the injection svn, and checked it out onto the hardware injection machines. Here is the update to the schedule file:

1187734000 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/{ifo}/400_400_maxspin_hwinjcbc_1126259455_{ifo}.txt
1187734300 H1L1 INJECT_BURST_ACTIVE 1 0.5 config/Burst/Waveform/{ifo}/400_400_maxspin_hwinjcbc_1126259455_{ifo}.txt
1187734600 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/{ifo}/100_20_nospin_edgeon_hwinjcbc_1126259453_{ifo}.txt
1187734900 H1L1 INJECT_BURST_ACTIVE 1 0.5 config/Burst/Waveform/{ifo}/100_20_nospin_edgeon_hwinjcbc_1126259453_{ifo}.txt
1187735200 H1L1 INJECT_STOCHASTIC_ACTIVE 1 1.0 stoch/Waveform/SB_O2A_{ifo}.txt

These are four burst injections and one stochastic injection. The first one starts at 15:06:22 PDT.

patrick.thomas@zotws7:~$ check_sdf_snapfiles_status
WARNING: local modification on file /opt/rtcds/userapps/trunk/psl/h1/burtfiles/fss/h1pslfss_safe.snap
WARNING: local modification on file /opt/rtcds/userapps/trunk/psl/h1/burtfiles/fss/h1pslfss_safe.snap
WARNING: local modification on file /opt/rtcds/userapps/trunk/omc/h1/burtfiles/h1omc_OBSERVE.snap
WARNING: local modification on file /opt/rtcds/userapps/trunk/tcs/h1/burtfiles/h1tcscs_OBSERVE.snap


h1pslfss_safe.snap:
-Time:      Tue Aug 15 16:38:08 2017
+Time:      Fri Aug 25 00:27:45 2017
-H1:PSL-FSS_COMMON_GAIN 1 1.600000000000000e+01 1
+H1:PSL-FSS_COMMON_GAIN 1 1.602103999999996e+01 1


h1omc_OBSERVE:
-Time:      Tue Jul 18 12:07:52 2017
+Time:      Fri Aug 25 00:27:37 2017
-H1:LSC-ASAIR_A_RF45_I_OFFSET 1 -7.589000000000000e+01 1
+H1:LSC-ASAIR_A_RF45_I_OFFSET 1 -7.220000000000000e+01 1
-H1:LSC-ASAIR_A_RF45_Q_OFFSET 1 2.000000000000000e+01 1
+H1:LSC-ASAIR_A_RF45_Q_OFFSET 1 2.150000000000000e+01 1


h1tcscs_OBSERVE.snap:
-Time:      Tue Apr  4 18:11:09 2017
+Time:      Thu Aug 24 03:19:07 2017

Changes committed.

Have remained in observing. Adam M. has logged in remotely to prepare for hardware injections. No issues to report.

Thursday afternoon we had a brief but strong wind event--See first plot: 2 day's minute trends.  I had moved the roaming STS2 a week or more ago and now resides at position Roam9.  At the corner station the wind average touched on 20mph for maybe 90 minutes with a stable direction of about 170^o or ~from EndX toward the corner.  No non-wind seismic evident.

The second attachment shows the usual STS ASD comparisons between the Roaming HAM5 and the Detector used ITMY STSs, see 38184 for the Roam8 comparison and you can follow back from there.  Great news: for the X dof here at Roam9, the HAM5 STS shows several factors less floor tilting than ITMY starting at 30ishmHz; and, the Y dof is maybe no worse--is that band between 10 & 100mHz too much?

So bottom line Roam9 shows promise!

Times: RefTime is low wind, 25 Aug 0930 utc.  High wind is 0130 25 Aug.  XMLs in /ligo/home/hugh.radkins/STS_Seismometer_Studies

TITLE: 08/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY: No issues to report.

TITLE: 08/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
INCOMING OPERATOR: Patrick (subbing for Cheryl)
SHIFT SUMMARY:
LOG:

12:01UTC Confirmed wit Livingston. Injections node working properly. 1 hour standown in effect.

07:22 Radar, at LLO aclled to confirm a GRB. Verbal Alarms did not report, however the INJ_TRANS node was activated into the 1hr standown mode. That being said, tweaks were in process after a fresh lock.

TITLE: 08/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 48Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 9mph Gusts, 8mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

H1 was locking when I arrived. uSEI ws up to .2um/s and winds had been nearing 40mph earlier. OMC had to be massaged a bit before DC readout as it wouldn't lock. The AS90(purple)trace looked like te victim of some kind of offset as it was off scale until power increase where it came back down to familiar amplitudes. I ran a prelim a2l before setting the bit. the range was below 50Mpc as it was after I spoke to Aidan yesterday morning and he had me manually adjust the TCSX LASER power from preheat level (.500W) to .300W (see his aLog). He told me that we would probably go to .350W to claim a bit more of our already weakish range, so I did and it looks as if it may be a good move as our range has crept back up to 50+Mpc. Tweaking PI mode 28 (as usual).

  Lost lock at start of shift. Relocked quickly and without trouble. Shortly after lost lock a second time; but was unable to relock. Completed initial alignment, after overcoming some difficulty with MITCH_DARK step. Tried relocking but with no success. Breaks on FIND_IR (DIFF) or at CHECK_IR. Also having difficulty with IR DIFF not really found. Can hand tune and get a good spike, but still cannot really find IR with regularity. 

   Winds are up and gusting into the mid-30mph. X and Y microseism is up to 0.3um/s. BRS-X is damping. High winds are forecast until around 22:00PT. Holding the IFO in DOWN until the environment settles before trying relocking. 

   Getting high dust alarms at End-Y. Given the high winds and heavy wildfire smoke, this is not unexpected.      

FAMIS 6537

Added 100 mL H2O to crystal chiller.
Neither chiller had a fault light lit and both chillers read that the water level was OK.
Both canister filters appear white and free of debris.

09:29UTC "TCSX CO2 LASER output off" verbal happened. After a trip into the LVEA to find the FLOW light tripped on the controller I went into the mezzanine to check the chiller which was NOT tripped. I went back down and reset the controller and everything looked ok except for some SDF diffs in TCS_ITMX_CO2_PWR,TCS_ITMX_CO2, and DIAG_SDF nodes. I called Jason on the phone and he didn't have to much to say about some new Guardian stuff that has been added. I accepted te DIFFS that were showing and took a couple of screenshots.

10:32UTC LASER won't stay locked. It keeps dropping/searching/locking...rinse, lather, repeat. When it locks, the ready bit goes GREEN and I set the Intention bit but it just keeps falling out over and over again.

10:35UTC maybe it will hold this time?

10:46UTC nope

Rai W., Mike Z., Daniel S., Jeff K., Chandra R., Kyle R. 

Today the TMDS Gas Delivery Table was transported to the X-end VEA and set it up for operation.  The actual Surface Discharge Ionizer was mounted on a stand for today's demonstration purposes.  Nominally, it would be mounted to the dedicated TMDS port of BSC9's East Door.  The Vent/Purge air supply was ran and dry air supplied to the TMDS setup.  Prior to exposing the Ionizer to the conditioned air supply, the plumbing connection at the Ionizer was decoupled and connected to a test setup that facilitated the measurement of > 0.3 micron and > 0.5 micron particulate in the conditioned air. The air line was then re-coupled to the Ionizer.  An approximate 50/50 mix of Ethylene Glycol to Alcohol along with "chunks" of dry ice was used as a cold trap to the path.  

Rai W. gave an overview of the theory and a detailed tutorial as to the operation of the setup.  Daniel S. and Jeff K. noted details related to the ion production while Kyle R. and Chandra R. noted detail related to the vacuum related issues.  

The Ionizer setup performed satisfactorily (with caveats) at making comparable amounts of positive and negative ions.  

The plan now is to connect the Ionizer to BSC9 and perform an actual discharge of the ETMx during next Tuesday's maintenance day.  

My notes from today; 

1. Oscillations were noted and attributed to electronics design -> Daniel S. will address.  
2. Rai W. requested that we provide a means of support to take the weight of the Ionizer when mounted to the 1 1/2" valve on the BSC -> Kyle R. will address.  
3. Confirmation of the preferred means to pump to rough vacuum the X-end VE between cycles of discharge gas admission -> Chandra R. will address.  

J. Kissel

I've processed the data from LHO aLOG 38232, in which I was looking to see if the complex, high frequency dynamics found in the UIM (L1) stage of H1 SUSETMY (see LHO aLOG 31603).

Plots are attached; note that I've used the former 2016-11-17 data for ETMY. To guide the eye, I show the calibration group's dynamical model used during O2. Data shown with a coherence threshold of 0.75 or greater. I've not yet compared this against the unphysical, fitted update to the QUAD model that Brett developed for H1 SUS ETMY in CSWG aLOG 11197

It looks like 
- All suspensions see the "unknown" ~165 Hz resonance, though interestingly ITMY's mode appears to be split. ETMX and ITMY's are *strikingly* similar.
- only ETMY and ITMX show what Norna suspects is the "UIM blade bending mode" at ~110 Hz. ETMY's is indeed the ugliest.
- All but ETMX show evidence for resonances between 290 and 340 Hz, which are likely the (Suspension Point to Top Mass) wire violin mode fundamentals weakly excited by the UIM excitation. (see LHO aLOG 24917, T1300876)
- All suspensions show their (UIM to PUM) wire violin mode fundamentals between 410 and 470 Hz (see LHO aLOG 24917, T1300876)
- ETMY and ITMY's wire violin modes are *strikingly* similar; ITMX's modes are surprisingly low Q.
- We don't see the TOP to UIM wire violin modes likely because I didn't excite up to high enough a frequency; they're between ~500-510 Hz for ETMY (modeled at 495 Hz).


So now the question becomes -- what's the physical mechanism for this huge mystery resonance that's seen virtually identically in all QUADs? It seems quite a fundamental feature. Why is it split on ITMX?

It would be nice to have similarly detailed measurement of L1's QUADs, but all evidence from calibration measurements on L1's ETMY UIM stage point to this same feature (see the discrepancy between model and measurement for the UIM stage, e.g. in 2016-11-25_L1_SUSETMY_L1_actuation_stages.pdf LHO aLOG 29899). Further, it's *still there* before and after their Bounce/Roll mode Dampers (BRDs) have been installed (i.e. the same feature is seen in O1 and O2 CAL measurements; the above linked measurement was after BRD install). 

J. Kissel

I've checked the last suspensions for any sign of rubbing. Preliminary results look like "Nope." 

The data has been committed to SUS repo here:
/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM1/SAGM1/Data/
2017-08-08_1629_H1SUSIM1_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1629_H1SUSIM1_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1629_H1SUSIM1_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM2/SAGM1/Data/
2017-08-08_1714_H1SUSIM2_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1714_H1SUSIM2_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1714_H1SUSIM2_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM3/SAGM1/Data/
2017-08-08_1719_H1SUSIM3_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1719_H1SUSIM3_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1719_H1SUSIM3_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM4/SAGM1/Data/
2017-08-08_1741_H1SUSIM4_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1741_H1SUSIM4_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1741_H1SUSIM4_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM1/SAGM1/Data/
2017-08-08_1544_H1SUSOM1_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1544_H1SUSOM1_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1544_H1SUSOM1_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM2/SAGM1/Data/
2017-08-08_1546_H1SUSOM2_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1546_H1SUSOM2_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1546_H1SUSOM2_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/OM3/SAGM1/Data/
2017-08-08_1625_H1SUSOM3_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1625_H1SUSOM3_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1625_H1SUSOM3_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/RM1/SAGM1/Data/
2017-08-08_1516_H1SUSRM1_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1516_H1SUSRM1_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1516_H1SUSRM1_M1_WhiteNoise_Y_0p01to50Hz.xml

/ligo/svncommon/SusSVN/sus/trunk/HTTS/H1/RM2/SAGM1/Data/
2017-08-08_1520_H1SUSRM2_M1_WhiteNoise_L_0p01to50Hz.xml
2017-08-08_1520_H1SUSRM2_M1_WhiteNoise_P_0p01to50Hz.xml
2017-08-08_1520_H1SUSRM2_M1_WhiteNoise_Y_0p01to50Hz.xml

Will post results in due time, but my measurement processing / analysis / aLOGging queue is severely backed up.