Sheila, Stefan

The green arm maximum build-up had been trending down for a while to about 500cts, so we decided to do an arm alignment from scratch today.

Step 1: Baffle PDs
- We used the single shot beam to find the baffle PDs:
         TMS PIT    TMS YAW
  PD1    220.0      -226.7
  PD4    289.3      -288.6
  Center 254.65     -257.6
  
  PD1 is H1:AOS-ITMX_BAFFLEPD_1_VOLTS, and PD4 is actually H1:AOS-ITMX_BAFFLEPD_3_VOLTS 

Step 2: Follow with the arm
- We still had some fringing at the old TMS alignment (P 279.3, Y -245.3 - yes, that's 27urad from the new position...)
- Thus we stepped TMS first in pitch and then yaw, and roughly followed with the ETMX and ITMX.

Step 3: Arm dither: Control ETMX and ITMX instead of ETMX and TMSX
- We changed the feed-back scheme to leave the TMS untouched, and only align the arm to the input beam.
- This was done by feeding back PZT1 dither (DOF2) to ETMX, and PZT2 dither (DOF3) to ITMX.

Step 4: Move PR3 to center the green transmitted beam on the first reference iris on ISCT1.
- The new (good) PR3 alignment is
  PR3 P: -245.0  Y: -253.28

Step 5: Realign the green ISCT1 path
- We aligned the camera (and marked the spot on the monitor), realigned the transmitted green DC PD, and tweaked the COMM beat node up.


With this scheme we got about 915cts of green transmitted light - more than ever.


Step 6 (TBD): Diagonalize the dither drive matrix
- Evan and Yuta will do this soon.

FSS, ISS NOT in nominal range

Output Power is 29.1 W (should be 30 W)
Frontend Watchdog is green
Only warning is 'VB program online'

PMC
locked for 1 day 8 hr
Reflected power is 10% of transmitted

FSS
reference cavity has been locked for 17 min (not good, should be days/weeks)
trans PD threshold is .3 V (not good, should be .9 V)

ISS
Diffracted power is 5.3% (not good, should be 10%)
Last saturation event was 23 min ago (not good, should be days/weeks)

I temporarily installed a modal damping filter on the longitudinal degree of freedom of ETMX. The filter has 32 poles, so it is split between two modules, 'md_part1' and 'md_part2'. I plan to measure ringdown times of the test mass tomorrow using the green cavity signal. This is part of an effort to see what are the fastest possible ringdown times of the test mass with top mass damping. After the test I will remove the filters.

Normally a modal damping filter wouldn't need this many poles, but I decided to include the pitch dynamics in the estimator to get a more faithful reproduction of the 1st longitudinal mode frequency for this test.

Brett and Andres

In an effort to get more data to improve sus models, we locked the top mass down on SR2 and measured spectra of the lower two masses. We then locked the middle mass down and measured spectra on the bottom mass. The data has been committed to the svn at .../sus/trunk/HSTS/H1/SR2/Common/Data.

I will process this data and see if it gives us a model that matches this suspension more accurately.

All ISIs are in Control Lvl3 except for ETMX Stage2 which is in Lvl2.  All Blends are TCrappy where available(only ETMx & ITMx) except for ITMX Stage2 is at 100mHz (Jim--should this be TCrappy?)  The ITMY & BS has 750mHZ blends on Stage 2.  For the BS & ITMY Stage1, T250mHz blends everywhere except the X & Y dofs have T100mHz_0.44 for BS and T40mHz_NO.44 onthe ITMY.

Kiwamu created a new h1lsc0 model called h1lscaux. I have added it to the h1boot system and the DAQ. The DAQ was then restarted. 
h1lscaux was restarted to get the awgtpman to startup.

17:11PST, restarted DAQ against modified susaux models and latest Beckhoff ini files (4 channels added to c1plc2). Found that the models h1susaux(ex, h34) needed a manual start due to burt button not pressed quickly enough.

Today I finished up modifying the SUS monitor models as it has been deployed at LLO in december (alog 9964 and alog 10010), under ECR 1300261 in order to add the voltage and noise monitors in the frame + science frame for each individual osem. The following models were modified, recompiled, and commited to the svn :

h1susb123 (bs, itmx, itmy) rev 7070
h1susauxh2 (mc1, mc3, prm, pr3, im1, im2, im3, im4) rev 7087
h1susauxh34 (mc2, pr2, sr2) rev 7072
h1susauxh56 (srm, omc)  rev 7074
h1susauxex (etmx, tmsx)  rev 7083
h1susauxey (etmy, tmsy) rev 7085

Details of modifications are specified below :

For the quads :

M0/R0 Noisemon was changed from 1024 to 512Hz
M0/R0 Voltmon was changed from 1024Hz to 256Hz
L1/L2 Noisemon were created at a rate of 1024Hz
L1/L2 Voltmon were created at a rate of 256Hz

For the triple suspensions :

M1 M2 M3 Voltmon added at 256Hz
M1 Noisemon added at 512Hz, M2 at 1024Hz and M3 at 2048Hz

For the IMs and OMCs

M1 Voltmon added at 256Hz
M1 Noisemon added at 512Hz

For the TMS :

M1 Voltmon added at 256Hz
M1 Noisemon added at 256Hz

Fire department testing smoke detectors

09:15 Mike L. taking Kim on tour through LVEA, end Y
09:39 Jim B. upgrading GDS tools (WP 4432)
09:56 - 11:50 Mitchel R. cleaning up in LVEA west bay
10:31 Jaclyn S. to squeezer bay
10:35 Dave B. running OS updates on cdsssh, cdslogin, lhoepics
10:56 - 11:23 Stefan B. restarted h1odcmaster model, which crashed the h1oaf frontend and killed mxstreams. Dave B., Jim B. recovering
11:21 - 12:45 Joe D. working on PCAL assembly in H2 PSL enclosure
11:48 LN2 delivery ~10 min away
12:01 Jaclyn S. and Alexa S. to end Y to look at electronics
13:01 - 13:36 Justin B. to end Y to look at conditions for moving table in
13:03 Kris cleaning at end X
13:14 - 14:40 Karen at end Y
13:32 HVAC repair for chiller unit in MSR
? - 16:13 Mitchel R. cleaning up in LVEA west bay

We are testing the h1odcmaster on the DAQ test stand, this has required that the H1.ipc file be replaced with a copy of the one from the h1 system (with host names changed from h1 to x1).  The previous H1.ipc has been saved as H1.ipc.11feb2014.  This will be restored when we are finished troubleshooting.

(Corey, Doug, Keita, Yuta)

X-Translation Push

Started off the day securing the TMS with "hard stops" and installing (7) teflon-tipped dog clamps on the TMS Upper Structure & Pusher in preparation for our horizontal translation of ~6.5mm to the "left".  Doug watched us as we pushed the entire assembly this distance.

Yaw Alignment

After the big move, we then set up to fix the yaw of the structure.  This took a few iterations, because we noticed that after we Yawed and looked good, we would back off the Pusher and see that the structure springed back a little.  So we had to figure out how to overshoot and then have it spring back to nominal.  Once Doug was happy here, we torqued down all the Dog Clamps (25ft-lbs) and moved to pitch.

Pitch Alignment

The TMS was then freed up, balanced, and prepared for pitch work.  The back end of the TMS was seen to be pitched UP, so Yuta and I moved the TMS Table Counterweights toward the back, and we were able to get the Table pretty flat according to Doug.

Clean-Up & Tomorrow

So with this alignment, with a 0.0 Pitch & Yaw bias, we had a most excellent alignment of the TMS.  Doug and Jason were excused and we worked on finishing clean-up:  remove all Pusher hardware, re-install/torque removed Dog Clamps, re-adjust BOSEMs to new alignment, and then put TMS on EQ Stops.

NEXT UP:  Install tooling to secure the TMS for Cartridge insertion.

h1susauxb123
h1susauxh2
h1susauxh56
h1susauxh34
h1susauxex
h1susauxey

   The in chamber power spectra (aLOG #9961) for H1-SR2 showed noise at around 10Hz and up which does not appear in the LLO spectra for the same type suspension and phase of testing. Per the testing group’s request, the spectra data for H1-SR2 was reprocessed to show the individual channel data for each DOF and with additional comparisons to other LHO HSTS suspensions. The plots are posted below. All scripts and data files have been committed to the SVN repository. 

Dave, Jim, Stefan

Stefan restarted the h1odcmaster model which has been running since Friday evening and it did two things: locked up the h1oaf0 machine and caused DAQ errors on both end station front end computers, plus LSC, ASC and SUSAUXB123. Running start-streamers on the affected front-ends did not fix the problem. We took h1oaf0 out of the dolphin fabric, its console was locked up so we power cycled the CPU. All the models started OK and the MX stream error resolved itself. A few minutes later the IOP IRIGB drifted upwards to 66 and then back down to 15.

I stopped the h1oafmaster model and then started it again. Once again it froze up the CPU but this time no MXSTREAM errors on other front ends.

We took h1oaf0 out of the fabric and power cycled, once again h1odcmaster started (with 0x2000 DAQ error due to INI file mismatch). 

We are now testing on the DTS.

The login machine has been updated today, including an updated authentication module.  This work required a reboot of the system.

This is the commercial software controlling the Lighthouse particle counters in the H1 PSL enclosure.

Logging into h0dust (Windows 7 Pro SP1 64 bit virtual machine) through VNC this afternoon I found the error message in the attached pictures.

I found two related events under Event Viewer (Local) -> Windows Logs -> Application on 2/7/2014 11:02:01 AM. The text of the errors is attached.

Searching for related information I found the following: http://support.microsoft.com/kb/2640103

HAM3-ISI tripped recently and needed to be turned back on. Commissioners noticed that the command buttons were not working anymore.

It turns out that someone ran an SVN update on the following file: /opt/rtcds/userapps/release/isi/common/scripts/HAMISItool, which was to be updated along with new models, screens and scripts, after testing at MIT. Having a model/script mismatch, the command script would be looking for inexistent channels, and fail.

I reverted HAMISItool to -r5830. This script should not be updated from the SVN again, until the latest HAM-ISI update gets propagated.

HAM3-ISI was turned back on with Isolation Lv3 and 01_28 blend filters. Target values were not changed to ensure returning to previous alignment.