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
I believe I have ameliorated the wireless problems with the workstations at EX. Let me know if they continue to misbehave.
Also, I rebooted the dedicated vacuum workstation in the control room since it was running terribly. It's also had the latest updates applied.
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.
HAM2+3 HEPI and ISIs have tripped along with MC2+PR2. We have seen similar behavoir before after a beckhoff restart, but this time it was the LSC model.
The LSC model restart would have killed the guardian, and unlocked the modecleaner, meaning that the integrator at the top stage of MC2 would get saturated, so it makes sense that MC2 tripped. The ISIs and HEPIs weren't payload trips, so something else is going wrong.
This probably could have been prevented if I unlocked the mode cleaner and puased the guardian first.
Here is an error message from the plotting script failing:
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
9:00- 10:45 Getting ready to remove payload on HAM5 – Hugh and crew 9:05- 10:00 Performing PET swipe at HAM 5 – Jeff B. 9:25- Doing inventory by the squeezer bay area – Corey 9:43- Moderate dust alarms at both end station 10:00-11:55 Working at End X-Richard 10:06 PSL check (Done) 10:07: 11:30 Heading to End Y to work on dust monitors – Jeff B. 10:40 Moving laser barriers around the HAM4 TCS table area – Justin/Cris 11:02-12:45 Heading into H2 Laser enclosure to set up the OFI - Gerardo 12:37 Heading to End X (cleaning) – Chris 12:49-14:16 Heading to Mid Y (cleaning) – Karen 13:27 Running hose from near HAM4 to inside Diode Room – Jeff B. 13:36-14:48 Back to H2 Laser enclosure to set up the OFI - Gerardo 13:44-14:48 Joining Gerardo in H2 Laser enclosure (LVEA) – Mark B. 13:45-14:41 Setting signs around TCS area in LVEA – Justin 14:47 Beckoff power recycling – Matt/Greg 15:25 Heading to End X to fix CDS workstations - Cyrus
This exercise will need to be done occasionally until the Y2-1 port is restored to its nominal configuration (i.e., following the removal of the RGA test setup)
Mark B. and Gerardo
Yesterday (4/22/14) Gerardo and I measured the vertical mode Q of the OFIS for three different positions of the ECD block to try to get the Q in the specified range of 25-30.
The OFIS was set up on the optical bench in the H2 laser enclosure. The ECD block sits on a tray below the payload which is supported by four groups of vertically pointing screws at accessible positions around the edge of the structure. Gerardo had earlier attempted to set the ECD block at the nominal height using the spacer tool provided but found that this was too high and caused interference. He therefore lowered the block until it was just barely clear plus approximately an extra two turns of the 1/4-20 screws. This was our starting point for further adjustments.
To measure the vertical Q, we used the laser pointer and QPD from the monolithic violin mode setup and used a convenient screw on the top of the payload to partially block the beam. We displayed the "pitch" output of the QPD box on a digital oscilloscope with a 1 sec/div timebase and photographed the screen to capture the data. I read off the peak positions with GraphClick, and worked out the logarithmic decrement and Q with Mathematica.
For the initial position, the Q was 10.7. We lowered the ECD by one turn on all the screws and got Q = 18.9. We lowered the ECD another half turn and got Q = 23.3. Finally, today (4/23/14) we lowered the ECD another 3/4 turn and got 27.8, which is in spec.
Attached is a JPG of the setup, a PDF of all the screenshots, and for the fourth and final run, the Mathematica notebook, PDF thereof and the raw data.
We went back on Friday 4/25 and used the same method to measure the longitudinal (parallel to the OFI beam axis) and transverse mode Qs. For the longitudinal measurement we were able to keep the laser in almost the same position, just clipping a different edge, but for the transverse we had to send the beam on an odd diagonal path clipping one corner and then passing through the hole in the beam dump at the end (see photo). The results were
L: 21.3
T: 15.3
V: 27.8 (from 4/23, above)
The spec is <30 per T1000308-v1, p36, so these Qs look good and we propose to leave it like this.
I measured the gap between the copper plate and the magnets, 4 mm and all 4 corners.
Per request of Jeff Kissel, I extracted the frequencies from the data of 4/23 and 4/25 for the final configuration of the dampers: