Daniel, Thomas, Stefan

- We added a button to the TCS-HWS medm screen that plots the contour difference between a reference time and the current time. For now the reference time is taken from /opt/rtcds/userapps/release/tcs/common/medm/referencetimeITMY.txt

- We really want a streaming version of this working, but the current streaming scripts are inoperational (and some of them interfere with the EPICS logging)

- With that we did a quick shot with the CO2 laser - it didn't look good... (plot 1) It almost looks like CO2 heating fringes... we will have to go back to this.

- We next wanted to verify that none of this is the fault of the HWS, so we did a ring heater run. That one looked reasonably well (plot 2), both in circularity and centering (note that the centering is sensitive to SR3 alignment).

- The optics are now cooling down over night - we will look at the CO2 heating again tomorrow morning.

[Jenne, Hang, Gabriele]

We had DRMI locked for long periods earlier today, and worked some on improving the 72MHz ASC sensing matrix (Hang will comment with details).  After concluding that we had done as much as reasonable with that work, we decided to try walking the PRC spots to see if we could find an alignment that had better sideband buildups.  This is when it all went wrong....

I was thinking that we could use the ISC_LOCK states that are meant for moving the PRC spots (you move a specified slider, eg. IM3 for moving the spot on PRM, and the script moves other sliders to make the cavity axis only move the spot on the chosen mirror.)  But, that required taking the ISC_LOCK guardian out of the Paused mode.  And, I hadn't already selected the PRM_SPOT_MOVE state, so we ran the ISC_LOCK DOWN state.  One of the things that this does is request the TCS CO2 lasers to go to the PREHEATING state.  Since TVo and Danny turned the CO2 lasers on earlier today (and at the time confirmed that 0W were being injected into the chambers), this preheating state was able to start sending several hundred mW to each of the ITMs.  At some point we lost lock after touching a few of the alignment sliders, but then have not been able to lock DRMI with good buildups since then.  After about an hour, I realized that the CO2 laser power was one of the things that had changed with the ISC_LOCK DOWN state, and requested that the CO2 lasers' rotation stages send 0W into the vacuum.  There really shouldn't be anything else in there that affects the alignment. 

However, even after more than an hour or so, we still cannot lock DRMI with good sideband buildups.  We have gone back to the witness sensor positions for all the optics for several different times when we had good DRMI locks both this afternoon and Hang's locks yesterday (these are all pretty similar to one another).  When we do this, we see some really bad pitch modes flash on the AS AIR camera.  We are able to get POPAIR_18 values of about 25% of what we had been achieving earlier this afternoon (POPAIR_B_RF18_I_NORM_MON of only ~8 counts rather than the ~32 we were getting earlier), but not more than that. 

It's very unclear to me why we can't get better alignment right now.  I'm sure there's something obvious that I'm missing, but I don't know what.  At this point, I think Hang and I agree that it makes sense to let the PSL team do their work, and then once we have the laser back we can open up the Xarm beam tube, and really set our input pointing to that (we didn't finish doing this during last week's peek), and go from there.

J. Kissel, G. Mansell

Georgia has found that ETMX optical lever was reporting unpleasantly large  ~0.5 Hz motion. While I warned her against the on-going issues with ETMX's excessive RX /RY motion (LHO aLOG 42711, FRS Ticket 11021), I also was reminded of earlier today when Fil and Ken were at the end stations killing electronics, which drove Jim to turn off all sensor correction.

I've restored the SEI_CONFIG manager to WINDY.

All platforms except for ETMY went to "CONFIG_FIR" which I think is right, browsing through the platforms. ETMY failed because it suggests BRSY is at fault. BRSY says it's at fault because its FILTERS [are] NOT READY. I don't know what this means, so I'll leave it for team SEI to debug tomorrow.

TVo, Danny Vander-Hyde, and I went to EX today to pull out the old HWS optics and place the new ones in their rough positions. The new LED light source was placed on the table and routed to the feedthrough panel, but we need to make a longer M8 cable to reach the controller. Also, the controller needs a power supply. We will tackle these issues and then start aligning.

I left the ALS laser shuttered since it doesn't seem like anyone needs it tonight.

ChrisS, ThomasV, RickS

Bubba and the Apollo crew moved the LIGO India "Front End" laser crate from the shelves in the Ymid station to floor level early this morning (thank you!).

Chris and I extracted the 35-W laser and moved it to the OSB receiving area.

After removing packing material and wiping down the internal plastic film wrapping, Thomas and I moved it to outside the H1 Laser Area Enclosure in preparation for installation tomorrow, in case we decide to proceed with that effort.

This morning I did a quick inspection of the spare 3IFO 35W FE laser (it lives in the H1 Laser Diode Room for cleanliness purposes).  All of the parts are there, but there is one issue with it: the NPRO is not aligned to the MOPA, making this laser currently unusable.  Before this laser can be utilized in any fashion the NPRO needs to be aligned to the MOPA and the mode matching adjusted as needed.  To make this clear, Rick is adding a tag (shown in the attached picture) indicating that the NPRO is not aligned to the amplifier; this laser should not be used until this alignment is complete.

Laser Status:
SysStat is good
Front End Power is -0.002217W (should be around 30 W)
HPO Output Power is 0.4705W
Front End Watch is RED
HPO Watch is RED

PMC:
It has been locked 3 days, 6 hr 19 minutes (should be days/weeks)
Reflected power = 28.8Watts
Transmitted power = 33.62Watts
PowerSum = 62.42Watts.

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

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

Possible Issues:
Front End Power is Low
PMC reflected power is high
ISS diffracted power is Low
LRA out of range, see SYSSTAT.adl

WP 7694
WP 6052
WP 7044

With S&K Electric working on new receptacles for CP ion pumps, the following items had to be moved or disconnected from the vacuum dedicated circuits until work is complete:

1. VAC - ION and NEG pumps
2. BRS - controller
3. ISC table enclosure
4. PEM/BRS STS
5. ESD LN Electronics
6. CPS fanout chassis
7. Comtrol- weather station/dust monitor

The ESD and CPS electronics were switched back to rack power and the temporary power supplies removed.

J. Kissel, J. Driggers, H. Yu

While I was exploring signals for balancing the coils fro MC2, I found that we were sending the same control IMC ASC P and Y signals to all three stages of MC2 (see 3rd attachment showing ASDs of test points just upstream of the LOCK filter banks for stage, after the hierarchy split). Which stage gets what signal can be controlled by output switches which are just downstream of the LOCK filters for each stage (see green highlighted switches on the overview screen; 4th attachment). 

Trending reveals that, while the M3 stage output switches had been turned ON on Jun 21 2018 at 14:36 PDT (21:36 UTC), where they had been OFF up until then during and since O2. The M2 stage output switches are a little bit more confusingly ON during O2, and only briefly off between Jan 2018 and Feb 2018 -- but there have been no distribution filters (typically a simply integrator) on the M2 or M1 stages for P and Y which delineates at what frequency the control signal has authority at each stage. See 1st attachment, showing a 360 day trend, which takes us back to Jul of 2017, during O2.

Even more suspiciously, there *is* an "1:0", 1 Hz integrator in each FM2 bank of MC2's M1 LOCK bank, but they haven't been turned on ever (at least not back through prior to the beginning of O2). See 2nd attachment, showing the SWSTAT for this filter bank. The bank is alternating between having the following states:

    SWSTAT            What Switches 
    Binary Value      Are ON

    32768             DEC
    33792             DEC, INP
    36864             DEC, OUT
    37888             DEC, INP, OUT    (The apparent nominal state during O2)

The SWSTAT never goes higher that 37888, implying that the filter state INP, FM2, OUT, DEC, which is 300034, never happened. I checked back as far as 2016, and didn't see this state ever occur.

For now, pending further investigation, we're leaving the H1SUSMC2 M2 and M3 stages P and Y output switches OFF, and Jenne accepted these changes into the SDF system.

This is a follow up to:

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=42730

After a week of observing this change it does not appear to have had an impact in the retransmit rate of h1fw2.  Comparing the producer receive times from h1fw2 & h1fw1 shows that h1fw2 has a noisier signal than h1fw1.

We will probably not push this change from h1fw2 into the production system.

I have attached 3 plots.

1. The retransmits over the last 8 days.  The point of interest is the right most line, which is the retransmits since the config change.
2. A 3hr sample of the producer receive time on h1fw2 & h1fw1 for Monday 2 July 2018 (pre config change on h1fw2).
3. A 3hr sample of the producer receive time on h1fw2 & h1fw2 for Monday 9 July 2018 (post config change on h1fw2).

The h1fw2 signal looks a little cleaner than last week, but still is showing large spikes, spikes that are larger than h1fw1.  So while this may be a contributing factor to h1fw2, it appears to not be an issue on h1fw1 (which is newer hardware and cpu).

   Found many IPC errors on the CDS Overview screen. Used the universal Diag Reset button to clear the errors and they have not returned. Attached is a screen shot of the nodes that were in error before the reset. 

Peter K., Robert s., Jeff B.

   This morning Peter and Jeff moved the chiller bypass from inside the PSL enclosure to the Chiller Room. We fully closed off the bypass valve on the PSL manifold (inside the PSL enclosure) and opened up the bypass between the Crystal Chiller supply and return lines. Next we adjusted the bypass valve in the Chiller Room and the pressure regulators on the Front End, Shutter, and 70W amp circuits to bring them back to their proper flow rates. 

   After making the changes, Robert ran a noise check. The noise is OK at lower frequencies, and has improved at higher frequencies. There is still some work needed to lower the noise in the 400 to 900 hertz bands.

Attached are two RGA scans:

• Scan at 10:30am before the cryopump was valved in; 2000 l/s turbo pump only
• Scan at 3pm, about 2.5 hrs after CP was valved in, with 2000 l/s turbo also pumping on main volume

Later in the week we will collect more scans to see how the water is falling.

Total pressure at EX before valving in CP was 5e-7 Torr and is now 5e-8 Torr, as expected, as a result of a full order of magnitude decrease in water partial pressure.

Note that the short CPs allow 30% of water molecules to escape past the trap and into BT; long CPs in corner allow only 3% transmission.

EX is currently isolated from BT with a soft closure of GV19. We typically don't operate in this state (BT valve soft closed with a VEA turbo valved in) in case the turbo pump fails and back streams into main volume, possibly seeping past GV o-ring.

Craig, Sheila, T Vo

We installed the OMC trans camera this afternoon.  We had to use a normal post/post holder mount, not the fancy adjustable camera mounts, because we needed to mount the camera higher than those mounts would allow us to.  The beam should be on the camera but we don't see anything in CDS.  We didn't see anything on the laptop when we pointed the camera at the room lights, so it is probably a problem of what is connected where.