I reset both PSL power watchdogs at 17:40 UTC (9:40 PST). This closes FAMIS task 3639.
FRS 7447
WP 6507
The GDS software in the control room has been updated to gds-2.17.9-2 (branch) to correct a bug in foton and add an enhancement to the NDS2 interface to diaggui. This affects Debian 8, Ubuntu 12.04, and Ubuntu 14.04 workstations.
For control room use, the following bugs were fixed:
Bugzilla 1072 - Add GDS channel names to the list of channels displayed using the NDS2 interface. This allows ${IFO}:GDS-CALIB_STRAIN channels to be analyzed using diaggui.
Bugzilla 1075 - Changed format of the gain coefficient in filter files as written by foton to include more decimal places. Some filters with very large gains were being flagged as having a mismatch between design and coefficients because not enough decimal places were used (with very large gain values) and the filter could not be reconstructed accurately using the coefficients from the filter file. Note that the affected filter files will still report this condition with the new version of foton until foton is used to rewrite the filter file with the new format.
As per LHO WP 6501, this morning I temperature tuned the HPO pump diodes after last Saturday's pump diode current increase. I began by turning the ISS OFF and then proceeded to tune the HPO pump diodes' operating temperature. The old and new pump diode operating temperatures for the 7 diodes in each diode box are listed in Table 1 below.
| Diode Box 1 (°C) | Diode Box 2 (°C) | Diode Box 3 (°C) | Diode Box 4 (°C) | |||||
| Old | New | Old | New | Old | New | Old | New | |
| D1 | 25.5 | 25.0 | 20.0 | 20.0 | 22.0 | 22.0 | 24.5 | 24.0 |
| D2 | 26.0 | 25.5 | 19.5 | 19.5 | 26.0 | 26.0 | 22.0 | 21.5 |
| D3 | 28.0 | 27.5 | 20.5 | 20.5 | 26.0 | 26.0 | 23.5 | 23.0 |
| D4 | 24.5 | 24.0 | 18.5 | 18.5 | 23.0 | 23.0 | 22.0 | 21.5 |
| D5 | 26.5 | 26.0 | 18.5 | 18.5 | 27.0 | 27.0 | 24.0 | 23.5 |
| D6 | 26.0 | 25.5 | 19.0 | 19.0 | 21.5 | 21.5 | 24.0 | 23.5 |
| D7 | 23.5 | 23.0 | 19.5 | 19.5 | 22.5 | 22.5 | 24.0 | 23.5 |
In addition, I increased the current to DB1 by a further 0.2A to bring it closer to the other diode boxes; this diode box is starting to decay more rapidly than the others, so is likely to need replacement first. A summary of the old and new HPO diode box operating currents is shown in Table 2 below. The PSL HPO is now outputting ~169.0 W.
| Operating Current (A) | ||
| Old (pre-2/25/2017) | New (2/28/2017) | |
| DB1 | 51.0 | 51.7 |
| DB2 | 51.0 | 51.5 |
| DB3 | 51.0 | 51.5 |
| DB4 | 51.0 | 51.5 |
Following that, with the ISS still OFF, I then proceeded to tweak the beam alignnment into the PMC; only small tweaks were necessary to to maximize the transmitted power. With the ISS turned back ON, the PMC transmitted power is now 65.0 W and the PMC reflected power is now 14.0 W. This closes WP 6501.
TITLE: 02/28 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventative Maintenance
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.18 μm/s
QUICK SUMMARY: Locked for 49 hours 42 minutes at the time I took the IFO down. I asked Keita if we could keep the IFO up to better our new O2 lock record but he said "Take it down!."
IFO in Observing for some 48.5 hours. A2L and PIs are OK. Weather and environment are good. Other than one large glitch, no operational troubles noted.
Reset Timing error on H1IOPASCO
TITLE: 02/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Observing the entire shift other than a quick a2l.
LOG:
LLO just unlocked so Im currently running a2l. We have been locked for 38.5hrs.
[Keita, Dave, Kiwamu]
WP 6506, ECR E1700074 (waiting for approval as of now)
We have added a subblock at the top level of h1asc.mdl to accommodate the newly installed bullseye sensor (34154). If the ECR is approved, this change will be implemented tomorrow during the maintenance period at earliest. The channel names will be PSL-DIAG_BULLSEYE_*.
We made sure that the model compiles without errors. So the model is ready to install. This is an H1-specific change. We didn't change the ASC_MASTER model at all for this change [don't be confused with Jenne's activity which edited the ASC_MASTER model (34444) and is orthogonal to our activity]. The attached are screenshots showing how h1asc.mdl looks like with the addition of the bullseye block.
LLO has been using an offshoot of the ASC_MASTER simulink model that generates almost all of our ASC and ADS channels. It seems that the only thing they added was several extra ADS filter rows, so that they could use some of them for spot centering, and still have others available for other things.
By using an offshoot though, they have missed out on many of the upgrades that have gone into the LHO ASC.
This is something that has an issue tracker open in FRS 7287. Once we both do an svn checkout and are using the main ASC_MASTER block, this issue should be close-able.
I have replaced the LHO ADS part with the LLO version, which includes 10 each ADS filters for pitch and yaw, rather than 5 each. This also removes several inputs that we had been using for testing during commissioning time over the summer, but no longer need (AS36 channels). The modified ASC_MASTER part is checked into the svn, ready for LLO to pull.
Unfortunately, LLO also had re-ordered the input matrix to make the order make a bit more sense. Since they have calls to this matrix interleaved several places in their guardian, and we only use it in ENGAGE_SRC_ASC, I have prepped the guardian code to handle the change. In ISC_LOCK, lines 2470-2476 should be commented out (or deleted), while lines 2482-2489 should be un-commented. The first set of lines is our existing code, and the second set is the re-ordered version for the new input matrix. This must be done after the ASC model is restarted tomorrow, before we get to ENGAGE_SRC_ASC in the lock aquisition sequence.
Note that LLO should need to do no work, and make no code changes, to keep the same functionality that they currently have, since I've chosen LHO to be the ones to change the guardian code. The only thing they should need to do is change the link in l1asc.mdl to the ASC_MASTER block, rather than the offshoot they've been using. They'll have a few extra epics channels floating around that they won't use (like RF90 centering, which we will again use after the post-O2 vent), but everything should work as before.
If there are problems with ENGAGE_SRC_ASC tomorrow and I'm not in the control room, call me. But hopefully we'll finish maintenance early enough that we can go through that state before the end of the day.
This reconcilliation was done under work permit 6505. After we restart the ASC model and the DAQ, we can close out this permit.
MEDM screens are updated and ready now too.
I need to check the a2l script, since it uses the ADS system and will have a few channel name changes.
Hopefully after this, we can go back to having the same model and not diverging, so that we don't have to reconcile....
A2L script is prepped too. We'll need to copy ...uapps/isc/l1/guardian/isclib/matrices_newAsOf28Feb2017.py to ...uapps/isc/l1/guardian/isclib/matrices.py after the ASC model reboot, and then we can run the script with the new ASC code.
WP 6503
Plan today was to re-terminate the HV ion pump connector. The old connector was cut off and cable tested with a volt meter. No short. A more valid test would be to HiPOT the cable with no connector installed to ensure no other cable issues. Since this requires access to the mechanical room at EY, work was put on hold for tomorrow's maintenance window. See alog 34386 for troubleshooting of cable last Friday.
F. Clara, R. McCarthy, G. Moreno
TITLE: 02/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 31mph Gusts, 19mph 5min avg
Primary useism: 0.17 μm/s
Secondary useism: 0.41 μm/s
QUICK SUMMARY: Winds are up but we are still observing at 61Mpc on a lock going on 33+hours.
TITLE: 02/27 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 55Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
H1 locked and Observing, going on 33hr35min. Winds starting to pick up to near 40mph
LOG:
17:55 Travis and Betsy to MX
18:08 Fil and Gerardo to y-28 to fix a cable
18:55 Timing error in EX (known issue/in consequential). reset itself.
18:56 Travis and Betsy to MY
19:30 Richard out to Fil and Gerardo
19:38 King Soft on site to service RO water.
19:45 Richard back from visiting Gerardo and Fil
20:00 Fill and Gerardo back
20:33 Automated phone call from Hanford Emergency regarding monthly testing from 12:20PST to 2:30PST. Area sirens will be sounding at approximately 1:15PM.
22:08 Jason and Betsy goin to MY
23:56 Jason and Betsy are back.
Data was good throughout the four days. Hyperlinks are behaving strangely for me in the html editor so here's the URL of the shift report: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20170223 Overall Summary: - Duty cycle of 82.2% for the four days. - First two days were hit with many EQs and aftershocks. Our duty cycle was actually pretty good considering how many spikes there are on the summary page's seismic BLRMS plots, but they did cause some locklosses. - Work was done to damp PI modes at times and they were noted in the aLogs but they were not blamed for any locklosses. - Evening of the 24th some opportunistic commissioning was done. - PSL tripped at 8:38 on the 25th. Expert was needed to get things working and were out of Observing for a little more than 3 hours. - Interesting 3.5M EQ from central Washington on Sunday the 26th knocked us out of lock but did not show up in the normal EQ band seismic noise plots. Instead, large spikes showed up in all of the higher frequency ground motion plots (> .3 Hz).
Apollo is working at Mid X on the HVAC controls upgrade and have the supply fans for the building off until sometime tomorrow. May see some slight temperature excursions until the fans are operable again.