I came in to lock the IFO for Adam's injections which are scheduled for 2 hours from now, (38380), but have had about 4 BS ISI ST1 CPS trips in the last hour. 

Two of these might have happened while the BS was isolating stage 2 (I have not double checked) but at least one happened while we were just sitting in CHECK_IR (no feedback to the BS sus, ISI state should not have been changing).  The screenshot attached is for that most recent trip in CHECK_IR

Edit:  Made it to a fully locked interferometer and was engagning ASC when it happened again, again it was a glitch in the ST1 H3 CPS.  Second screenshot 

Edit again: This seems very similar to the situation described in 37499, 37522 the third screenshot shows the glitches getting worse over the last 1:40 minutes.  Jim describes power cycling the satlite racks which seemed to make the problem go away last time. 

Another update: I power cycled the 3 top chassis in the CER rack SEI C5, these are labeled BSC ISI interface chassis and have cables going to BSC2 CPSs, GS13s and L4C's.  The ISI has not tripped in about 20 minutes, I am relocking but paused to damp violin modes.

Last O2 report:

model restarts logged for Fri 25/Aug/2017
2017_08_25 17:06 h1sysecatc1plc1sdf
2017_08_25 17:06 h1sysecatc1plc2sdf
2017_08_25 17:06 h1sysecatc1plc3sdf
2017_08_25 17:06 h1sysecatx1plc1sdf
2017_08_25 17:06 h1sysecatx1plc2sdf
2017_08_25 17:06 h1sysecatx1plc3sdf
2017_08_25 17:07 h1sysecaty1plc1sdf
2017_08_25 17:07 h1sysecaty1plc2sdf
2017_08_25 17:07 h1sysecaty1plc3sdf
2017_08_25 17:09 h1pslopcsdf
2017_08_25 17:13 h1hpipumpctrlsdf

50 minutes after the end of O2, h1build froze up and required a reboot. The Beckhoff SDF models were then restarted.

model restarts logged for Thu 24/Aug/2017 No restarts reported

Sheila plans to come in and lock the IFO this afternoon, so that I can try to finish these detchar safety injections. I've schedule 7 injections, the first one will begin at 16:06:22 PDT, and the last at 16:51:22 PDT. Here is the update to the schedule:

1187824000 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187824450 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187824900 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187825350 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187825800 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187826250 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187826700 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt

The IFO should be left out of observation mode. Also, I'm not sure if the PCALX 1500Hz line gets turned back on, but this also needs to be turned off. Simply typing the following on the command line will do the trick:

caput H1:CAL-PCALX_PCALOSC1_OSC_SINGAIN 0
caput H1:CAL-PCALX_PCALOSC1_OSC_COSGAIN 0

Thomas Vo, Sheila Dwyer

We started out pre vent/discharging measurements in tonight.  

• First we ran the automated version of the ESD actuation strength measurements described using the attached script, we got data for all 4 ESDs.  
• We made an attempt to transition DARM control to the ITMX ESD but noticed that we are missing IPCs that would allow us to send DARM to the ITMs. 
• We intentionally unlocked the IFO so Thomas could take some HWS measurements for the ETMs, but has difficulty getting a reference at DC readout. While we were moving the PZT misalingment biases the interferometer became misalinged and unlocked.  We will need to investigate this before continuteing the HWS measurements. 

The CA sdf systems stopped.  After a quick investigation it was found that the server running the SDF systems had locked up.  H1build had suffered a kernel panic and needed to be restarted.

I manually started the following SDF models:

h1sysecatc1plc1sdf 
h1sysecatc1plc2sdf 
h1sysecatc1plc3sdf 
h1sysecatx1plc1sdf 
h1sysecatx1plc2sdf 
h1sysecatx1plc3sdf 
h1sysecaty1plc1sdf 
h1sysecaty1plc2sdf 
h1sysecaty1plc3sdf
h1pslopcsdf 
h1hpipumpctrlsdf 

Attached are photos for our End Of O2 Toast at LHO!  :)

TITLE: 08/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY: Last shift of O2! No issues until Beckhoff SDF died during Adam's detchar safety injections. Jonathan has restarted h1build and it is currently running a file system check. Intention bit set to commissioning. Observatory mode set to commissioning. IFO at NLN.
LOG:

16:02 UTC Powercycled video2. MEDM screen updates were intermittent.
16:07 UTC Restarted the range integrand DMT that is displayed on video0. It had been running locally on video0 instead of through ssh on nuc6.
17:23 UTC Gave Adam M. remote access to cdsssh and h1hwinj1.
18:50 UTC GRB verbal alarm. Confirmed with LLO.
15:00 UTC End of O2! Set observatory mode to calibration. Changed INJ_TRANS guardian node to INJECT_SUCCESS.
22:43 UTC Adam M. starting detchar safety injections. Set intent bit to commissioning. HFD to mid X to check on RFAIR box.
~23:09 UTC Beckhoff SDF died. IFO_LOCK guardian node went into error (lost connection to SDF channels). Adam's injections interrupted. Jonathan investigating.
23:23 UTC Jonathan restarted h1build and it is running a file system check. Adam canceling remainder of injections. Transitioned observatory mode to commissioning.

While the LHO folk are celebrating the end of the O2 run, I decided to sneak in some detchar safety injections. Here is the update to the schedule file:

1187736700 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187737150 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187737600 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187738050 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187738500 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt

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:

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).