J. Kissel

Will post much more details and (performance / metrics of success) later, but I've balanced the ITMY L2 coils using methods described in LHO aLOGs 11392 and 9453.

Former Balance:
UL 1.028
LL -0.911
UR -1.091
LR 0.968

New Balance:
UL 0.973282
LL -1.01098
UR -0.98898
LR 1.02728

TJ, TVo

Feeling like we should try to capture the positions of the alignment from alog-42507, we attempted center the HWS QPDS but we had an incredibly difficult time finding the beam because it was so dim returning from the ITM and the sensitivity of the QPDs were not very good. I'm not sure if this is an old issue but we eventually gave up on this.  The motivation behind this was because the current position of SR3 to get the ALS green beam onto the HWS table requires that SR2's alignment to come close to railing when trying to get the main IFO beam down to HAM6.  If we move SR3, we'll have to adjust the HWS injection alignment with the periscope mirrors but it is not clear how much we can compensate before we start clipping.  I think the current plan is that we'll try to wait until the ISC alignment crew (Sheila+Georgia+Hang) is happy with their spot positions with respect to the y-arm and see how much SR3 adjusted can be fixed with.

One interesting thing worth mentioning is that we removed the Hartmann plate in preparation for this alignment work and noticed that the beam did not look the same as it did yesterday even though we didn't move anything.  This could be due to the SR3 drift mentioned in alog-42507 and wasn't noticed because the plate was on. There's a bit more prominent clipping on the right side and the top, but I suspect this can be easily fixed by adjusting the periscope mirrors.

J. Kissel

Overheard the alarm that TMSX's independent software watchdog (SWWD) tripped at Jun 14 2018, 00:06:27 UTC.
Control room reports not activity.
Don't know why. 
Regular watchdog did not trip.
Transverse DOF was SUPER rung up.
ISI was still isolated, showed some red in its ST2 performance matrix in RZ, but may have been reactionary.

To fix:
Bypassed the SWWD.
Tried just turning on all damping loops by hand at their regular gains.
Saw that Transverse had obviously huge control output request.
Tried slowly (well, just one-at-a-time) turning on each degree of freedom besides T with normal gain. Works.
Waited for a bit, still obviously large transverse motion (looking at speed dials).
Turned on Transverse with much-less than normal gain (normal = -3. Started with -0.1.). Works.
Slowly (increments of factors of two, every 20-30 seconds, watching the speed dials) turned up the gain back to normal.

Now looks OK.

QUAD looks OK. 

Don't have time to figure out what happened...

Gabriele, TVo

Summary: We turned on the ring heaters to test the ITMY HWS, it is the correct sign and about the right change in spherical power for the input wattage.  First we input 2 Watts but the results were faulty because of SR3 drifting, then we waited till SR3 was stable and turned the power up to 14 Watts and the results were more consistent with what we expect. The compiled the overall results are here:

Details: 

After we aligned HWS ITMY and felt we were close to the conjugate plane of the test mass, we started the HWS acquisition code and took new references.  In order to fine tune the alignment, we also turned on the ring heater at 2 Watts (1 on the bottom, 1 on the top) and looked at the spherical power as well as the prism_x and prism_y values. As shown by the animation, it looks very badly misaligned but we found that this was due to a drift in SR3 when we were taking measurements and this threw off our results. 

A few hours later we decided to energize the ring heater  with higher power (7 Watts on the bottom, 7 on the top) and made sure that SR3 was not drifting too much, we saw a ratio of the Prisms_X/Y and Spherical_Power drop to about 5mm. The animation below shows that the heating pattern is much more centralized on the heater, but this is with a bad reference prior to the SR3 drift mentioned above so it still has residual heating imbalance.  When we get a chance, we can try to get a good reference and redo this scan overnight.  Because the heating causes changes in alignment, it might not be compatible with other commissioning tasks (alignment, locking, etc)

TITLE: 06/13 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:

Winds picked up late morning (& caused some dust alarms).

Variety of commissioning activities & other activities throughout the day.
LOG:

• 15:14 APS on-site at OSB (& MX later)
• 15:29 EY ALS Transfer Functions (Daniel, Craig)
• 15:57 Cleaning Room & then plumbing prep-work around PSL related to chiller manifold (Jeff B.)
• 16:00 IMC was misaligned while running at 11W, but realigned it after it was at 2W (Thomas, Hang)
• 16:02 Plugging in HAM6 CPS sensor (Hugh)
• 16:20-16:31 Looking for parts around HAM6 (Betsy)
• offload pSL PZT 
• target of opportunity for EY SUS charge measurement (betsy)
• 16:47-17:18 ITMy oplev centering (Jason)
• 17:04-17:34 Climbing on HAM6 (Chandra)
• 17:00 Working on DIAG_MAIN/Guardian (TJ)
• 17:20 Yarm clean up complete
• 17:15 Tour:  Univ Of WA New-professors (Jenne)
• 17:34 PSL Chiller Fill (Corey)
• 17:56 EX high voltage turn-ON (Georgia)
• 18:03 Centering ITMy Hartman sensor QPDs for reference (Thomas, TJ)
• 20:05 Moving cable walk-over at PSL/rack (Jeff B)
• 20:06 Moving fiber welding equip from EX to storage locations on site (Mark & Tyler)
• 21:44 Taking photos of ITMy (Jeff B)

All PD for ALS Y have been normalized to their new nominal values. The dip in reflection is about 25% (with ~40% expected with perfect mode matching, see alog 42384).

The PLL ugf was verified to be around 25kHz. The PDH servo ugf was set to about 5 kHz. We are able to use 2 100Hz/1kHz boost stages. This is now the default.

To drive the ESD for effective bias measurements later today.

HAM & BSC CPS's looked good for high frequencies (screenshots with all plots squeezed in are attached).  Closing FAMIS 6954.

At Sheila's request I have re-centered the ITMy optical lever to capture the current Y-arm alignment.  The OpLev beam was well off of the QPD with a SUM of ~500 counts; it is now centered with a SUM of ~31k counts.

Topped of the Crystal Chiller with 250mL of water.  (Diode Chiller was fine.)

Inspected the two filters.  The one on the left (labeled "X") had a black ring on the bottom of the filter.  Not sure if this was normal, so I contacted Jeff B.  (this is a new type of filter and so these filters have a black sealing gasket at the bottom of the filter.  So mainly look for noticeable amounts of particulates on white filter and particulates at the bottom of the container for the filter.)

Closing FAMIS task.

Troubleshooting the noise on the HAM6 corner3 CPS, see 42471.  Our testing suggested that unplugging either cable from the satellite box improved the noise in the still plugged-in channel.  So, the V3 was unplugged for a few hours followed by having the H3 unplugged for several hours.  Nominal configuration was restored this morning.

Attached are spectra from these three periods, the platform was damped during these times.  The top plot is the current nominal state showing the extreme noise on the corner3 sensors.  In the middle plot, the H3 sensor is unplugged and the V3 sensor nicely trends with the other vertical channels.  The bottom plot is during the time V3 is unplugged and the H3 signal mostly trends sort of with the other horizontal signals.  In both unplugged tests, the remaining corner3 signal still shows higher noise at higher frequencies maybe hinting at the underlying issue.

Also looking at the time series, not shown here, the min-max peaks are reduced nearly to pre June 1 levels when one channel is unplugged.

I have a 3IFO request in so as to swap out the crate to see if there is anything in the theory that these results suggest the crate may be the problem.  FYI, this is HAM6 and this ISI was built what 10 years ago?  Installed and pulled from chamber, some mods made (can't remember what off hand) and then reinstalled.  It has been a test piece for many things given its convenient location.  Anyway, fodder.

Will Update FRS 10851

Richard, Carlos

Had to kill the processes on the server that were hanging on and restart the process.  The ITM-y camera that looks at IR is now able to launch from MEDM.

TITLE: 06/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 12mph Gusts, 7mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

Daniel is working on IMC alignment.

Richard working on cameras.

APS on-site.

HAM6 ISI is tripped (looks like CPS issue---will check alog).

The following signals were measured directly from the TTFSS.  The input modecleaner was unlocked for this
series of measurements.

    scope_21.png shows the fastm (yellow), pcm (green) and mixer monitor (purple) signals.  The case of
the front end laser was knocked with a screwdriver.  In this case the NPRO PZT temporarily rails before
a short term recovery followed by it oscillating and saturating continuously.

    scope_24.png is the same as described above except that there is no temporary recovery period.

    scope_34.png also displays the output of the common mode servo to the tune input of the VCO that
drives the frequency shifting AOM in the PSL (magenta).  For this particular trace the breadboard that
the TTFSS sits on was knocked with a screwdriver.  Clearly the PZT starts railing before the Pockels
cell follows.

    This scenario would be partly alleviated by giving the PZT more dynamic range by the use of a high
voltage amplifier.  The PZT is capable of handling +100V or more.  The TTFSS only drives the PZT with
+/-10V.





  Rick / Peter

tek00000.png shows the fastm signal (yellow) and pcm signal (cyan) as given from the TTFSS field box.
It was noticed that the pcm signal never crossed zero and always had a slightly saw tooth appearance
to it.  The same two signals taken from the TTFSS board (TP10 and TP9 respectively) are shown in
scope_11.png.  Clearly the pcm signal from the field box is broken.  Either the differential amplifier
(N14) or the differential-to-single ended amplifier (N15) is faulty.

    More to follow.





  Rick / Peter

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

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.

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.

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