Installed the following electronics at EX per D1001423-v18. D1002559 ISC Whitening Chassis for WFS_A D0902796 WFS I/Q Demodulator WFS_A D1100905 Demodulator Patch Panel D0902796 WFS I/Q Demodulator WFS_A D1002559 ISC Whitening Chassis for WFS_B D1100749 Legacy iLIGO WFS PD Interface Items still needed for tomorrow: 1. Power up electronics 2. Finish running long field cables to 384 Channel Acromag Binary and AA chassis 3. RF cabling from field rack to ISCTEX table Filiberto Clara
I loaded the Tcrappy blend filters on the BS ISI today, and reworked some level 3 controllers with a more aggressive boost (while preserving the .m-file with the old working controllers!), but it's not fully working yet. I can get st1 on the new controllers, but it trips as soon as I turn any of the boosts on. For now I'm leaving the ISI on the old level 2 controller. I'll look at it again tomorrow.
I've moved IOHT2R into its proper position. The plan for tomorrow will be to transition the LVEA in the afternoon while the red light working group has PRM aligned to begin aligning the table to the SM2 trans beams.
A crashed ops machine ate my homework, so this isn't very complete...
Earthquake this morning tripped ITMX and ETMX, and others. ETMX ISI didn't come back up until 1300. There has been elevated microseism all day due to high winds.
Fil at Ex, mid-Y, Ex again
Fire Dept at EY 0900
HEPI pump station down at ex this morning, hugh down to diagnose 1100
MarkB working on tip-tilt filters 1300?
JeffB at ham4 1330
Mitch & Justin ACB cleanroom 1330
JoeD h2 psl enclosure 1200-1300
JeffL in LVEA ~1300
Me loading new isolation lvl3 filters in the BS ISI 1515
Calibration gain for MC1 MC2 MC3 alignment offsets was modified after Paul's measurement :
OPTIC | DOF | Initial factor (cts/urad) calculated from alog 4763 | Scaling factor from alog 9870 | New gain (cts/urad) |
MC1 | Pitch | 1.875 | 0.7043 | 1.3206 |
Yaw | 2.681 | 0.8223 | 2.2046 | |
MC2 | Pitch | 1.875 | 0.8572 | 1.6072 |
Yaw | 2.681 | 0.8326 | 2.2322 | |
MC3 | Pitch | 1.875 | 0.7823 | 1.4668 |
Yaw | 2.681 | 0.8588 | 2.3024 |
(Alexa, Sheila)
Today we had trouble locking the green arm...
Starting to update the models, scripts and screens for HAM-ISI. Work is performed under WP #4434
Details about the update can be found in DCC T1400012
Yesterday with completion of TMS Alignment, may have jumped the gun with securing the assembly. Forgot that SEI will want to float, balance, and test the ISI. So the EQ Stop Tooling (aka Alignment Stabilization Tool) needed to be removed. Before removing it, the Swing Stop Cart was installed, and then the EQ Stops were removed. So now the TMS is ready for the ISI to be tested. So with SUS's work this afternoon and SEI's work for the next few days, that would put us back on deck to secure the TMS next week most likely.
TMS TO DO List Post-SEI Test Stand Work:
I swapped in a new HTTS filter file with corrected dewhitening filters (what claimed to be 10:0.4 had actually been 40:1.6). I checked that RM1 and RM2 still damp stably.
I've started on a round of undamped TFs on RM1 and RM2 to check that I get the expected results without post-hoc corrections.
The TFs were taken successfully. The raw data was processed with meas.badFilt = '' (no post-hoc filter correction) and meas.E1201027 = true (coil driver resistors replaced):
^/trunk/HTTS/H1/RM1/SAGM1/Results/2014-02-12_1330_H1SUSRM1_M1.mat
^/trunk/HTTS/H1/RM2/SAGM1/Results/2014-02-12_1330_H1SUSRM2_M1.mat
These data sets are plotted in the attached PDF with the latest L1:RM1 and L1:RM2 results and the immediately previous H1:RM1 and H1:RM2 results of 12/20/13. As expected, the new results without post-hoc filter correction agree with the earlier results with correction, showing that the new H1SUSHTTS.txt file is good. (It has been committed.)
The agreement with the model is good for H1:RM1 so this new data (2014-02-12_1330) can count towards Phase3b testing. The RM2 data shows the same strong coupling of L into Y as the last few measurements, and this needs to be investigated at the next vent.
LLO should impement the same fix as soon as convenient. Specifically, in L1SUSHTTS.txt, all the ???_M1_OSEMINF_?? modules should have Section 1 set to have label '10:0.4' (probably that way already) and filter zpk([10],[0.4],1,"n") (will have been zpk([40],[1.6],1,"n")).
I created a new version of the HTTS TF plotting script, plotHTTS_ddtfs_M1.m, to correct for the fact that the wrong dewhitening filter has been installed at both sites, and that the LHO ISC HAM-A coil drivers have only recently been changed per E1201027. Setting meas.badFilt = '40:1.6' (rather than ' ' or anything else) enables the correction for the bad filter, and meas.E1201027=true enables the new gains.
The actual hardware whitening filter is 0.4:10 per D1002818/D080276. The dewhitening filter installed in Slot 1 of the the OSEMINF blocks claims to be 10:0.4 but has actually been 40:1.6.
After checking with Stuart to ensure that there was no LLO data that hadn't been committed, I reran plotHTTS_ddtfs_M1.m on all the data sets listed in measList in plotallhtts_tfs_M1.m, so as to regenerate the summary .mat files and plots at ^/trunk/HTTS/ifo/optic/SAGM1/Results .
I used meas.badFilt = '40:1.6' in all cases and meas.E1201027=true for all except the measurements of H1:RM1 and H1:RM2 in 11/2013, which were before the LHO resistor change. I lost a day to head-scratching before I realized that the L1 resistors had been changed shortly after the ECR was approved in 12/2012, whereas the LHO ones were changed almost exactly a year later (12/2/13, LHO alog 8792).
As might be hoped, the new plots were free of the hump caused by the misalignment of poles and zeroes between hardware and software. The new files have been committed to the SVN.
The two attached comparison plots show L1:RM1, L1RM2, H1:RM1 and H2:RM2 before (2013-11-25) and after (2014-02-12) the fixes. Note that the H1 data in the second plot is from later (12/20/13), and fixes a second filter issue that has not been identified but only affects the 11/24/13 data).
I prepared a new filter file for LHO with the correct dewhitening filters, /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSHTTS_dewhitefix.txt , and will install it at the earliest convenient opportunity.
I have updated the CDS MEDM overview screens: added new h1lscaux model changed the WD colors to support HIFOX
Fluid level trip. Found the Pump Controller (not servo) red lite off--other than power failure, sure indication of Fluid Level trip.
Turn on Process:
Since I've hardwired the FWD button, the controller will start at the Servos Command as soon as the Green Start Button is pushed, so:
Must turn down the Servo Output--On Pump Controller medm set servo set point to zero or manually run down the output.
Press Green Start button on Controller Cabinet, Ramp up servo set point to 80psi, or step up output manually to near 80 and then switch servo to Auto mode.
Warning--Don't overshoot the pressure too much or the level may trip again or if you really overshoot and the level doesn't trip, the pressure relief valve will release.
After I got the servo running again, I pulled up the trip switch and found the trip level was only ~1/16" below the run level. Of course to do this test you have to trip the switch and start all over again. I then lowered the switch ~1/4" so we should be good for a while.
I have a scale on the site glass and a white board logging the running levels and now I have a trip level. We have been trending down a bit over the past few months. I have a couple minor leaks at the pump station, maybe something like a teaspoon a month. That combined with evaporation and the large servo load (really minor affect I believe) led to the trip. I'll start a regular maintenance routine of noting the running fluid level and lowering the trip switch to keep ahead of it.
Patrick T., Sheila D. We went to check on the H1 PSL environment. We verified that all the HEPA fans are off. We couldn't tell if the make up air fan was running, so we commanded it to run again. It was and still is set at 20% fan speed.
Something odd is happening with the IOC for the dust monitors at end Y. The medm indicates that the IOC has died. Telneting into the procServ server for it appears to automatically restart it. This happened yesterday morning as well.
I have attached two plots of the dust counts in the H1 PSL enclosure from 8 AM yesterday to 8 AM this morning, one from the laser room (Location 1) and the other from the anteroom (Location 2). These are from the newly installed Lighthouse Remote 3014 particle counters. The counts are normalized to particles per cubic foot. The samples run for 20 seconds with no hold time between them. The black traces are counts > .5 microns. The blue traces are counts > .3 microns (including > .5 microns). The scale for particle counts is on the left. The scale for temperature and relative humidity is on the right.
Sheila found the two TM ISIs tripped--Looks like a big event hitting the microseisem plus we are having a bit of a wind event. Sheila was unable to get the ETMx to go up but she was using the 750mHz blends and that may just not work for Lvl3. We likely need to tailor some blends to work with Lvl3 that don't use the T240s. I was able to get the ETMx ISI Stage1 up directly to Lvl3 with TCrappy blends as the Bias Position were not far from the targets. And Stage2 is still using Lvl2 controller with TCrappy blends.
Sheila had no issues getting ITMx back up. This ISI had been on since Friday 0816utc--not bad.
All HEPIs are operational and running position loops.
The ITMY & BS Appear to be in the same state as I left them last night. According to the WD last trip time these last tripped about 10:30 & 11:30 yesterday am. They weren't up during all that time though as we were ignoring them.
As far as the trips on the TM ISIs, there were some significant EQs around the globe in the hour before the trip( such as a 6.9 ~50 minutes before in China), we had elevated winds (no wind monitor at Ends) and running these very aggressive controllers all may have combined to causes these near simultanios trips (8 seconds apart.)
In case you didn't catch it -- the large event was most likely the 6.9 Mag Earthquake in China that Aidan noticed. It took down LLO's seismic platforms too! We *really* need to get legible ground motion plots posted on the control room walls that remain functional for more than a few hours and are in physical units. This would have been obvious in the S5/S6 era control room.
These plots are on the walls at LLO at present. We are still working on getting snapshots posted to the web site for off-site inspection.
plots attched.
For the ITM it was basically a one click recovery (using Tcrappy blends and isolate level 3), I tripped the ETM trying to bring it up (I tried 750 blends and level 3 on stage 1, that didn't work).
Hugh saw that the biases on the EMT ISI were fairly small, and brough it to stage 1 level 3 with T crappy, stage 2 level 2 Tcrappy.
The microseism has been rising over the last 20 hours, and there was a big spike somewhere around 2 am. (we are currently at around 5 on the strip chart, I'm not sure what the units are).
The tripping may be due to the M6.9 earthquake in China (see LLO aLOG entry ) which occurred at about 3:20 AM CST (or 1:20 AM PST). It tripped all our watchdogs
(Alexa, Hugo)
ETMX watch dog tripped at 9:45am. Similar spikes seen in ISI.
What happened at 9:44am PCT: Fluid pressure drops on HEPI (No fluid pressure on MEDM screen of HEPI pump. reason still unknown). HEPI drive increases to meet targets, but hepi does not get physically driven due to the abscence of fluid pressure. The servo increase the output drive to compensate for it to the point where HEPI trips (1). Once tripped, HEPI slowly (hydrolic system) comes back to its floating position. While slowly coming back, it saturates the T240s, which are included in the blend which is fed to the ISO, causing the ISO of the ISI to ramp up as well, and trip the ISI (2), 2 seconds after HEPI tripped.
Trip times:
HEPI: 1076262292 (1)
ISI: 1076262294 (2)
[Stefan, Lisa, Evan, Kiwamu]
Our goal tonight was to get the IR transmitted light centered on the transmon QPDs. A coarse alignment was established. We still need to do a fine alignment with the picomotors.
QPD centering:
We had never aligned this path with the actual IR beam, and neither QPDs had a beam on them. As discussed and suggested in the last integration meeting, we started this mission from a scan of the TMS in order to find an IR beam with the QPDs. Moving the TMSX in an almost random way, we found a beam which was flashing as the carrier light resonated in the cavity. The yaw angle needed to be twisted by roughly 100 urad to get the beam on the QPDs. Then, keeping the flashing beam on the QPD by steering the picomotors (M4 and M14), we steered the TMSX back to the nominal angle. This operation was successful. Then we moved onto a fine adjustment by locking the main infrared light to the arm cavity (the detail of the locking procedure can be found in alog 9644).
The fine tuning was very frustrating. We kept loosing the lock because of the roll mode of MC2 at 40 Hz (see awiki for HSTS resonances ) which then saturates everything and breaks the lock. Plus the spot position on the two QPDs didn't seem to be conversing by moving a combination of the two picomotors. The spot behaved as if the picomotors are degenerate. It is possible that, since the time for tweaking the picotomors was limited by the stability of the locking, we confused ourselves in the rush. This needs to be revisited. Anyway, a good news is that we now have a beam on both the QPDs and therefore we can do the fine adjustment anytime when we get a chance. Also we did an estimation of the power on the QPD, because we needed to clarify if the beam we saw was the main beam or a ghost. This is summarized in Evan's log (see alog 1006).
Some other things:
Later tonight, I tried to engage the AO path. Though I haven't succeeded. The idea is to have a low cross over frequency which then allows us to (re)insert the notch filter for the 40 Hz roll mode. However the loop was not so stable and everytime when I changed the AO path gain in the common mode servo board it simply broke the lock even if the gain seemed small enough. In addition to it, it became harder to lock approximately after 1:30 am probably due to some angular fluctuation in the arm cavity. I am too lazy to identify what optic is moving, but it is also clearly visible in the green ISCT1 CCD camera. Because of that, the IR locking doesn't stay more than 2 seconds -- the cavity build up in infrared drops extremely quickly due to the angular fluctuation.
End Station work:
Also, Lisa and Stefan went to the end X station to realign the single trans PD because the beam almost completely fell off from the diode during our picomotor adjustment. Because this PD was used for triggering the infrared locking, we needed to realign it. The alignment wasn't completed because the infrared light was not bright enough to easily work with. Then, it turned out that the bottom periscope mirror for the IR trans path was found to be very low reflective for some reason. It can be a wrong mirror. Indeed, Lisa and Stefan could see a beam with a card before it hits the bottom periscope mirror.
This mirror needs to be checked and possibly replaced by a proper one.
Just for reference the picomotors are now at: M4 X=-3273 Y=1796 M14 X=-1630 Y=-3515 In case any one wants to go back to approximately the position they were at before.
Also noted in alog 9731, most of the light the "IR trans" path has about 30-40 uW of green light, this may be what is transmitted by the lower persicope mirror.
Modifications to the slow controls system were made to add WFS whitening channels and WFS demodulator readbacks.