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.

TITLE: 08/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
INCOMING OPERATOR: Jeff B.
SHIFT SUMMARY: Lost lock for unknown reason. Had to make a significant adjustment to PRM in YAW to lock PRMI. Made it to NLN. While running a2l PI mode 27 ran away and I lost lock again. Succeeded in making it back to NLN and did not attempt to run a2l again. Set to observing. Succeeded in damping PI mode 27 early on.
Have transitioned the INJ_TRANS guardian back to INJECT_SUCCESS.
LOG:

14:47 UTC Closed terminal on nuc3 that was obscuring DARM on control room screenshots.
15:35 UTC Noticed DIAG_MAIN message stating that seismon is not updating. The GPS time does appear stuck at 1187621613.
16:10 UTC Betsy to optics lab.
16:26 UTC Lock loss.
16:32 UTC Gave Aidan remote access.
16:37 UTC Filiberto to mid Y.
17:03 UTC Filiberto back.
17:43 UTC NLN.
17:47 UTC Running a2l.
17:59 UTC Richard to CER.
18:05 UTC Lock loss. PI mode 27 ran away and I could not bring it back.
18:08 UTC Richard back.
18:31 UTC Visitor through gate to see Chandra.
18:32 UTC NLN.
18:35 UTC Observing.
Damped PI mode 27
18:59 UTC Nichole W. to mid X to retrieve Pelican cases.
19:09 UTC Nichole W. through main gate.
19:23 UTC Nichole W. back.
20:19 UTC Set INJ_TRANS to INJECT_SUCCESS.
20:51 UTC Elizabeth to mid Y to pick up parts.
21:14 UTC Elizabeth back.
21:26 UTC Travis and Liz to mechanical room (property control).
21:34 UTC Travis and Liz back.
21:50 UTC Jeff B. moving equipment from LSB to staging building.
22:08 UTC TJ to optics lab.
22:10 UTC Jeff B. done, moving yellow cart to OSB.
22:23 UTC TJ back.

Back to observing after lock loss at 16:26 UTC.

model restarts logged for Wed 23/Aug/2017 - Wed 16/Aug/2017 No restarts reported

[Aidan]

I've been investigating the apparent increase in range that occurred this morning when CO2X was turned off. This would seem to indicate that either (a) the CO2 laser is somehow misaligned/or deformed and causing a very poor lens, or (b) the present level of lensing (SELF heating + CO2) is too much. It's worth noting that the requested (and delivered) levels of CO2X laser power haven't changed significantly over the last four or five months.

If we assume (b) and also that the better range in the past is partially due to a better thermal state, then the conclusion is that either the effective CO2 lens or the SELF heating lens has increased.

I've gone back and looked at the HWSX spherical power data (H1:TCS-ITMX_HWS_PROBE_SPHERICAL_POWER) from two months around the period of the earthquake. The relevant value here is the spherical power change per lock (the difference between the upper and lower levels that are obvious in the time series which shows the transient lens from SELF heating and CO2 laser changes). There is an interesting period form 22-June to 7-July where this trends upwards by approximately 25 micro-diopters (or about 50%). This indicates that the apparent lens change per lock seen by the HWS is increasing significantly.

Two factors also play into this. (1) the CO2 laser is being turned on and off during this time (to keep the thermal state warm when the IFO has lost lock). However there is no significant change in the CO2 power level behaviour over the corresponding time range. (2) we know there is already a point absorber on ITMX as well as uniform absorption. The spherical power value is fitted to the low spatial-frequency lens. The presence of a known high spatial frequency point in the wavefront complicates this. For example, it's possible that the HWS alignment may be drifting and the point absorber is contributing more to the total spherical power value. This obviously needs to be investigated further by looking at the stored gradient fields.

However, it does seem that there is a real effect going on as the range got much better (~15% better) when the CO2 laser turned off. 

Laser Status:
SysStat is good
Front End Power is 33.8W (should be around 30 W)
HPO Output Power is 154.8W
Front End Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 9 days, 0 hr 11 minutes (should be days/weeks)
Reflected power = 16.77Watts
Transmitted power = 57.41Watts
PowerSum = 74.17Watts.

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

ISS:
The diffracted power is around 3.1% (should be 3-5%)
Last saturation event was 0 days 0 hours and 34 minutes ago (should be days/weeks)

Possible Issues:  None
 

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