I made a simple MEDM screen for IY baffle diodes:
/opt/rtcds/userapps/release/aos/h2/medm/H2AOS_CUST_ITMY_SCATTERING_MONITOR.adl
Note to self: The screen is meant to be the view from the HR side.
The GDS software (diaggui, awggui, foton, ezca*, etc) has been updated on the suspension and seismic test stands to include modifications for the June 30 leap second. Also, the diaggui and awggui channel selection menus have changed to include 6 levels of hierarchy in the channel selection. This should make selecting channels easier as the very long menu with the tiny scroll bar has been replaced with hierarchy.
[Stuart A, Jeff B, Betsy B, Deepak K, Andres R] Prior to taking transfer functions on the PR2 (HSTS) suspension, it was necessary to configure the the digital system and triple test stand. PR2 requires the x1sushxts27 model be running, which had not yet been set-up on the LHO triple test stand. The x1sushxts05 model was shut down, using "killx1sushxts05", the other model started with "startx1sushxts27" and the framebuilder restarted (in future I need to adapt LLO scripts to automate this). The OSEM input filters, DAMP filters, COIL output filters, OSEM2EUL and EUL2OSEM matrices had to be configured for M1, M2 and M3 of a HSTS. Thankfully, Betsy was able to route the PR2 harness whist the above was taking place. BOSEMs and AOSEMs could then be connected up, and following some minor cabling shenanigans, signal appeared on the correct channels. Open-light measurements were made for the BOSEMs on M1, and the AOSEMs on M2 and M3. AOSEM open-light counts initially ranged from 15k to 30k, with a few units under 25k. However, after tweaking the alignment of the IRLED boards, it was possible to improve all open-lights counts to over 24k. All OSEM gains and offsets were calculated from the open-light values, allowing BOSEMs on M1 to be aligned. n.b. AOSEMs would be aligned later and were left backed-off, all the way back, for transfer functions to be run overnight. Sensor and actuator signs were checked and damping loops closed. M1-M1 transfer functions were taken overnight for each degree of freedom, with damping loops OFF. n.b. the suspension was not yet covered by a canopy (see 2012-06-18_1800_X1SUSPR2_M1_ALL_TFs.pdf). These transfer functions obtained can also be compared to other HSTS suspensions previously measured on test-stands at LLO and LHO (see allhstss_2012-06-19_AllHSTS_ALL_ZOOMED_TFs.pdf). The TFs demonstrate good agreement with the model and the spread of all HSTS measurements obtained thus far. A BURT snapshot has been taken of the functioning environment "20120618_x1sushxts27_PR2.snap", which has been stored in the following directory:- opt/rtcds3/tst/x1/cds_user_apps/trunk/sus/x1/burtfiles All of the above data, plots, scripts, and snapshots have been committed to the SUS svn as of this entry. To be able to complete Phase 1b testing, I had hoped to be able to take power spectra today for M1, M2 and M3. However, Jeff B informed me that he had found that a magnet had become detached from the M2 mass. Rectifying (re-attaching) this magnet is now the assembly teams top priority, and it is hoped that I should still be able to take power spectra before I leave LHO at the end of the week.
Y-end has been pumped by only IP11 and CP7 (Turbo valved-out) for ~24 hours now -> Took scan ye061912 (attached) -> compare to ye061812 which was taken when pumped only be Turbo. Note that the RGA filament was energized for only 1 hour prior to taking ye061812 which may explain the apparent increase in hydrocarbons from the initial scan, ye061112. Also, decoupled aux. turbo cart from GV18 annulus and changed IP11 HV from 5000V (as found) to 7000V (Vmax setting at controller was 5000V -> should be 7000V. Nominal STEP Voltage thresholds are > 1x10-7 torr = 7000V, 1x10-8 torr < pressure < 1x10-7 torr = 5000V and < 1x10-8 torr = 3000V. IP11 now indicated as "RED" on vacuum MEDM screens as a result -> I think that the CDS values to convert i/v to "pressure" are left over from "old-style" ion pump controller and need to be corrected for current model controller.
recently h1fw1 has been quite unstable, restarting itself every two to four hours. During my investigation, I noticed that the raw minute trend files stopped getting updated about an hour before h1fw1 crashed, but the framed data (minute, second and full) kept being written right up to the crash. Also h1fw0 does not show this problem, or has it at a much lower rate. I extended the raw minute update rate from 5 mins to 15 mins on both h1fw0 and h1fw1 by setting in their daqdrc files:
set raw_minute_trend_saving_period=15;
The new configuration went in at 4pm Monday afternoon. As of time of writing, h1fw1 has been up for 17 hours.
The fact that the identical h1fw0 does not have the same behavior suggests a QFS issue with the SATABOY for this system.
Forgot to mention that the reason this instability has just appeared is that the H1 DAQ system was recently expanded from just the PSL to include all SUS and SEI systems for HAMS 1,2,3. The number of channels in the DAQ is now 42k, making it comparable with the H2 DAQ.
This begs another question, why isn't H2 DAQ, with a 5 minute raw min trend rate, not seeing this problem?
Attached are plots of dust counts > .5 microns.
...continuing from Corey's shift: - 2:43pm: H2 DAQ restarted so HWS channels can be added to the DAQ. - 3:30pm: Dale leads tour in LVEA for visiting teachers. - 4:00pm: OSB Doors locked.
~1130 hrs. local Took RGA scan ye061812*soft-closed GV17*burped GV18 gate annulus into aux. cart*opened GV18 ~1530 hrs. local Valved-in IP11*Valved-out MTP
Report includes work from Friday, 15 June, since I did not alog that day. On Friday, brushing and first vacuum in HAM6 (The chamber formerly known as HAM5)were completed. Today, the crew worked on wipe down which took most of the day (that is much longer than it usually takes to wipe down a HAM). The chamber did not look much better after wipe down than it did when cleaning started so Bubba and I asked John to come out and have a look. The crew took some pix including a close-up that shows an "orange peel" surface that appears to retain quite a lot of the original oxide(See below). Second vacuum was completed just prior to end of shift. John asked me to let Rai and Mike Z. know what we have found so that they can weigh in.
Below is Rai's response to the reported condition of HAM6 interior. "I don't know what to make of these surfaces. It looks as though they were heated by welding and then quenched while still fluid. I don't think you can do anything about the surface but I also suspect they are not a major particle source."
(covering shift for Jeff Garcia)
Day's Activities
Jonathan is covering my last 2hrs.
A complete set of M1-M1 transfer functions had already previously been taken for MC2 (HSTS), with damping loops OFF (see LHO aLog entry 3108). Another complete set of transfer functions has now been taken, but this time with damping loops ON (n.b. using the same damping loop parameters as determined for LLO HSTS's, see LLO aLog entry 2705). Both the un-damped and damped MC2 M1-M1 transfer functions have been plotted and compared to the equivalent LLO MC2 suspension, during the same phase of testing (allhstss_2012-06-15_AllHSTS_ALL_ZOOMED_TFs.pdf). Plot Key:- Blue trace = Model Orange trace = MC2 Phase 1b at LLO test-stand with damping loops OFF Black trace = MC2 Phase 1b at LHO test-stand with damping loops OFF Pink trace = MC2 Phase 1b at LHO test-stand with damping loops ON Power spectra have been taken with damping loops both ON and OFF for each stage (2012-06-15_2000_X1SUSMC2_M*_ALL_Spectra.pdf ). Power spectra data, with both damping ON and OFF have been taken, which compare all phases of MC2 measurements (allhstss_2012-06-16_ALL_Spectra_Don.pdf and allhstss_2012-06-16_ALL_Spectra_Doff.pdf). In addition, power spectra for specific degrees of freedom (L, P and Y) can be more conveniently compared across multiple stages (M1, M2 and M3) of the same suspension in the final plots found below (allhstss_2012-06-16_X1SUSMC2_M1M2M3_Spectra_ALL_Don.pdf). Finally, all data, plots and scripts have been committed to the SUS svn as of this entry. This should now be sufficient to complete Phase 1b testing of the MC2 suspension.
I came over to address the FSS issues and found that the laser had shut down at around noon (I would have hoped that the operator would notify me, but maybe he/she didn't notice it). Seems that the NPRO tripped (again!). Got the laser back on line, then started working on the FSS. It appears that something is not right with the database. 0.1 unit changes on the FSS Common gain result in 4 dB gain changes - way too much. I went back to two delay units (left and right) in series to get the loop locking (24 nsec on the left unit and 14 nsec on the right unit). With gains at 0.8/0.3 (Common/Fast) the UGF is near 350 kHz with about 50 deg of phase margin. Auto lock is working with threshold set at 0.2. I will let it run over the weekend and investigate further next week.
Replaced R111 on all four channels from 10K to 100K to fix issues with the signal input selection monitor bits for the PUM. Serial number of unit S1102653.
The ALS PLL now locks stably for several minutes by using a modified version of the servo filter. The bandwidth is about 12.5 kHz and the phase at the UGF is 127 degrees. Earlier the loop was stable with only a very small gain of the common mode servo board (-47dB). Because of that, the PLL range was insufficient and the lock would brake after few seconds. To better redistribute the gain, Keita made a small filter with gain of 1 at DC, a pole a 4Hz and a zero a 4kHz inside of a small Pomona box (see attached schematic). This provides a gain of -40dB above 4kHz and so it relieves the attenuation by the common mode board. Today we connected this filter between the output of the phase-frequency discriminator and the input of the common mode board. After a bit of tinkering with the common mode board gains and switches, Keita found a stable set of parameters. Input 1: ENABLED Input 1 Polarity: ENABLED Com. Comp: ENABLED COM. EXC.: ENABLED Fast: ENABLED Gain IN1: 0 Gain Fast: -6 The lock now breaks only when the laser temperature drifts out of the PZT range (+/- 15V). The slow control will have to make up for that. Work is in progress.
Looked at cabling for ISC at End Y. Found following DB37 cables without Pin 19 connected, or connected to cable shield. Modified cables with pin 19 connected on both ends (not to sheild), and shield connected to the backshell on the female side. H2:ISC-BSC6-20 H2:ISC-BSC6-21 H2:ISC-BSC6-39 H2:ISC-BSC6-40 H2:ISC-BSC6-76 H2:ISC-BSC6-77 H2:ISC-BSC6-78 H2:ISC-BSC6-79 H2:ISC-BSC6-80 Filiberto Clara
The following is a list of work of which I was notified, in no particular order.
Y-End
- Reboot of computers to fix timing error, Jim B.
- Cable work, Filiberto and Rodney
- Viewport location, Cheryl V.
- Many other visitors, but no information about their work
Corner Station
- HAM03 work, Corey and crew, see Corey's entry
Doors locked at 4:20 PM.
HAM6 was placed into a shipping container around January 27th, Corey's alog, and purged with a Nitrogen boil-off from a dewar. To the best of my knowledge it has not been purged since that time. To determine what the humidity levels inside the container were like, a super elaborate no expenses spared contraption was developed to capture the exhaust from the container during the purge (photos attached). Data logging using a testo 645 dew point probe was started as soon as the purge began and ran for about 19 hours (graph attached). Direct LN2 boil-off read at -48.5 td°C, 9.2 °C; while ambient LVEA readings were at 4.4 td°C, 20.1 °C. Purge rate is ~10 L/m with ~5,442 L of empty volume inside the container.
Future data from purges will be stored on the DCC here. T1000714.
Over the weekend (6-15 to 6-18) purge of the HAM6 shipping container.
Attached is a handy Moisture Conversion Table by request of John Worden.
I verified the location of viewports on the A-17B adaptor, and compared those positions to the stated plan in T1000746-v5, and found that the most likely viewport position (VP5) to use for the video camera, has a blank on it. See attached file.
Lisa Austin confirmed today that, at EY on the A-17B Adaptor, VP5 should be a video viewport, but is currently a blank, and VP10 should be a blank, but is currently a viewport.
