Locked on 00 and started the script at about Jun 13 2018 04:38:34 UTC (1212899932)

Sheila Craig Jenne Georgia

This afternoon we started preparing for a loss measurement of the y-arm at 1064. We aligned the arm in green, adjusting ETMY, the TMSY, and ITMY. We saw some Y-arm IR flashes on ASC-Y_TR_A and B, and maximised these with PR2 and IM4. Craig and Sheila used SR2 to align to the camera on ISCT6, however the beam looks smudgey when it centred on the camera, perhaps it is clipping somewhere. We will continue this tomorrow once ITMY has settled down after Team Hartmann’s ring heater test.

Sheila, Hang

We tried to do the PRM local length to pitch decoupling, similar to what LLO had done (LLO:31459). We measured both the M2L -> M3P and M2P -> M3P transfer functions, and fitted them using Lee's IIRrational.  The filters were loaded into the PRM_M2_DRIVEALIGN_L2P filter bank. To engage the L2A, we should put a gain of -1. 

The first and second plots were measured TFs. They were left in [ct/ct] as this was sufficient for filter design. 

We also tested the effectiveness of the filter using past data (starting gps: 1186963218; duration: 2048 s). We used the fitted coefficients to filter SUS-PRM_M2_LOCK_L_OUT16 and then subtracted the results from SUS-PRM_M3_WIT_P_DQ. We further computed the residual coherence between PRM_PIT and CHARD_PIT. The result was shown in the third plot. The blue trace was the original coherence between PRM_PIT and CHARD_PIT and the red trace was after the M2_L decoupling. It seemed to reduced the coherence around 1 Hz significantly.

However, the measured suspension M2L->M3P did not quite match the optimal Wiener filter computed for the L2P decoupling from the past data with the full ifo locked, whose result was shown in the light cyan curve (the reason we start with M2 instead of M1 was that the M1 suspension L2A deviated from the Wiener result even more than M2). We might want to switch to the Wiener results in the future for better decoupling...

(Mark D, Tyler G)

A new rack was installed at each end station.  They were installed on one of the walls of the mechanical room for each station, on the north wall for the Y End, and the west wall for the X End.  The racks are to consolidate vacuum controllers for NEGs and IPs.

Work per WP 7646.

TITLE: 06/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: Maintenance day. As well as work on PSL FSS, ITM HWS, and much more commissioning.
LOG: See attached

Added new suspension nodes for the OPO and the OFI. They are running a different version of sustools than the other sus nodes until I get the chance to restart the  rest of the nodes.

I ran through all of the states and even tripped the suspensions and all went well. This speaks for both the nodes and for sustools.

Added them to the Guardian overview, as well as I added a compact version of the overview to the sitemap. See attached.

Measured noise on line delivering 118 Mhz to the EOM, and the line delivering 9 Mhz to the EOM driver. 118 Mhz signal was strongest noise source present on both lines. Replaced 118 Mhz BALUN with a modified BALUN. BALUN was modified by adding capacitors to the BALUN enclosure. BALUN measured capacitace apx 85 uF. Verified 118 Mhz noise is reduced in the vicinity. The first plot reflects the 118 Mhz noise measured at an antenna placed in front of the rack, and the second plot reflects the 118 Mhz noise measured after replacement of the BALUN. This antenna and receiver are pictured in attachment 6. The third plot reflects the noise measured at the 118 Mhz line connector using a custom fitted test lead (pictured in attachment 5) both before and after replacement of the BALUN. The fourth plot shows the 118 Mhz noise at the 9 Mhz line connector as measured with the custom test lead. 

EX pump down curve attached. There is a strange feature in the curve from Monday morning that caused the pressure read back to change, but not evident in the adjacent hot cathode gauge, so it could be an electronics issue specific to this cold cathode gauge.

A quick update on the external shutter installation.  We are still having issues with the external shutter, so it did not get connected today as we had planned.  The shutter assembly has been removed from the shutter enclosure and we are testing it in the EE lab.

SUS oplev model changes WP7637

Jeff K, Dave:

New models for h1susmc2, h1sussrm and h1sussr3 were installed today. New IPC channels were added.

New Vacuum channels for LX, LY

Patrick, Dave:

Channel configuration for h0vacl[x,y] was changed. I decided to split out H0EDCU_VAC.ini into one ini file per system (H0EDCU_VAC[LX,LY,MR,EX,EY,MX,MY]. It was getting unwieldy maintaining one concatenated file.

New Beckhoff HEPI EX Pump Controller Channel list:

Patrick, Dave:

a new H1EDCU_HEPIPUMPEX.ini file was installed

New Guardian Nodes:

TJ

Adding new guardian nodes resulted in a new H1EDCU_GRD.ini file.

New Slow Controls ALS EX,EY Channel configuration

Daniel, Dave:

New PLC2 channel configuration for EX and EY Beckhoff slow controls was added. The SDF monitor channel list was modified, so the h1sysecat[x,y]1plc2sdf systems were restarted. This resulted in 7 new channels at each end stations which were not-initialized, these were added to the monitor list and their values accepted.

DAQ restart

One DAQ restarted at 12:02 PDT to cover all of the above.

[Thomas Vo, Gabriele V.]

Summary: The ITMY HWS sensor is aligned.

Still to do: check if we are on the correct beam from the IMTY HR face, by changing the ring heater and monitoring the HWS signals.

We removed the mask in front of the Hartmann sensor, and found that the beam was badly clipping on the SR3 baffle. We could fix it by moving the lower periscope picomotor.

We checked that we are imagining the right plane (i.e. the ITMY plane) by moving in angle the ITMY in pitch by about 20 urad peak to peak, and checking that the beam center of mass on the HWS moved by about 1e-3 of the image size. To do this, we modified the stream_intensity_Y.py script (located in controls@h1hwsmsr1:~/temp) to compute the center of mass of the beam intensity in X and Y and plot it as a function of the frame number (horizontal axis). In the bottom panel of the plot below you can see how the Y position of them moves when there is a 0.03 Hz pitch motion of 20 urad peak to peak.

We fine tuned the centering of the beam on the HWS by adjusting the last mirror in front of the camera. We put back the mask and got images like the one shown below.

TJ noted that the beam splitter was oscillating wildly.  Glancing at the screen, it looks like the move that we did yesterday to align MICH (alog 42467) moved the BS mostly off of its optical lever PD.  So, with a small nudge (maybe a recent EQ? there's a small close one that showed up in our seismic blrms) we've fallen enough off the PD that the oplev loops started going crazy. 

I have the outputs of the BS oplev turned off for now.  We need to re-center the BS oplev next time Jason has a moment to spare.

Chandra has requested that all beam Tube vacuum auge high alarm levels be set to 8.0e-08Torr for the near future. This was done and the system was restarted.

+<Channel name="H0:VAC-LX_X4_PT144B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, LX X1-beamtube, CC">
+<Channel name="H0:VAC-MX_X1_PT343B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, MX X1-beamtube, CC">
+<Channel name="H0:VAC-MX_X5_PT346B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, MX X2-beamtube, CC">
+<Channel name="H0:VAC-EX_X1_PT523B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, EX X2-beamtube, CC">
+<Channel name="H0:VAC-LY_Y4_PT124B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, LY Y1-beamtube, CC">
+<Channel name="H0:VAC-MY_Y1_PT243B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, MY Y1-beamtube, CC">
+<Channel name="H0:VAC-MY_Y5_PT246B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, MY Y2-beamtube, CC">
+<Channel name="H0:VAC-EY_Y1_PT423B_PRESS_TORR" low="1.0e-10" high="8.0e-08" description="VE gauge, EY Y2-beamtube, CC">

Per work permit 7644.

I updated the PLC code on h0vaclx and h0vacly to add readbacks for the new annulus ion pumps on CP1 and CP2.

I got messages when restarting h0vacly that seemed to indicate that at least one variable was forced, but I was unable to determine which. I thought at first it might be PT100, but a previous alog says it no longer was. I also got error messages when scanning the bus and decided to recreate the project and try again. I did not get error messages the next time. I think the only difference was that I activated the configuration before scanning on the second attempt.

I burtrestored both h0vaclx and h0vacly to 6 AM local this morning.

The in-vacuum high voltage will need to be turned back on.

Dave will do a DAQ restart.

T. Vo, C. Cahillane, G. Mansell

Summary:
-We have aligned the ITMX and ITMY Hartmann wavefront sensor periscopes to get the ALS-X green beams co-aligned with the SLED beams.

-While we see something on HWSY (attached image), we’re not quite sure yet if we’re sampling the right optical surface (ITMY) or something else, investigation ongoing.

-We don’t currently see a signal on HWSX, alignment ongoing.


Details:

We steered SR3 to get the ALS-Y green beam onto the ITM Hartmann sensor table. This was quite arduous as none of the workstations or CDS laptops were allowing anyone to log in.

We can see green light on both HWSX and HWSY paths, assumedly the Y path is from the reflection off the back surface of the beamsplitter.

We had to adjust the positions of both periscopes on the table to centre the green beam on the top mirror in yaw (Y periscope moved by ~1 inch, X periscope by a bit less), and adjust the position of the top mirrors to centre the beam in yaw. We then steered the top and bottom periscope mirrors to align the beam with the SLED irises set up by TVo previously.

We encountered an interesting phenomenon where one of the steering mirrors on the HWSX path (between the two irises) seemed to be angled right at Brewster’s angle for the green beam. Alignment onto the second iris was virtually impossible as there was no reflection off this mirror. We instead placed a new iris aligned to the SLED and aligned the green beam to this.

Once we have a CDS computer working on the floor we'll be able to take the Hartmann sensor plate off HWSY and confirm which optical surface we're sampling, as the baffle apertures should be visible if we are hitting ITMY.

[Jenne, Gabriele, Daniel, Keita]

Once the gate valve was opened, we started work on aligning the Yarm to the green beam.  Short story: green now locks nicely, we have beam coming to ISCT1, we moved BS to get MICH flashes (with the new ITMY alignment and the ITMX that we've had for a while now), which got us some IR flashes in the Yarm.  Team Hartmann (TVo, Craig, Georgia) are now setting SR3 to get the green beam out onto the TCS table. 

----------

• Alignment of arm to green
  • Baffle PD alignment script worked pretty well for TMS.  The TEST filter banks needed to have the urad-to-counts calibration put in, so now the script will do that, so that the moves to the expected PD locations actually work.  So, TMSY was set to point at ITMY.
  • ITMY was far enough off that the baffle PD script did not work at first.  We scanned around (a lot, hundreds of urad) until we saw beam on one of the baffle PDs (#2 at first, which isn't at all close to the optic), then made our way to maximizing the beam on one of the 2 that are close to the optic, setting ourselves close to the center of the optic, then ran the baffle PD alignment script, which worked.
  • ETMY was also far off, but again scanning around to find the beam on one of the PDs, we were able to then find the other baffle PD, and put ourselves in the center.  We don't have the ETMs available in the baffle PD alignment script, because we don't usually need them.  But, sometimes we do need them, so maybe we should add them....if we had infinite time.
  • ITMY is now +90 urad in pitch from previous, and -305 urad in yaw from previous.  The pitch wasn't so surprising due to the AMD install, but the yaw was unexpected. 
• Locking solidly
  • Pretty easy - requested Yarm guardian to go to LOCKING_NO_SLOW_NO_WFS. 
  • There was some triggering that was causing us to lose lock - Daniel overrode / fixed that triggering, and now we're able to stay locked for long periods of time.
• WFS loops closed for Yarm green, camera loop not closed, so not yet full green ASC
  • The WFS loops (DOF1, DOF2) for the green ASC closed just fine.  They seem to oscillate with the old overall gain value (H1:ALS-Y_WFS_GAIN) of 0.5, but 0.4 is good.
  • The camera setpoints are not good any more, so we cannot close the DOF3 loop.
    • There is some light coming to the camera that can be moved by moving the compensation plate.  Something has always been there (see attached ITMYgreen_old.png), but it seems worse now.  As we found it, it was as shown in attachment 2, ITMYgreen_new_prevCompPlatePosition.png.  We can move all but the last spot by moving the compensation plate.  Because it seems not so nice to have fringes, we've left it at as shown in attachment 3, ITMYgreen_new_newCompPlatePosition.png.  Of course, we'll reset the CP later to be good for the IR beam, so this won't be its final final position.
    • Once we decide that we're happy with the beam position on ITMY, we can reset the setpoints for the camera, since the one spot doesn't move with ITM position, but the actual beam does.  This is what we have done previously, and seemed to work.  Eventually, of course, we'd like to figure out where the spot is actually coming from, and prevent it.
      • Daniel has calculated that it can't be coming directly from the compensation plate, but we're still not sure where the true source is.
      • It's definitely green light coming from the Yarm, since it flashes along with the beam from the Yarm.  If the Yarm unlocks, those spots are gone.
    • To decide that we're in a good place, we think we'll set the green beam position by dithering ITMY and moving the beam so that it's at the center of the optic.  This relies, however, on the coil balancing that JeffK will be doing soon.  For now, it should be good enough for Hartmann alignment work.
• MICH aligned, not locked
  • Using our new ITMY alignment, and the ITMX alignment that we've been using for the last few weeks, we set the BS to have MICH fringes that we could see on the LSC POP diode. 
  • We still don't have beam out to the AS port, so we have not yet locked MICH.
• Yarm IR flashes
  • Once we restored ETMY alignment (it was misaligned for our MICH work), we started seeing sign of IR flashes in POP DC.  We have not yet looked further, since we had other things to work on, but feel reassured that we won't be too terribly far off with our input pointing, once we have the Xarm open.
• Moved PR3 to prevent clipping of beam on ISCT1
  • We already have beam at ISCT1, as seen on the ALSY camera.  It was clipping a little bit, so I moved PR3 a small amount in both pitch and yaw.  There is still some clipping somewhere, but it looks much more similar to what we used to have. 
  • The Yarm green transmission currently reads a max of 4.4 or so, where the normalization was set to that in O2 the max was 1.  This is roughly consistent with what we expect with our new Finesse.

-----------------

Next up for main IFO locking is to move SR2 to get the beam back to the AS port (after the TCS team has set SR3 to get beam out to their table). 

Final attachment is our current slider values.

Closed safety valve on turbo station, spinning down turbo, and turned off backing scroll pump.

De-energized compressor #1,2 in chiller yard, along with the drying tower controller.