Attached are a couple trend plots to show the history of the HAM4 alignment. HAM4 ISI Optical Table was aligned late January and the Actuators finally attached Early March. The first plot shows the electronics coming on 7 March and the zeroing of the IPS & Locking 11March. The doors were installed then to work on HAM5. The Pier Pods were turned off briefly towards the end of March. The second plot just overlaps the first plot by a day or so and switches to the Cartesian basis. The matrices were loaded 28 March (aLog 11078) making the Cartesian units valid. Pretty quite after that until 11/12 April when TFs De-Stress the system and things settle into a new position (more steady/long lasting?--Who knows) Bottom line--The main thing is the 80 urads of CCW yaw. THis of couse won't take much for SUS to correct during up coming alignment but the position loops are still not working. But, -80urads will be the HEPI 'zero' for HAM4 Rz.
Aidan, Thomas, Greg, Dave H, Matt H.
We worked on getting the polarizers aligned after the half wave plate on Friday. Despite our best efforts, we could get an extinction ratio better than 500:1 (so 20mW off the polarizers for 10W into them). We achieved a lot better than this at LLO (~ 250,000:1). We're going to revisit the alignment of the first polarizer after the laser (which is supposed to clean up the polarization of the laser).
We got several MOTOR ERROR warnings whilst using the rotation stage on Friday which required the Beckhoff system to be reset each time. Also, the rotation stage is now only turning in a range of about 5 degrees or so. Vern is looking into this today.
IMTX triped (GS13s and T240s) this morning, I don't know why. ( first attached plot)
I had some trouble brining it back, which might be because we paused the guardian and used the command scripts for Jim's measurement on friday. I followed Jamie's instructions from alog 11246, this didn't work verry well. At first the indivdual stage guaridans compalined about gains that weren't set corectly (all the ISO gains were set to 0) I paused everyone, fixed the gains, and unpaused again. Stage 1 guardian complained about filters which weren't set correctly (which was true, they weren't set correctly.) and stage 2 went ahead and tried to isolate, then the watchdog tripped.
I paused everyone again, set the fitlers the way the guardian was asking for, and unpaused again. One more time stage 2 tripped, which is the second plot attached. after reseting this one last time I think that the gaurdian has suceeded in bringing it back.
One more trip, the reson for this trip is not clear. There is no one working out by ITMX, the gain switches are all set correctly, sensor correction is on from the ground to stage 1 XYZ, we have Tbetter on all blends except for RZ which is Tcrappy
Also, the plotting script failed for some of the first trips on ITMX this morning.
File "/opt/rtcds/userapps/release//isi/common/scripts/wd_plots/main.py", line 170, in _BufferDict
abs_threshold_mask=abs_threshold_mask, host=host, port=port)
File "/opt/rtcds/userapps/trunk/isi/common/scripts/wd_plots/pydv/bufferdict.py", line 243, in __init__
self.add_channels(channel_names, wd_state_mask=wd_state_mask, abs_threshold_mask=abs_threshold_mask)
File "/opt/rtcds/userapps/trunk/isi/common/scripts/wd_plots/pydv/bufferdict.py", line 382, in add_channels
abs_threshold_mask=abs_threshold_mask)
File "/opt/rtcds/userapps/trunk/isi/common/scripts/wd_plots/pydv/bufferdict.py", line 344, in __fetch_data
self.conn.clear_cache() # clear any saved information from a previous connection
RuntimeError: Input/output error
Laser is on Output power is 27.4 W (should be about 30 W) Watchdog is red (not active?) (should be active) No warnings in PSL SYSSTAT.adl except "VB program online" PMC Last relock 6 days ago (should be days/weeks) Reflected power is 14.4% of transmitted power (should be 10% or less) FSS Locked for 2 days, 4 hours (should be days/weeks) Trans PD threshold is .4 V (should be at least .9 V) ISS Diffracted power is ~ 9.6% (should be around 10%) Last saturation event was 2 days, 5 hours ago (should be days/weeks)
Apollo has started taking the doors off of HAM6, will then move to HAM4. This will involve a forklift and light craning. Plan to be laser safe in morning, laser hazard for TCS work in the afternoon. Hugh will lock the HEPI and ISI on HAM4. SR2 alignment is planned for tomorrow. One cleaning of HAM4 was done on Friday, second cleaning underway this morning. Competing airflows between the BSC and HAM cleanrooms may need to be addressed. TCS alignment work will start with the X arm. Justin plans to install laser barriers near HAM6. These may need to be inside the cleanroom over HAM6. Peter plans to be working in the H2 PSL enclosure.
Here is the list of commissioning task for the next 7-14 days:
Blue team (Y-arm):
Blue team (X-arm):
Green team (XY-arm):
Red team:
SEI/SUS team:
no restarts reported. May be incomplete list due to file system problems freezing report server.
The workstations had lost their NFS mounts, which makes them unhappy. While it was possible to log in directly on cdsfs0, there was a kernel stack trace in dmesg, so I rebooted it. It hung on shutdown (not terribly surprising), but power-cycling brought it back with no apparent issues.
Also, cdsfs0 was still trying to NFS mount h2boot which no longer exists, so I corrected this. 'df' shows that the filesystem usage on /ligo dropped from 66% to 64% after reboot, will have to look into that; not that I entirely trust the output from before the reboot based on the presence of a kernel stack trace.
The timestamp in the syslog for the start of the stack trace is Apr 27 05:08:27 (local). This is absent in the cut and paste from the dmesg (which is timeticks only) in the file attached.
Find attached the watchdogs trips summary of last week/beginning of this week. We'll discuss about it during the SEI portion of the testing meeting tomorrow.
J. Kissel Came in to complete the work of adding dither paths to the BSFM and QUADs, but found all -- yes all -- workstations frozen. I hard-rebooted (power cycled using the button on the back) opsws6 and opsws5 successfully only to be thwarted by a log-in screen that wouldn't let me log in (it goes black for a second like the log-in process was successful, and then ding-a-lings back to the log-in screen). A few other computers, opsws1 and opws10, just froze on the first re-attempt to log in. The rest I've left as I found them, either frozen in the power-saver screen saver (i.e. blacked out with a small clock on top), or frozen on whatever the last person was doing. Apparently, the workstations are just as excited to take this sunny day off as I am! See you tomorrow, CDS. #archnemesis
no restarts reported.
model restarts logged for Fri 25/Apr/2014
2014_04_25 16:35 h1lsc
no unexpected restarts.
EY tripped, recovered, I started realigning Y arm, and at some stage when the arm transmission started to become decent the transmission number started jumping back and forth.
At first I was tempted to think of this as a HOM-related fluke, but when I looked at the time series, it looks as if some incorrect bits are flipped at certain number (though the data is already decimated to 2kHz and the decimation filter should make things somewhat fuzzy).
I'll connect a function generator or something to this channel and see what's going on on Monday.
After Richard fixed the issue with the ETMX ESD (see alog 11573) this morning, I briefly took an angular transfer function of pitch and yaw using the oplev. They don't look crazy -- 1/f^2 shape and non-measurable crosscoupling between pitch and yaw. However there was a descrepancy from the model predictions by a factor of 2-ish. I am not sure what makes the descrepancy for the moment. The transfer functions are shown below with the models for comparison.
Anyway, the ESD is functional and ready to go.
Note that I included Jeff K's arc-integral-factor which gave an extra factor of 2/pi for the torque in the model. For those who are interested in the details of the calculation, please find it in the attachment (ESD_pitandyaw.m). The raw data are attached as well.
The L1 ESD actuation measurements, applying 2 Hz pitch and yaw signals and looking at the optical lever signals, also show the reponse being a factor of 2 smaller than expected. There seems to be something systematic here that we are missing.
The original templates for this measurement can be found here: /ligo/home/kiwamu.izumi/Desktop/binary/20140424_ESD_ETMX/dtt/ swept_sine_long.xml (for L2L) swept_sine_pit_yaw.xml (for P2P and Y2Y) In addition, they've been copied and committed to the SUS repository here: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL3/Data/ 2014-04-28_H1SUSETMX_L3_L2LPY_SweptSine_1to20Hz.xml 2014-04-24_H1SUSETMX_L3_P2PandY2Y_SweptSine_1to20Hz.xml
Sheila, Alexa, Stefan, Daniel
Attached is a spectrum, in Hz/rt Hz, of the PLL control singals for ALS diff and COMM. This looks simliar to what was measured at Livingston last week.
We made changes to the LSC model to route these control signals into the input matrix to allow us to lock ALS DIFF.
These are calibrated in Hz, the spectra plotted above. The first column is frequency, the second is COMM ASD in HZ/rt Hz,the third DIFF ASD in Hz/rt Hz.