The ESD was non-functional this morning when we tried to operate it. I went down to EX and found the negative supply in the off state (indicating a trip probably not someone shutting it off). Turned it on went out to ESD drive to turn it on. As soon as I turned on ESD amp the Neg. Power supply tripped off. Went back out to power supply to see if I had not set the over current. The unit was off again. This time it would not turn on. Took this opportunity to swap out bot the positive and negative supplies. The positive due to problems noted last week with sync. and the neg. do to this failure. Power the system back up. The system once again was in an odd state all of the supplies present but sitting at a neg rail. I verified voltage everything was properly connected but still at a neg. rail. This was the same state the unit was in on Friday when I had Kiwamu come out to help. I disconnected the DAC inputs and reconnected them. Everything came up just fine. This is a very troubling state as the DAC was not sending out a voltage and the unit was behaving as though it was. The unit is now running and seems to be working again.
Took PET swipe samples: (1). Center of HAM5 ISI from the north side door. (2). End of HAM6 ISI near east door. (3). Just south of Center of HSM4 ISI from the south door.
Added two new dust monitors to cover the installation and alignment work at HAMs 4,5 & 6. Loc #1 is at the South side door of HAM4. Loc #6 is at the East side door of HAM6.
Plot attached.
I updated the H1ECATY1PLC2 xml file with the required manual setting to be compatible with the autolockers, and turned it on. All of the original four CSD prototype targets (H1ECATX1PLC2 H1ECATY1PLC2 H1ISCEX H1ISCEY) are now running. I also stood up the infrastructure for the CSD for H1LSC and H1LSCAUX - this was literally just running the commands: ./createCSD H1LSC lsc /ligo/cds/lho/h1/burt/2014/04/28/12:00/h1lscepics.snap ./createCSD H1LSCAUX lsc /ligo/cds/lho/h1/burt/2014/04/28/12:00/h1lscauxepics.snap followed by adding the systems to the CSD main screen.
Plot attached.
(Daniel, Alexa)
We have placed the broken demod from EY (SN S1000774) in the EE shop. We replaced it with a spare from MY (SN S1000779). We had also found a spare demod (SN100781) floating around at EY and have returned it to MY.
Plots attached.
The lockers were very smooth, no issues there. The Optical Table translated from 15 to 35um depending on dof, the tilts were 65 and 90 urads and the Yaw shifted <20urads CW.
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:
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.
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.
This is just a followup of the ETMX ESD power supply failure.
It seems that the power supply became non-functional (or at least the HV amp started generating zero voltage) in the evening of this past Friday which is the day we activated the ESD for the first time on ETMX.
The DC bias was the only channel which had a non-zero value and all the other quadrants was not doing anything at the time of the failure. A trend of the DC bias and its readback is attached.