I installed the 2 new local humidifiers yesterday, one in the electronics bay at EY and one in the electronics bay at the CS. The fans were too noisy to put one in the VEA where I wanted it; I did put them on foam to reduce the vibration coupling to the floor, but I think they are too acoustically noisy to put in the VEAs. I have doubts that these are high enough capacity to help, but I set them to come on at a RH of 30, so we wouldn’t have to refill them all the time. John is going to look again into the building humidifiers.
Also, in related activities, I moved the temporary magnetometer to near the ESD feed-through on the ETMY chamber. It would be good for DetChar to monitor for coincidences with blip glitches. Channels:
H1:PEM-EY_ADC_0_08_OUT_DQ, H1:PEM-EY_ADC_0_12_OUT_DQ, H1:PEM-EY_ADC_0_13_OUT_DQ
late entry for yesterday's maintenance
WP6446 Dust monitor install
Jeff B, Jim B:
A new LVEA Dust monitor was added to the system. A new DAQ INI file was created and installed when the DAQ was restarted
WP6451 Vacuum alarm texts
Dave:
CP4 was added back to the daily status texts. The ERROR status of all signals was added to the texts.
Restart Guardian DIAG_MAIN node:
T.J:
DIAG_MAIN was restarted, memory was recouped
New TCS_RH Guardian node:
TJ, Nutsinee
A new node was created. A new INI file was created which was install on the DAQ restart.
WP6452 Update control room GDS tools for leap second change
Jim:
New version of GDS tools was installed.
WP6450 DAQ GDS-Broadcaster reconfigure
Dave, Jim:
daqdrc for h1broadcast0 was changed to stop writing the MD5 check sum file for each frame file is creates.
Remove controlled power strip from Mechanical Room Vacuum Rack
Dave, Jim:
We removed an obsolete remote power strip from the MR Vac Rack. Richard says this was left over from iLIGO as a means of remotely powering the chamber illuminators.
DAQ Restart
Dave:
DAQ was restarted to support many of the above activities. This was a clean restart, h1broadcast0 was quick to start, but unlike the last time did not need a restart.
I've added the Beckhoff SDF diffs as a matrix in the lower left hand corner of the CDS Overview MEDM.
Guardian will not permit observation mode if any of these diffs are non-zero. Similar to the SDF diff display for the front end models, a non-zero will be displayed with a red circular border around the number.
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 20 seconds. TC B did not register fill. LLCV set back to 17.0% open. Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 87 seconds. TC A did not register fill. LLCV set back to 37.0% open.
Dave, Jim W.
We restarted all the seismon code which runs on h1hwinj2. The problem we are investigating is an empy H1O2 directory even though earthquakes with mag>4.0 have occurred.
looks like we are still having issues. USGS code has not reported on a 5.2 at 13:50UTC, it did report a 5.2 at 18:50UTC, which is in our 5 hour window but traveltimes did not report it. Investigation continues.
I have cleaned out the ProductClient/data/listener_storage/origin directory to only files created in the past two days. This directory was getting very full and causing 'ls' to fail.
Users may have noticed that when working on cdswiki you have had to press the "I am LIGO" identification button many times. On Ryan's suggestion we extended the timeout of this identification from 600 to 86400 seconds. The shibd and apache2 daemons were restarted on cdswiki.
Verbal has been crashing at 00:00:03UTC some days and not others. I went through the code and found that it came from the Lock_Logging.py module that records lock data and puts it in a text file. From here I had to track down exactly where and what was going on, but I eventually found the issue and my stupid mistake. I wrote it a long time ago, so that maybe makes me feel a bit better....maybe not.
A good reminder to all the python users out there, because I have fallen into this trap more times than I would like to admit.
>>> a = [1,2,3,4]
>>> b = a
>>> b.append(5)
>>> print b
[1, 2, 3, 4, 5]
>>> print a
[1, 2, 3, 4, 5]
Unlike normal variable assignment, when assigning lists, Python will make both assignments point to the same list ( a -> [1,2,3,4] <- b ). So if you change list a, then list b will also change, and vis-versa.
The Solution: use list()
>>> a = [1,2,3,4]
>>> b = list(a)
>>> b.append(5)
>>> print b
[1, 2, 3, 4, 5]
>>> print a
[1, 2, 3, 4]
Hopefully my dumb mistakes can help prevent someone else making the same ones.
TITLE: 01/25 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC STATE of H1: Observing at 64Mpc INCOMING OPERATOR: Ed SHIFT SUMMARY: Very quiet night. I restarted video1 to run the updated vacuum overview medm screen. H1IOPASC0 reported a timing error, Ed has reset it. LOG: No events logged.
At some point in the night I noticed that the HAM6 HEPI guardian was reporting SPM diffs. Since I was told at one point that this feature of guardian is not used, I have ignored it.
Thanks for noticing Patrick. This is related to the Guardian Pringle loop changes TJ and I did yesterday. I am surprised the HPI Guardian is complaining as we changed the guardian and used the guardian to reisolate the platform. The SPM diffs should clear safely with an INIT but maybe best to wait until a lock loss to do that. The INIT should not trip the platform but I'd like to understand why there are SPM diffs. Maybe if the platform is reisolated using the SEI Guardian rather than the HPI. I've asked the operator to let me know if there is a lock loss so this can be addressed: when the light is green the trap is clean!
The IFO Broke Lock ~2220utc, HAM6 ISI tripped too on Actuators (Shutter Fire.) Ran Guardian INIT on HPI, again, and then on SEI Guardian but these did not clear the SPM diffs. Untripped the ISI and the SEI Manager brought the ISI back up. SPM diffs remain. Executed INIT again on SEI but this did not clear the SPM diffs. Took SEI down to READY (deisolating ISI and HEPI.) SEI Guardian then brough HPI and ISI back to Isolated and SPM diffs are gone. Good things these aren't in Observing bit.
15:59UTC Diag reset. I expect it will be back.
Yesterday, all of the AXIVANE Supply Fans on site were lubricated per FAMIS. The lubrication schedule is quarterly for the fans and semi-annual for the motors. At the out buildings, i.e. mid stations and end stations, we typically only run 1 fan, so when either of the above mentioned lube schedules are performed I rotate the run schedule on the fans at those buildings, I have completed that rotation this morning.
Have remained in observing. I restarted video1 to run the updated vacuum overview medm screen. H1IOPASC0 has a timing error. No other issues to report.
TITLE: 01/25 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
OUTGOING OPERATOR: Nutsinee
CURRENT ENVIRONMENT:
Wind: 0mph Gusts, 0mph 5min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.37 μm/s
QUICK SUMMARY:
No issues to report.
I was tasked by Sheila to find out which of the 1st violin mode harmonics are consistently rung up. We were hoping to see just a few modes that like to ring up so we can have the guardian damp them automatically. However, pretty much everything in 1kHz rings up over time (also true back in O1). Some of the lines seem to be ringing down on their own and some don't. Because we only have 2-3 free violin filter banks per test mass I chose to damp some of the lines that are high and don't ring down on their own. The lucky frequencies that will be damp automatically by the guardian are:
[ITMX]
992.42Hz -- MODE9: FM8(BP), FM2(-60deg), FM4(100dB), -10gain
994.27Hz -- MODE10: FM5(BP), FM2(-60deg), FM4(100dB), -10gain
[ITMY]
994.65Hz -- MODE9: FM8(BP), FM2(-60deg), FM4(100dB), +10gain
998.81Hz -- MODE10: FM8(BP), FM2(-60deg), FM4(100dB) -10gain
[ETMX]
1003.67, 1003.78, 1003.91 -- MODE10: FM1(BBP), FM2(-60deg), FM4(100dB), +30gain -- Luckily the phases work out such that I can make a broader bp filter that covers all three lines. I wish to make more of these for other test masses but they weren't as straight forward.
1004.54 -- MODE9: FM9(BP), FM2(-60deg), FM4(100dB), +10gain
[ETMY]
1009.44, 1009.49 -- MODE1: FM6(BBP), FM4(100dB) +15gain (these two lines are generally the highest of 1k violin amplitude. I don't want to crank up to the gain too much. Just let them damp slowly, safely, and surely)
With permission from Keita I took the IFO out of observing briefly to test all the settings (LLO was down), wrote them in the ISC_GEN_STATES.py, and accepted the differences in the SDFs. I haven't hit the load button yet. I hit load button after a lockloss.
Note: BBP = Broad Band Pass filter (not that broad, actually, just broader than usual)
All the settings were tested for 30+ minutes and will be monitored until the end of shift. I also updated the violin mode table.
Notice that the damping filter of the 1009Hz lines may have an effect on the 2kHz glitch line reported here.
7 hours later the 1009.44Hz and 1009.49Hz are continued to be damped (I gave them a very small gain given their amplitudes). Other modes seem to be done damping.
Borja: I hope the "effect" is a positive one!
Fil called and reported that one of the supplies was tripped upon his arrival.
18:30 - 19:00 - UTC 1/24/2017
Found one of the HV ESD power supplies alarming and screen blacked out. Tried power cycling the unit, but would instantly trip. Removed adapter card from back of power supply and re-seated. Unit was powered on, and set to "Recall 1" settings. Enabled ouput, screen showed 430V.
I turned off Supply Fan 2 at E Y since the weather is warming up and temps seem to be stabilizing (sorta).