This afternoon I tweaked up the DBB and took a round of measurements prior to the 70W amplifier install. Something appears to be not quite right with this NPRO laser. Both the frequency and pointing noise measurements show a very large peak between 100 Hz and 500 Hz, with the peak being somewhere in the neighborhood of 260ish Hz. This looks similar to the peak from Peter's NPRO measurements from this morning. We'll have to look into this first thing on Tuesday morning. Perhaps our decision to keep the old NPRO power supply installed was not a wise one, as there can sometimes be odd behavior when using a NPRO with a different power supply. Swapping in the new power supply is fairly painless, so this will be easy to check, although we will then lose the ability to remote start the NPRO laser, and therefore the PSL as well.
I dug up the acceptance test results for this laser (T1500521) and the same peak is present when the power supply that came with the laser was used. So it is not likely to be solely due to the different power supply.
We fixed a couple of issues resulting from the update of userapps to 1.8 today.
1. Several files were found to be not executable in the new userapps, but were in the old. Problem was that the files did not have the executable bit set in the repository. This was changed and the working directory updated.
2. Several data-like files were missing in the new userapps. These files were not in the repository. We made the decision that since in this case these files are small and critical we went ahead and added them to the repo and updated userapps to get them.
The first issue prompted me to write up a wiki on how svn handles file permissions
Corey Terry Nutsinee Daniel
We moved ISCT6 from the squeezer bay close to its final position next to HAM6. To allow for work in the chamber the table is positioned about 1m back from its final position and outside the clean room. All three rear panels have been replaced with temporary blanks. The panel on the left will have to be swapped back with panel 1 eventually to get the AISAIR beam path onto the table. Still to do: Drill mounting holes into two new blank rear panels.
TITLE: 02/16 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
It was decided the corner station will be vented on Tues. 7.5 Magnitude EQ from Mexico ended the shift. Sheila is still in the Optics Lab doing Squeezer measurements.
LOG:
In light of the error made in catching the short on 1 cable of the ITMY reaction chain suspension during chamber closeout last month (see Kissel's alog 40555), we are venting the corner volume for a very short period next TUES-WED (20-21st). Kyle and Gerardo will perform a slow vent and then Gerardo and I will attempt a fix at the feedthru, checking Kissel's spectra template for confirmation of fix. If that does not fix it, we are working through plans and preps to pull the door to the chamber and make the fix from the inside.
The large cleanroom in the biergarden has been turned on by Mark D in prep for this activity and will remain on during the weekend.
During this vent activity, please stand down on the following:
- HAM6 In-chamber work
- Transitioning to Laser Haz
WP7357
Chandra, Dave:
The cell phone alarms configuration was modified in order to:
remove CP4 discharge line pressure channel (and associated error channel)
decrease CP4 vacuum gauge upper alarm level from 5.0e-04 to 5.0-e06 Torr
I also took the opportunity to make some code changes related to running the code in the background under systemd control. The STDOUT verbose reporting is now directed to a time-stamped file. Issuing a SIGUSR1 signal to the code will cause it to open a new reporting file, permitting me to rotate these files and compress the old ones (yes, I know python has logging with rotation, I'm using that to write low level logging output already).
Configuration change for PT245:
H0:VAC-MY_Y4_PT245B_PRESS_TORR VE gauge, MY CP4, CC 9.713e-07 True 0 0 OK NO_ALARM 1.000e-10 5.000e-06
This should be a good configuration for the long weekend and maybe through next week.
The full set of TFs for the newly re-assembled ETMy has been taken, and all appears to be healthy and ready to be passed to the next teams that need to use it for in-chamber work. This is the first set of TFs of the reaction chain with the new AERM, so some of the peaks in the R0 TFs have shifted due to the new mass distribution of the chain (AERM is lighter than the old ERM and the PenRe has been made heavier to compensate). Kissel had a quick look at some of these TFs and agreed that the peak shifting seems reasonable, but noted that the dynamical model for these SUSes will need to be updated.
The TFs can be found in the usual place:
Main chain: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGM0/Data/2018-02-18_2037_H1SUSETMY_M0_Mono_WhiteNoise_*_tf.txt
Reaction chain: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGR0/Data/2018-02-18_2117_H1SUSETMY_R0_WhiteNoise_*_tf.txt
I attach a reaction chain Yaw TF screenshot as a sample of the peak shifting due to the AERM.
J. Kissel Stuart recently discovered that the SR3 optical lever got overlooked during the big SUS HAM 5-6 Computer swap to accomodate new suspensions related to the SQZ upgrade (see IIET ticket 9928). Daniel and I brainstormed several different possibilities after browsing through the HAM3-4 and HAM5-6 SUS wiring diagrams (D1000599 and D1002740, respectively): (1) Buy a whole new ADC card for SUS HAM 56 computer (and associated ADC Adapter Card, Cabling, and AA chassis) (2) Plug the signal -- no matter how icky it is in analog -- into some other suspension's spare spigot (a) The SUSHAM3-4 control chassis has a few spare DB9 ports (especially after the decommissioning of HAM table optical levers) (b) The SUSHAM5-6 monitor chassis has one spare DB9 port After discussing with the systems group, they suggest nixing (1) in favor of (2) for the time being (i.e. until A+). Having no preference for (2)(a) or (b), they suggested looking at the physical location of the cables and ports in the CER to break the tie. I attach pictures of the relevant racks. I had initially thought -- based on the pictures -- we should obviously go for (2)(b): plug the SR3 optical lever DB9 into the spare DB9 port of the SUS-C8-38 AA chassis, which feeds into channels 4,5,6, and 7 of ADC 2 of the monitor chassis. Once in the susauxh56 monitor model, we would then ship the signals over to the h1sussr3 control model via Dolphin PCIe inter process communication, as had already being done during O1/O2 via the h1sussrm model. HOWEVER -- I remember that the AUX monitor IO chassis / computers don't have a Dolphin PCIe cards installed, and Dave confirms this. He also confirms, however, that adding a new card to the IO chassis is a small expense -- but only if we're not short on Dolphin PCIe switch ports. The HAM3-4 racks are on the other side of the "hall" of racks, so it would be possible to connect in that control chassis (which does already have Dolphin PCIe capability) re-routing the cable over to that rack and into the appropriate chassis. So, again, both options in (2) are a toss-up requiring a bit more information to decide between the two. I'll update the ticket, file and ECR, and wait for further discussion with a few more people before making the decision.
Ken disconnected power to the CP4 liquid level and exhaust pressure equipment which is generating email (and eventually text) alarms. Dave B. will remove the exhaust pressure alarm this afternoon along with other changes, including lowering the CP4 pressure PT-245B set point.
The performance of the noise eater was last measured on the 11th October, 2017 in this alog entry. The performance is much better now. Yesterday Jason re-aligned the EOM to the beam. The output of the monitoring photodiode is now ~1.13V compared to the ~0.21V from before. The output power of the NPRO was measured to be 1.743 +/- 0.003 W in front of the EOM. Measured with an Ophir 7Z02692 power meter (S/N 805795) with a 10s average. Attached is the power noise spectrum of the NPRO output. There's quite a broad peak from ~100 Hz to ~500 Hz. I do not recall seeing this in an NPRO's output before. Not sure what it's due to at this point in time.
D. Barker, F. Clara, C. Gray, J. Kissel FRS Ticket 9983. After the corner station dolphin network crashed this morning (LHo aLOG 40574), Corey and I have finished resetting all watchdogs and bringing back suspensions to functional damping and aligned (or misaligned as need be). We've recovered the SEI systems as well but have elected to leave them in "ISI_DAMPED_HEPI_OFFLINE" to (a) have the platforms be more robust against LVEA heavy lifting activity today, and (b) to gather data for sensor correction tuning while the microseism is high and wind is at ~30 mph. As a courtesy, we also restored suspension alignment sliders to their arm-peak values reported in LHO aLOG 40445. We can close the FRS ticket.
In preparation for moving ISCT6 next to HAM6, the HV power supplies for the fast shutter and PZT have been powered off. This includes power supplies in the CER mezzanine and the temporary power supply being used near SQZ-R1 rack. Field cabling to ISCT6 enclosure can be disconnected.
J. Kissel, for D. Barker Dave came in this morning to find that the LSC front-end computer had failed. Upon hard booting the computer and IO chassis, even though he tried his darnedest to gracefully take the computer out of the Dolphin Network, upon restart it broke all front-end processes in the corner station, and even killed the h1susham2 computer software entirely. We're now in the process of recovering.
details on this event:
Jeff, Corey, Fil, Dave:
h1lsc0 models were not running, the computer could not see its IO Chassis. In the CER, there was no activity reported near the ISC chassis at the time of crash (09:15 PST), we found the IO Chassis was fully powered.
On h1lsc0 I closed the models and issued the disconnect-from-dolphin command, and then powered down. On power up, h1lsc0 dolphin glitched the corner station, so all models except for sus-aux stopped running. Around the time h1ioplsc0 model started, h1sush2a froze up. Its console was blank and no sshd service. I waited for h1lsc0 to fully start up to verify its problem was transient.
I rebooted h1sush2a using the front panel reset button. As expected, when it came back it had glitched the dolphin fabric and taken down the lsc models.
I then restarted all models on all dolphin'ed corner station front end computers (except for h1sush2a which had just restarted). Procedure was /etc/kill_models.sh followed by /etc/start_models.sh. Restart order in attached restart log.
Once all the models were running again, I cleared the IPC and CRC errors.
Jeff and Corey are recovering the systems.
A small consolation is that the new Dolphin PCIe Gen2 hardware uses a switch-based method to disable ports that seems to be more robust.
Recovery complete -- see LHO aLOG 40580.
TITLE: 02/16 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
Wind: 26mph Gusts, 23mph 5min avg
Primary useism: 0.24 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY:
On this blustery morning a few activities already in action: EY BSC Arm removal, ISCT6 move prep, H1PSL work, cleaning at MY, & film crew around site.
0004 hrs. local -> Arriving on site to start CP4 watch attended "owl" shift. Working alone with Chandra R. as designated "phone buddy". Won't be doing much other than ensuring scroll pump doesn't shut down due to hydraulic lock as the result of the water vapor laden gas load as CP4 warms and off-gasses. Brought the camper-van so look for me to be at Y-mid VEA, my office or in my van (listening to 70's era rock or conservative radio :) Will make a comment to this entry to update CP4 status or when leaving the site.
As the attached graph indicates, the source of gas went away at about the same time the pressure alarm threshold was exceeded. To justify my visit, I did two iterations of 1)closing the turbo exhaust valve. 2)setting the foreline isolation valve setpoint to 950 Torr (maximum allowed value). 3)cracking open the foreline connection at the turbo exhaust valve (allows the scroll pump to pump viscous room air and blows out condensed water from between the two scroll stages). 4)restoring isolation valve setpoint (now 5 x 10-2 Torr). 0500 hrs. local -> Leaving site now.
attached alarm log for this event
Glad to be back in the safe zone! (for now)