As per Aidan's request, I have added the missing razor blade beam dump to a specific mirror on the HWSX path on the table. See attached - although it's a picture of LLO's HWS table, ours now has a beam dump in the circled location. Although Aidan may elaborate more, basically he asked for this since he sees evidence of scatter coming from this path.
Note, there is a beam dump already in the (debunk) HWSY path for this ghost beam.
Evan G., Travis S., Yuki, Sadakazu, We made our bi-monthly Pcal calibration, this time for End-Y. Attached are the notes from the calibration work. The trend report after Matlab analysis with this and the previous measurements can be found at T1500131-v12. The trend looks quite good and within expectations.
Today I swapped the glitching ITMy laser for one that has been stabilized in the lab. This was in response to the ITMy oplev being the winner on several recent DetChar hveto rounds.
To be on the safe side, B. Weaver turned off the oplev pitch damping on the ITMy suspension for the duration of the work. I began by installing the armored fiber and cooler per ECR E1500408; this new installation is shown in the attached picture. The laser is powered by the dedicated oplev power supply located in the CER. This was unplugged when I started the swap, thank you R. McCarthy for getting it working. I unplugged and removed the old laser, and then installed the armored fiber. I set the laser power by monitoring the Current Mon port on the back of the laser (uses a voltage to monitor the current being delivered to the laser diode); I set this to 0.885 V, the same setting used in the lab. The new laser will need 4-6 hours to come to thermal equilibrium in its new home; once this time has passed I will see if any adjustments are needed to the laser power to stop any glitches. The oplev became un-centered during this effort due to the fiber swap, so I then re-centerd the oplev. I also had to adjust the whitening gain for the ITMy to get the SUM counts back to same level. I added 6dB of whitening gain to return the SUM counts to ~31k; T1500556 has been updated to reflect this change. Finally, Betsy turned the ITMy oplev pitch damping back on.
Old laser was SN 105-1, new laser is SN 189-1. I will leave WP 6513 open until I have finished any adjustments to the laser power to obtain glitch-free operation.
WP 6514 Carlos, Jim Added a digital video camera to h1digivideo0 as HWS CAM 0 in place of VID-CAM09. Modified H1VID_DIGITAL_OVERVIEW.adl, added camera to monit, modified the configuration file for camera 9 to use the IP address of the camera. Address was also added to DNS as h1hwscam0, and was configured for DHCP. Camera is currently viewing a bunch of cables in the MSR. This setup is for testing the camera for eventual use with the HWS X at the corner station.
At yesterday morning's meeting it was pointed out that there are temperature fluctuations in the laser room. Sure enough plots of the temperature at the north and south ends of the table, and the relative humidity, do show repetitive excursions. One thing that is a little puzzling is that the same temperature excursions are not seen by an AD590KF temperature sensor that is located on the table after the reference cavity. There is no low pass filtering that I am aware of that would mask the trend. The other option is that the temperature sensor interface box is not working. However the last time it was examined in the EE Lab (~1 - 2 years ago) is was just fine. The LED power indicators on the front panel do not suggest anything untoward. So I cannot explain the different signals.
This morning I turned on 6 new wireless access points (2.4GHz / 5GHz) in the OSB in preparation for replacing our existing system.
The access points are installed in the following locations:
They were powered up at:
$ date Tue Mar 7 11:11:49 PST 2017 $ date -u Tue Mar 7 19:11:50 UTC 2017
This afternoon I turned on 5 additional wireless access points (2.4GHz / 5GHz) in the LSB in preparation for replacing our existing system.
The access points are installed in the following locations:
They were enabled at approximately 15:30 PST (23:30 UTC)
Powered up a different style GigE camera today to see if it can be used on the HWS table to look for beam clipping. The camera is in the MSR and will be looked at over the next day or two.
With the issues of temperature in the PSL this past week and some anecdotal evidence of the system not responding properly when people are changing setting we rebooted the controller this morning. Everything looks to be back to normal and the system is functioning. One item to note is that the makeup air unit seems to maintain its setting and stays on in low mode with the power removed from the controller.
TITLE: 03/07 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC STATE of H1: Preventive Maintenance OUTGOING OPERATOR: TJ CURRENT ENVIRONMENT: Wind: 11mph Gusts, 8mph 5min avg Primary useism: 0.07 μm/s Secondary useism: 0.20 μm/s QUICK SUMMARY: Start of maintenance Ken heading to end Y to install conduit, drilling
TITLE: 03/07 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Locked at 65Mpc, but in Maintenance.
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Observing the whole shift till the last 15min because maintenance activities began.
LOG:
16hour lock at 65Mpc. Environment is calm but the Hanford commute has started.
TITLE: 03/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
Wind: 16mph Gusts, 13mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.21 μm/s
QUICK SUMMARY: Breezy but otherwise calm. 11 hours at 65Mpc.
TITLE: 03/07 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
H1 locked for 11hr40min
LOG:
ALL TIMES IN UTC
2:23 Big LF glitch in DARM. waiting for h(t) DMT Omega to update for more details
5:10 Low temp in PSL Verbal alert
5:39 Low temp in PSL Verbal alert
H1 Observing, 64Mpc. Locked for 7hr40min. winds trending below 20mph. One LF glitch.
With a nudge from peterF and mevans, I checked to see how hard it might be to do some time-domain subtraction of the jitter in H1 DARM. This is similar to what Sheila (alog 34223) and Keita (alog 33650) have done, but now it's in the time domain so that we could actually clean up DARM before sending it to our analysis pipelines.
The punchline: It's pretty easy. I got pretty good feedforward subtraction (close to matching what Sheila and Keita got with freq-domain subtraction) without too much effort.
Next steps: See if the filters are good for times other than the training time, or if they must be re-calculated often (tomorrow). Implement in GDS before the data goes to the analysis pipelines (farther future?).
I was finding it difficult to calculate effective Wiener filters with so many lines in the data, since the Wiener filter calculation is just minimizing the RMS of the residual between a desired channel (eg. DARM) and a witness (eg. IMC WFS for jitter). So, I first removed the calibration lines and most of the 60Hz line. See the first attached figure for the difference between the original DARM spectrum and my line-subtracted DARM spectrum. This is "raw" CAL-DELTAL_EXTERNAL, so the y-axis is not in true meters.
I did not need to use any emphasis filters to reshape DARM or the witnesses for the line removal portion of this work. The lines are so clear in these witnesses that they don't need any help. I calculated the Wiener filters for each of the following channels separately, and calculated their estimated contribution to DARM individually, then subtracted all of them at once. H1:CAL-PCALY_EXC_SUM_DQ has information about the 7Hz line, the middle line in the 36Hz group, the 332Hz line and the 1080Hz line. H1:LSC-CAL_LINE_SUM_DQ has information about the highest frequency line in the 36Hz group. Both of those are saved at 16kHz, so required no extra signal processing. I used H1:SUS-ETMY_L3_CAL_LINE_OUT_DQ for the lowest frequency of the 36Hz group, and H1:PEM-CS_MAINSMON_EBAY_1_DQ for the 60Hz power lines. Both of these channels are saved slower (ETMY cal at 512Hz and MainsMon at 1kHz), but since they are very clean signals, I felt comfortable interpolating them up to 16kHz. So, these channels were interpolated using Matlab's spline function before calculating their Wiener filters. Robert or Anamaria may have thoughts on this, but I only used one power line monitor, and only at the corner station for the 60Hz line witness. I need to re-look at Anamaria's eLIGO 60Hz paper to see what the magical combination of witnesses was back then.
Once I removed the calibration lines, I roughly whitened the DARM spectrum, and calculated filters for IMC WFS A and B, pit and yaw, as well as all 3 bullseye degrees of freedom. Unfortunately, these are only saved at 2kHz, so I first had to downsample DARM. If we really want to use offline data to do this kind of subtraction, we may need to save these channels at higher data rates. See the second attached figure for the difference between the line-cleaned DARM and the line-and-jitter-cleaned DARM spectrum. You can see that I'm injecting a teeny bit of noise in, below 9Hz. I haven't tried adjusting my emphasis filter (so far just roughly whitening DARM) to minimize this, so it's possible that this can be avoided. It's interesting to note that the IMC WFS get much of the jitter noise removed around these broad peaks, but it requires the inclusion of the bullseye detector channels to really get the whole jitter floor down.
Just because it's even more striking when it's all put together, see the third attachment for the difference between the original DARM spectrum and the line-and-jitter-cleaned DARM spectrum.
It might be worth pushing the cleaned data through the offline PyCBC search and seeing what difference it makes. How hard would it be to make a week of cleaned data? We could repeat e.g. https://sugwg-jobs.phy.syr.edu/~derek.davis/cbc/O2/analysis-6/o2-analysis-6-c00-run5/ using the cleaned h(t) and see what the effect on range and glitches are. The data could be made offline, so as long as you can put h(t) in a frame (which we can help with) there's no need to get it in GDS to do this test.
Do you think it would be possible to post the spectrums as ascii files? It would be interesting to get a very rough estimate of the inspiral range difference.
In fact, I'm working on a visualization of this for a comparison between C00 and C01 calibration versions. See an example summary page here:
https://ldas-jobs.ligo.caltech.edu/~alexander.urban/O2/calibration/C00_vs_C01/L1/day/20161130/range/
I agree with Other Alex and I'd like to add your jitter-free spectrum to these plots. If possible, we should all get together at the LVC meeting next week and discuss.
Sheila, Kiwamu,
This is a followup/update on the beam pointing jitter measurement (34112). We simulated beam pointing jitter with FINESSE.
If we believe the simulation results, we can draw two conclusions:
The plot below shows a preliminary result of the simulation with H1's O2 specific parameters.
Some details of the simulation can be found in T1700080 (although the results in the document are specifically for a full power interferometer). Here is a brief list of remarks.
I think that the excitement found in the power plots and the chiller plots have been best described in Jason's alog
See CSWG log 11204
TITLE: 03/06 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
OUTGOING OPERATOR: Travis subbing for Corey
CURRENT ENVIRONMENT:
Wind: 32mph Gusts, 27mph 5min avg
Primary useism: 0.22 μm/s
Secondary useism: 0.25 μm/s
QUICK SUMMARY:
Travis reports nothing notable for handoff