Rick S, Peter K, Matt H
More detailed report to come, but quickly... after a lot of long long days, I think we can mostly claim success that we think we have the ISS array aligned with ~50mV DC readouts from all 8 phtoodiodes (more detailed alog will hopefully have a description of the temporary setup had to get this). We still dont see anything on the QPD though. Maybe as not enough power. Will have one last look tomorrow.
So just some tidy up work now to do on it before claim success (ie lid back on, put baffle back in place (which will need laser light for). I would say 30mins (lets say an hour to be safe :-)). Just to tired to finish it tonight.
Also before we attempt the LLO one I think we need a few modifications/solutions to make it a more efficient process. But we/I have learned alot from this one.
Start of session in cleanroom:
All zero
Start of session in chamber:
0.3um...10 counts
remainder zero
End of session in chamber 6 hours later
0.3um..0 counts
remainder...zero
Earlier today I updated it and added a GPS time channel for testing. I just updated it again. There are 34 unmonitored TCS channels. (see attached)
ISI ST1 and ST2 ACT tripped at 1088286405 GPS. (Jul 01 2014 14:46:29 PDT) HPI ACT tripped at 1088286647 GPS. (Jul 01 2014 14:50:31 PDT) Plots are attached.
08:34 Karen at end Y 08:48 Peter to H1 PSL enclosure to check problem with laser 08:48 Jeff B. to HAM 2,3,4 to work on contamination control 08:49 Filiberto to end Y to work on TCS cabling 09:11 Cyrus restarting the EPICS gateway for the vacuum subnet 09:16 Jeff B. out of the LVEA 09:21 alarm for end Y rollup door open 09:31 Karen leaving end Y 09:43 Cyrus done with EPICS gateway restarts 10:06 Dave restarting the IOP and user models for SUS and SEI BSC 1,2,3 to complete software WD updates 10:32 Dave done with model restarts 10:32 Justin transitioned the LVEA to laser safe 10:35 Call from Praxair driver to inform delivery is ~15 min away 10:51 Dave, Jim B. to end X to install HWS computer 11:08 Rick to join Matt and Peter in the H1 PSL enclosure to help address a water leak on the laser table 11:55 Jeff B. and Andres out of the LVEA 11:55 Dave and Jim B. back to end X 12:12 Jim B. back from end X 13:05 Matt to HAM2 to start ISS alignment work 13:57 Jeff B. and Andres to HAM 4,5 to work on contamination control 14:09 Cyrus to end X to install a patch panel and check the HWS computer 15:19 Cyrus done at end X, going to install patch panel at end Y 15:19 Justin transitioning the LVEA South and East bay to laser hazard 15:33 Jeff B. and Andres done in LVEA 15:39 Arnaud starting measurements on SUS ITMX
I received the patch panels required to finish the wiring at EX and EY, so I installed them this afternoon. I had to briefly disconnect the vacuum rack switch at EX to re-route a fiber that was in the way. This closes out WP 4684.
will be running overnight
This morning I changed the configuration of the EPICS gateway processes that serve the vacuum subnet IOC PVs to limit the allowed PVs to those actually available from the vacuum IOCs. This is to eliminate the additional broadcast traffic that occurs when the gateway searches for PVs that do not exist in this subnet (and it does this a lot, each time a client broadcasts for a non-vacuum channel). Searches are now limited to channels starting with "HVE-" or "H0:FMC-" (this last should probably be constrained further, but this is a good start). Attached is a plot of the reduction in broadcast traffic as a result; the 'mini-peaks' that still occur near the start of the hour are probably from the hourly burt backup for H0:FMC channels not in the vacuum subnet.
J. Kissel, A. Pele Given the confusion of installation status vs what guardians are running what and why, I've brought all corner station guardians down to their equivalent SAFE or OFFLINE or UNLOCKED or DOWN state, and then paused them. These should not be unpaused again until we close up a given chamber and the install is complete. ETMX and EMTY should still be maintained under guardian control, and operators should make sure that they are fully isolated / aligned at all times until further notice.
I'm not exactly sure what happened to instigate all of this, but "guardctrl stop" should be safer than PAUSE. PAUSE is not preserved across reboots of the guardian machine. "guardctrl stop" on the other hand should actually prevent the node from being started after a reboot, which may be what you want in this case (assuming that's what happened).
The latest results from the X1 QUAD08 tfs -after Joe Odel/Jeff B/Andres R reworked on the quad to replace the top mass blades and rebalance the masses- are attached below and compared with the previous measurements from last week. This work was initiated to resolve the 10% discrepancy seen between the measured and modeled 2nd pitch mode frequency (1.32Hz) cf 5th page of 1st attachment. Though, the comparison shows this mode has stayed unchanged, except for a new pitch to vertical coupling at 2.25Hz.
And here's Arnaud's plot comparing this Q8 M0 TF to other QUADs of the same species.
PeterK, MattH, ChrisM, RickS This morning, Peter found that the Crystal Chiller would not restart (apparently the laser has been down since last Friday). He went to the Laser Area Enclosure and found a puddle on the floor near the High Power Oscillator. Removing the HPO covers revealed that a small (~3/16" ID) hose had separated and was leaking. Hose was replaced, water mopped up, chiller restarted, water level topped off. More details and photos to follow.
Just prior to the 08:15 meeting I noticed that the laser was off. I pulled up the laser status screen and the "NPRO running", "Flow error (WD)" and "Frontend flow" indicators were red. I went into the chiller room to find the crystal chiller indicating a flow error and that the water level was close to minimum. I restarted the chiller from the diode room. No sooner than I had reached the door the crystal chiller stopped indicating a flow problem. This time the water level was below minimum, so I added enough water to bring it back to the maximum level. I restarted the chiller and after a few seconds the chiller stopped and the water level was back below minimum. Either we had a leak somewhere or we were getting rid of air bubbles in the plumbing. I went into the H1 Enclosure to check up on the high power oscillator and noticed a couple of large puddles on the floor, a few droplets on the side of the table. Putting the laser into service mode, enabled me to remove the cover of the laser. It was then that I noticed there were some small puddles inside the laser and the burst section of tubing. The tubing was replaced. The flow sensor was removed and examined. No blockages or debris was found in the flow sensor. The system was re-assembled and the crystal chiller restarted. After topping up the water, the crystal chiller seems to be okay. The lid of the high power oscillator will be left off for a few hours to let the laser dry out.
model restarts logged for Mon 30/Jun/2014
2014_06_30 10:45 h1iopsush2a
2014_06_30 10:46 h1suspr3
2014_06_30 10:46 h1susprm
2014_06_30 10:48 h1susmc1
2014_06_30 10:48 h1susmc3
2014_06_30 10:49 h1iopsush34
2014_06_30 10:50 h1suspr2
2014_06_30 10:50 h1sussr2
2014_06_30 10:52 h1iopsush56
2014_06_30 10:52 h1susmc2
2014_06_30 10:54 h1susomc
2014_06_30 10:54 h1sussr3
2014_06_30 10:54 h1sussrm
2014_06_30 10:56 h1hpiham1
2014_06_30 10:56 h1hpiham6
2014_06_30 10:56 h1iopseih16
2014_06_30 10:56 h1isiham6
2014_06_30 10:58 h1iopseih23
2014_06_30 10:59 h1isiham2
2014_06_30 10:59 h1isiham3
2014_06_30 11:01 h1hpiham2
2014_06_30 11:01 h1hpiham3
2014_06_30 11:02 h1iopseih45
2014_06_30 11:04 h1hpiham5
2014_06_30 11:04 h1isiham4
2014_06_30 11:04 h1isiham5
2014_06_30 11:06 h1hpiham4
no unexpected restarts. Install of SWWD on HAMs
Jeff, Patrick, Dave.
I installed the latest IOP SWWD models on the following systems: h1iopsusb123, h1iopseib1, h1iopseib2, h1iopseib3. All SUS and SEI models on these front ends were stopped (using guardian to first put them into a safe state) and then restarted.
This completes the SWWD FE install, I am now cleaning up the MEDM screens.
In the corner of the "cleaning area" adjacent to the door to the LVEA there is now a fully stocked Contamination Control (CC) Area and 3x fully stocked Contamination Control Portable Kits.
These are available for all to use. In fact if you have an open chamber there is no reason you shouldn't have a Contamination Control Portable Kits. How do I know what a Contamination Control Portable Kits looks like? Don't worry they are the BIG PINK Really Useful boxes, and as such pretty noticeable. See attached pdf for picutres of the portable kits and the main CC area.
Further details can be found here LIGO-T1400310: Contamination Control Kits - Parts list, poster and kiting plan and use. At this DCC link you will find slides descirbing the area, a poster of all of the items included in the kits, a correspoding parts list, labels and a chamber entrance guide.
Please see Jeff Bartlett if you have any questions and liaise with Jeff for re-stocking of the portable kits and areas.
Calum Torrie
Last week at LHO (Travis, Betsy, Kate and Calum) tested the TM Green Lantern, LIGO-D1400060-v4, on the ITM in the WBSC3 chamber. The Test Mass (TM) Green Lantern gives a system which allows us to: -
i) Illuminate the optic (in chamber) in a consistent manner at grazing angle to face of optic. (The TM Green Lantern can be installed while first contact (FC) in place. In addition the FC can be removed while TM Green Lantern is in place.)
ii) Highlight dust on the surface of the optic cf. previous methods of illumination (flashlight) which couldn't operate at grazing angle. As such the previous methods illuminatated substrate defects instead of dust on the surface.
iii) Image the dust on the optic (as a result of the effective illumination).
iv) See (and image) the effectiveness of the FC on a dusty optic. (This has not yet been tested.)
The TM Green Lantern is now on site at LHO (class B) under Betsy's ownership. See attached image below.
Calum Torrie (and team listed above).
After this mornings boots (just happened, see more from Dave I suspect shortly), I see that the guardians for all of the SUSes come back in EXEC mode. THey were previously set to PAUSE or other state. Why does it reset to EXEC after boots?
Guardian nodes come up in EXEC after restart. Their state is not preserved across restarts. I understand why this would be an issue, though, so maybe I should work on a way to preserve state across restarts.
Why did the nodes restart, though? Did the guardian machine get rebooted?
Presumably the problem here was that the nodes came up in EXEC, and then went to their default ALIGNED state, which disturbed the optic alignment happening in chamber. One way around this would have been temporarily modify the SUS nodes to come up with the initial request as SAFE. This would have prevented the damping loops from being engaged and the alignment offsets from being enabled.
Joe and Andres finished adjusting QUAD08 so I started a round of TFs on both chains at 12:52. Order is undamped M0, R0, then damped M0 and R0.
First set of measurement failed. Started them again at 23:52:23 UTC.
Transfer functions ran yesterday in the staging building are showing clear sources of rubbing especially in the pitch/length/yaw degrees of freedom for the reaction chain. Main chain has large unexpected cross couplings in pitch.
Andres and Jeff realized the cover was on during that measurement, which is why results were bad. We started them again Friday overnight.