Everything looks fine here.
If you happen to be on one of the Debian machines, I've been working on the Python scripts for this task. They can be launched from the bottom two buttons (BSC CPS Python & HAM CPS Python) on the OPS>>WEEKLIES screen. They now plot properly calibrated spectra for the CPS with sensor noise specs and save images of the spectra directly to your Desktop folder. The script also looks at the high frequency ASD average (over 80-120 hz) and will say on the xterm window which sensors (if any) are "out of spec". Sadly, these scripts won't work on the Ubuntu machines, because their scipy.signal libraries are too old and don't include welch. Maybe if operators find this workflow easier (push 2 buttons, look at plots, check xterm, and attach images to alog, done) we can convince Hugh to change the FAMIS task.
Per Keita: Spoke with Brian O’Rielly. LLO will be down for an unknown period. LLO ops will contact LHO ops when they are about an hour from relocking. Robert will be doing commissioning work until 13:00. The intent bit has been changed to Commissioning.
These are the commissioning tasks Robert will be working on: 1) Look into mitigating scattering on ISCT1 so we can use POP AIR 2) Bang on HAM6 to make sure dust doesn’t produce blip glitches 3) Put heat source under beam path on PSL to test jitter from air path 4) Shake input arm below 8 Hz 5) Probably for a later date: laser vibrometer on swiss cheese baffle
Hard to tell glitches from optical manipulation to lockloss spikes with these plots. HAM2 (not used) plots are the only ones that seem off spec. Currently OpLev damping is turned off IFO wide except for BS damping only during acquisition.
All looks well. Powers tracking humidity. Odd, little (very marginal)bump in chiller plots. I don't think this is any cause for concern.
Over the past few days and for the foreseeable future I'm running a python script which looks for ADC,TIM,IPC glitches on the end station computers. It scans roughly once a second (not synced to GPS but rather runs a loop and then waits one second). For all models running on the machines h1suse[x,y], h1seie[x,y] and h1isce[x,y] it reports any STATE_WORD which have non-zero values after the upper bits have been masked. For any model with an IPC error, it scans each IPC receiver channel and reports any non-zero error counts (plus IPC type and name of sender). Any latched errors are subsequently cleared by the once-a-minute issuing of a DIAG_RESET by a cronjob (actually happens at about 3 seconds in the minute).
Once I've accumulated some statistics, I'll post a report.
| Work Permit | Date | Description | alog/status |
| 6573.html | 04/11/17 01:37 PM | Move the high frequency lines to 5501.3 Hz and 6001.3 Hz | 35479 |
| 6572.html | 04/11/17 12:41 PM | Install SRC detuning time dependent tracking. Includes update to CAL-CS front-end model, GDS gst-lal calibration pipeline code, updates to the science frame channel list which need to be included in all down stream channel lists so that the GDS pipeline can use those channels. Requires DAQ restart, and modification to separate DMT Frame Broadcaster channel list. Corresponds to gstlal release 1.1.5. | 35462, 35474, 35478 |
| 6571.html | 04/11/17 10:16 AM | Duplicate of WP 6570 | |
| 6570.html | 04/11/17 10:16 AM | Add back in two PEM general ADC channels to the DAQ frame. Both will be 4kHz. DAQ restart required. | |
| 6569.html | 04/10/17 04:44 PM | Unlock MC to reduce ifo. light at End Stations, block OptLev beam, switch off ALS beam, energize illuminator, capture ETM photos for Pcal beam localization investigations. | |
| 6568.html | 04/10/17 02:35 PM | Reduce the cell phone texter alarm level for all LN2 Dewars from 20% to 15%. FRS7835 | |
| 6567.html | 04/10/17 01:39 PM | 1. Update DMT calibration code to gstlal-calibration-1.1.5-v1: i. Bug fix for time immediately before and after data dropouts. CALIB_STATE_VECTOR now marks this time as bad. For a description of the problem, see https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=32486 ii. New algorithm to compute SRC detuning parameters. These are written to the channels GDS-CALIB_F_S and GDS-CALIB_SRC_Q_INVERSE, but no corrections to them are applied to h(t). The calibration group wishes to further develop this so that corrections are applied to h(t), perhaps for O3. (Will turn this on only when new filters are ready.) iii. Addition of option --cancel-callines to remove calibration lines. This is a command line option, meaning we may choose not to use it yet. If used, GDS-CALIB_STRAIN is unaffected. Rather, an additional channel, GDS-CALIB_STRAIN_CLEAN, is written out, which has the calibration lines removed. 2. Run "yum update" to install all patches and updates on all 3 DMT boxes, h1dmt0, 1, and reboot. This is to install updated ROOT library packages and get latest OS patches to bring DMT boxes up-to-date. | 35471, 35472, 35478 |
| 6566.html | 04/10/17 10:31 AM | Spin up turbo pump attached to OMC vacuum tube in LVEA; run Kobelco dry purge air compressor system and QDP80 rouging pumps in mech. room. The purpose of this task it to test equipment needed for vertex vent. | 35465 |
| 6565.html | 04/10/17 09:57 AM | Swap the ITMy oplev laser for a new one. K. Venkateswara noted in LHO alog 35341 that the ITMy oplev had a feature at ~0.44Hz that appeared immediately after the March 7th laser swap and seemed to be causing range drop issues with H1. It is hoped a new laser will remove this feature. No viewports will be exposed during this work. | 35470 |
| 6564.html | 04/07/17 10:09 AM | Return ETMX PCIe card to ETMX HWS computer. | 35469 |
| 6563.html | 04/06/17 09:42 AM | Measure L2A TFs for MC2, Install L2A filters. | 35464 |
| 6562.html | 04/06/17 09:07 AM | Determine the left-right relation in the Hartman wave front sensor (HWS) image by intentionally tilting the ITMX mirror by several micro radians. This measurement will not let the interferometer stay locked. | 35364 |
| 6561.html | 04/06/17 08:23 AM | Regular bi-weekly calibration sweeps. Will be done during commissioning period between 9a - 1p. | 35361 |
| Previous W.P. | |||
| 6541.html | 03/27/17 08:40 AM | Perform scheduled maintenance to scroll compressors at Y-MID vent/purge-air supply skid. Maintenance activity will require for the compressors to run for brief periods of time to check compression. Lock-out/tag-out power to skid as required. | 35149, 35480 |
TITLE: 04/13 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 59Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Been locked for 17 hours. Wind seems to be picking up.
LOG:
Been locked for 13 hours. A brief Grace DB query failed between 1AM-1:12AM. Wind suddenly picked up an hour ago but died down quickly. Not much else is going on.
TITLE: 04/13 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY: Locked for the entire shift. No issues to report for LHO. LLO is still struggling with relocking.
LOG: None.
We have been locked for 5.5 hours. LLO is still currently down and struggling with some mystery noise after the commissioning period today.
I was informed by the Norco delivery driver that the mechanical level gauge (LI105A) at the X-end dewar was not responding to changes in the LN2 level, i.e., it was stuck @ 205" WC. I investigated and confirmed his observation. In doing so, I also discovered that the valve connecting the High and Low lines to this gauge (V-7) was open. This valve is normally closed and shorts out both the mechanical level gauge, as well as, the CDS level transducer which shares these lines and is connected in parallel to the mechanical gauge -> I will repair or replace the mechanical gauge on Tuesday. For now, I closed V-7. This should correct the "noisy" level signal that Chandra had noticed on CDS.
Begin 1 hour standdown.
TITLE: 04/12 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY: No issues handed off. Locked for ~1.5 hours.
Accepted the following SDF Diffs to go back into Observing
for some cameras their EPICS values were no longer updating, even after restarting their processes via monit. We took the opportunity to patch and reboot the machines h1digivideo[0,1,2]
Accept SDF diff for IMC-REFL_SERVO_IN1GAIN setpoint -6 to -8
[Vaishali, JimW, Jenne]
During maintenance, while no one needed the IMC, we tried out our new L2A decoupling filter for MC2. Recall that Jim found that it would be helpful in alog 35330, and we measured and fit TFs for it in alog 35397.
We found that (a) the pre-existing L2A decoupling was in fact worse than doing nothing at all, and (b) that our new filter works well.
In the attached screenshot, the upper left corner is the Foton Bode plot of our decoupling filter. In the other 3 DTT panels we have the coherence and transfer functions of 3 different MC2 L2A configurations. For these measurements, the IMC was unlocked, but MC2 still aligned. The red traces in all panels are with no L2A decoupling at all. The blue traces are with the old L2A "decoupling" gain. That was a flat gain, and clearly was making things worse than doing nothing at all, over a pretty broad frequency range. The green traces are with our new L2A decoupling filter on, and we win almost 20dB of isolation below a few hundred mHz.
We have accepted the new L2A settings for MC2 in the safe and observe SDF files, so they should always be on now.
I've looked at the coherence between MC2 M1 length drive and the two pitch witnesses (MC2 Trans qpd and MC2 M1 Pit) during locks before and after the install of the new L2P feedforward, and things look better. Attached plot shows the coherence between MC2 M1 L and MC2Trans (top plot, blue is before, red after) and MC2 M1 L and MC2 M1 P (bottom plot, blue is before, red after). Below .1 hz the coherence is much better, which should help for wind and earthquakes, which is what I was looking at originally anyways. Above .1hz the coherence is pretty much unchanged, not sure why, maybe the motion is dominated by the table motion at those frequencies?
Always useful to actually post promised plots...
PI mode 19 started to ring up a bit to cause the SUS_PI node to change some of the PLL filters causing an SDF diff. Mode 19 is not one of the modes that we regularly damp while at 30W, but it may have been excited from the wind. I went to clear the SDF diff but just trying to click the unmonitor button would not work, there was an exclamation point next to the "MON" but I'm not quite sure if that was suppose pop up a screen for me that didn't work remotely, or if it was something else. I managed to select the unmonitor all, with only that channel having an FM3 diff, and getting it to accept it that way. I'm worried that this may have accepted the entire filter bank, and there was another screen that I couldn't see that would allow me to choose what parts on that filter bank to monitor.
We are back to Observing and there is a screenshot below of the SDF diff.
I brought this back to how it was before I unmonitored this entire bank, but I unmonitored the FMs since the PI Guardian can change them. I was correct that I was suppose to get another screen for the filter bank when clicking the !MON button, but I could not get this remotely.