24V was tied from CER power racks to junction boxes in LVEA. New 24V will power the following:
1. Photodiode amplifier units (Beckhoff terminals)
2. New ITM spool camera (to be installed, Beckhoff terminal)
3. BRS system (next to BSC3)
4. RGA installed next to HAM4
Cable run goes from CER mezzanine to junction box on top of SUS-R3 (next to HAM4). From this junction box, we split to junction boxes on top of SUS-R5 and SUS-R6. As of now, nothing on the floor is being powered off the new 24V line. New work permit will be required as certain items will need to be powered off.
Compressors #1 and #2 were greased and pressure tested @ X-MID station.
Compression test results: #1 at 135 psi, and #2 at 130 psi.
All compressors and electrical motors were greased.
Both relief valves passed their test.
Both compressors were run tested after service was performed.
Work performed under WP#6309.
Today we took calibration measurements of both end station PCals. See full reports attached if interested. In summary, the newest calibration for EX looks good with the new RX/WS and TX/WS ratios being less than a tenth of a percent from the old values. For EY, the ratios are ~0.5% from the old values. Looking at the raw plots, there is some biased noise showing up from the WS and a very suspect shelf that comes and goes during separate measurements. We would like to retake the EY measurements at the next availability since Darkhan and I believe that it is possibly due to a funky power source we have been using with the WS current amplifier (a 3-way extension cord with a power strip plugged in).
Carlos set the BRS Beckoffs to run on the KVM display. The display cables are right next to the GIGE cable coming from the BRS camera. While the Y and X situation appeared different because Carlos restarted EndY but not EndX, neither system was working correctly as it would appear the camera data was not getting to the computer.
Patrick spotted this suttlety as the cable was sort of plugged in but not snapped/latched and had no indication of data stream. Once these were secured, and the codes restarted, the BEAMs damped quickly and appear to be running normally.
DaveB feels this cable will likely work its way loose with any activity wiggling the connection and may be best to re-terminate the connector.
State of H1: made it locked in NLN
Assistance: Betsy, JeffK, Sheila, Richard
Activities:
Currently:
This morning, all corner station Oplevs were aligned. All suspensions utilizing OpLevs were all aligned and witness sensors trended and returned back to a good, locked, position.
There was a bit of an issue with the BS. It seems that after alignment is executed there's some discharge from the positioner upon disconnecting that causes a predtty moderate 'kick' in pitch which causes the centroid to NOT return to the previously zeroed position, sometimes by as much a 10µrad. Jason and I tried also tried with AC power connected and disconnected. This did not seem to have any affect either way. I also tried just leaving everything in a good centered place and leaving everything connected. After a while there was some drift in pitch of about 2-3 µrad. It's when the PIT/YAW or hand controller module is disconnected is when this effect occurs.
The positioner has been taken into the EE lab for investigation into some dicharge that may be occuring. This work permit will remain open until the End stations can be re-aligned
Attached are the ~weekly ETM charge measurement trends with today's data appended.
Both ETMs have mostly near-zero charge now on all quadrants (plus or minus a quadrant)...
State of H1: issues are preventing lock
Current Issues:
Activities since the end of Maintenance:
State of the Site:
Activities up to 19:41UTC: all times UTC
Just to clarify Robert's work last weekend (alog 31243), he has confirmed that the CPY pitch should be set to -150. I've written this to the SDF DOWN snap file.
P. King, R. Savage, J. Oberling, Yuki
This morning we went in and tweaked up the PSL in advance of LHO's entrance into ER10 next Tuesday. The main activity was to improve the mode matching (MM) to the PMC, although the beam alignment into the FSS RefCav was also tweaked. The ISS was turned OFF for the duration of this work.
PMC Mode Matching
Before tweaking the position of the mode matching lenses (L02 and L03), the PMC visibility was measured:
Since L02 was butting up against the mount for M37, M37 had to be moved out of the way; M37 is the final turning mirror in the path that dumps the 1st order diffracted beam from the ISS AOM into the beam dump immediately to the right of the DBB enclosure (see D0902114 for a layout of the PSL table). This beam path was then realigned so that the 1st order diffracted beam was still dumped in the same beam dump.
The power into the PMC was then turned down using the high power attenuator immediatly after the HPO to ~40W incident onto the PMC (in hindsight we should have done the mode matching at the full HPO power, more on this below). Lens L02 was then moved ~1cm closer to the ISS AOM (this was a gross movement along the rail the MM lenses are mounted on, not a fine move with the lens mount's micrometer), the beam was realigned into the PMC and the visibility was measured; visibility came in at 89.5%. At this point we took a micrometer reading from the micrometer attached to the MM lens mounts as a starting point for fine tuning. We moved the lens a few times, realigning the beam into the PMC and measuring the visibility each time. The results are summarized in the below table (the larger the micrometer reading, the closer the lens was to the ISS AOM):
Micrometer Positions (mm) | Visibility (%) | |
L02 | L03 | |
5.0 | 6.32 | 89.5 |
8.0 | 6.32 | 90.7 |
11.0 | 6.32 | 90.4 |
11.0 | 8.0 | 90.5 |
The MM lenses were left in the final position indicated in the table. In summary we moved L02 by 21mm and L03 by 1.68mm, both moved closer to the ISS AOM.
We then increased the power to maximum and measured the visibility of the PMC at 81.5%. This difference was unexpected. The PMC incident power was then lowered to ~50W and the visibility was measured to be 89.6%. What we think is going on is that at higher powers the ISS AOM is heating up and distorting the beam, which changes the MM into the PMC. This is why I said above that in hindsight we should have done the MM at the maximum power incident to the PMC.
Running out of time and wanting to keep as much of the MM improvment we had made as we could, we decided (after consulting with Daniel) to lower the power incident to the PMC to ~80W; this gives ~67W transmitted by the PMC. To make up for the lost power (we were previously transmitting ~100W through the PMC), we asked Travis (who was watching the operator station) to request "Max Power" from the PSL rotation stage; the max power was reading ~40W. We then used IO_MB_HWP1 to return the power available to the IFO to ~63W; with the ISS ON and diffracting ~3.5% this results in a maximum of ~62W available to the IFO, which is close to what we had before lowering the PMC incident power. We then measured the visibility of the PMC with this new incident power (with the ISS OFF):
We left the PMC in this condition and should be sufficient for ER10/O2.
FSS Reference Cavity
The beam alignment into the FSS RefCav was tweaked. In addition, because of the PMC changes mentioned above the half-wave plate WP4 was adjusted for maximum incident power onto the RefCav. This gave us a voltage on the RefCav TPD of 4.2V, which is pretty close to where it's been sitting since we turned the HPO on in April. The FSS was left in this condition and should be sufficient for ER10/O2.
HPO Pump Diode Currents
With time running out for the maintenance period, we decided not to increase the pump diode currents. They should be good where they are for the duration of ER10 and O2a, but will probably need to be tweaked up before the start of O2b.
Other Miscellanea
Peter measured the AC voltage difference between the PSL table top and AC power ground; this was measured at 108 mVAC. He also measured a 19 mVDC voltage difference between the PSL table top and the ISS AOM driver (the driver sits on the Southeast corner of the PSL table).
We left the PSL enclosure with all PSL subsytems locked and operational. We turned off both Mac Minis in the laser room, as well as the Mac in the anteroom, as is required for Engineering and Observing runs. Should anyone do any work in the PSL enclosure that involves turning these computers back on, please be sure to shut them down when you are done. This closes out LHO work permits 6300 and 6301.
During a discussion of whether the SDF differences counts should be considered as a factor to whether the IFO is in observation mode, Hugh made the observation that the difference count can be changed by the user when switching between the MASK/ALL channel display filter.
For example, if a system has four channels with differences, three of which are monitored and one which is not, then the difference counter is normally 3 (display button defaults to the MASK setting). But if the user presses the ALL setting, the difference count increases to 4. In this example if the monitored channels were made to have zero differences, then pressing the button to ALL would cause the difference count to become non-zero.
Jamie's SDF MEDM alerts the user to this by highlighting the pink indicator if ALL are being displayed. I will follow suit and mark a non-zero SDF-DIFFs as: PINK if ALL chans are displayed, RED if monitored chans are displayed. Note that PINK does not necessarily mean non-monitored channels have differences, just that there is a possibility that this is the case.
WP6287 Add PEM ADC card to h1oaf0
Jim, Dave, commissioning
this turned into a large task. Please see alog 31316 for details. Currently the ADC card is in the chassis and we are not seeing any errors. We will monitor for any recurrence of ADC/DAC errors on this system, or nf_conntrack table errors.
WP6295 Add PEM-EX chans to DAQ for ESD-PS monitoring
Ansel, Robert, Dave
h1pemex was modified to add three test ADC channels to the DAQ at 2048Hz.
WP6303 Run later version of Frame-cpp on DAQ FW2
Jonathan,
as a test of using frame-cpp version 2.5.2 in the DAQ, the new version is being tested on h1fw2. This is the latest version supported by Ubuntu-12. It does have the leap-second modification needed for 31Dec2016.
WP6307 Add BRS Beckhoff computers to CDS KVM
Carlos
The new Beckhoff branded BRS computers at EX and EY were added to the KVM so we don't need to support an additional monitor, keyboard and mouse. These computers do not have an on/off switch, so we are unable to stop them booting up when power is restored after an outage.
WP6306 Update Hartmann Wavefront Sensor channels into DAQ
Kiwamu, Nutsinee, Dave
I have updated the H1EDCU_HWS.ini file now all four hws systems are running the new python code. Starting with the EPICS database file, I made a list of non-string channels (i.e. binary and analog channels).
Interestingly ITMX was found to be missing 14 channels which appear in the other systems. These channels have ITMM in their names. After discussion with Kiwamu and Nutsinee we decided to remove these from the ini file for now.
DAQ Restart
Jim
DAQ was restarted to: add ADC to h1iopoaf0, add chans to h1pemex, add new H1EDCU_HWS.ini.
Following the install of an updated H1EDCU_HWS.ini file this morning, Nutsinee has started the h1hwsey code and the DAQ EDCU is GREEN again. Note to operators, from now onwards if the EDCU block on the CDS overview becomes PURPLE we should investigate why.
Mounted scroll pump to Turbo stand at X-end VEA but didn't run pumps as specified on WP due to lack of NW16-25 adapter. I'll run the pumps and test the interlock next maintenance day.
Dave reported that since h1oaf continued to have issues this morning after some hardware card work, the "fix" he needed to do may or may not cause a dolphin network glitch similar to the events that occurred last Tuesday. Sooo, before he started this "fix", Hugh, Kissel, Sheila and I reconciled all SDF diffs in the down and safe.snap files. We captured many changes made by the commissioning team last night. Hopefully 1) the dolphin glitch won't actually happen and or 2) the SDF cleanup will help with recovering the nice lock from last night. In any case, it forced us to capture the latest and greatest commissioning settings, and a bunch of other mystery settings which have accumulated, so it will be less painful next time.
With the higher sideband power we were limited to ~2 kHz ugf in the PMC with the lowest gain settings. Today, we changed resistor R19 to 4.75K from 1.21K which reduced the electronics gain by about 2.
While having the servo board in the shop we check R16/R17 which are 9.09K/1.00K rather than the 19.6K/1.00K indicated in the schematics. This explains the gain mystery described in alog 31120. The calibration of the slider has been changed is now accurately going from 0dB to 40dB.
We measured the transfer function with 0 dB, 12 dB and 22 dB of gain. The servo goes unstable at 25 dB, so 22 dB should be the maximum used. The ugf was around 1.1 kHz, 3.2 kHz and 9.4 kHz, respectively.
The reason we are not able to go below 1 kHz ugf is todays PSL change which improved the mode matching into the PMC and increased the optical gain (maybe by a factor of 2).
OLTF pictures.
For the first plot we compare the ILS and PMC error and control spectra before and after today's change.The ILS gain is unchanged, whereas the PMC gain slider was set to 6 dB to make the ugf similar to before. We did not apply the 770 Hz pole that is formed by the PZT and the output resistor. The following observations can be made:
For the second plot we set the PMC gain to 0 dB:
WP6287 Add PEM ADC to h1oaf0, reconfigure h1iopoaf0 to read new ADC
Jim installed a 7th ADC into the h1oaf0 IO Chassis this morning. On power up, the IOP model did not start well and reported ADC and DAC errors.
Since we were to restart the h1iopoaf0 model to clear the DAC errors, we installed the new code which reads the new ADC.
After running for about an hour, the h1oaf0 machine stopped making new network connections with the console error
nf_conntrack: table full, dropping packet
repeating frequently. On h1lsc0 we issued the command to remotely take h1oaf0 out of the corner station dolphin fabric, and on h10af0's console we issued the command for it to prepare-shutdown from the fabric. With no connection between h1oaf0 and h1boot (dolphin master) we had little confidence we could reboot h1oaf0 without glitching most of the corner staiton.
Researching the error, we found that it is possible to expand the netfilter connection tracking table size on-the fly with the command
echo 256000 > /proc/sys/net/netfilter/nf_conntrack_max
(the max is at the default of 65536).
This cleared the error and new MEDM's and Guardian could establish CA links, and we could SSH onto the machine. At this point we again issued the dolphin prepare shutdown command with more confidence that it was successful, but there is still a chance of corner station crash.
We will make the larger table size the default by creating the file on the boot server (h1boot)
/diskless/root/etc/sysctl.conf
with one line
net.netfilter.nf_conntrack_max = 256000
will test this on the reboot of h1oaf0 (waiting for a good time if a CS crash is precipitated)
Note that around the time of the nf_conntrack errors the IOP reported ADC and DAC errors. It is still a possibility that the new ADC was the cause of these errors and may be removed it another error is seen.
Will likely propagate to LLO when possible
looks like our change to /etc/sysctl.conf didn't work and the front end computer had defaulted back to 65536. We manually set it to 256000 for now.
The online h(t) pipeline has been restarted at LHO, following a software upgrade to gstlal-calibration (see https://versions.ligo.org/cgit/gstlal/tag/?h=gstlal-calibration-1.0.7-v1 and Redmine issue https://bugs.ligo.org/redmine/issues/4813#change-20027). We are applying a coherence uncertainty threshold of 0.004 for the online calculation of kappas, which is consistent with behavior observed during recent lock stretches (see the figure attached).
This update adds six new channels containing kappa values not gated by the calib_state_vector or by coherence uncertainties:
Note, the filters have not been updated for this pipeline restart. We are still using the filters documented in this aLOG: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=30210.
[IFO]:GDS-CALIB_KAPPA_A_REAL [IFO]:GDS-CALIB_KAPPA_A_IMAGINARY
[IFO]:GDS-CALIB_KAPPA_A_REAL [IFO]:GDS-CALIB_KAPPA_A_IMAGINARY
Note that aggregation of hoft by DCS into 4096 s H1_HOFT_C00 frame files will pick up this change starting from 1162672336 == Nov 08 2016 20:31:59 UTC.
I have rebuilt daqd fw on h1fw2 using a new ldas-tools build (2.5.2). This is the version in use at LLO and contains updated leap second tables. The plan is to compare the output from h1fw2 to h1fw0 and h1fw1 for a week and then migrate h1fw0 and h1fw1 to use the newer framecpp releases next week. In the mean time the daq status page will show differences in the frames between h1fw2 and the other frame writers. This is due to framecpp encoding a different version string in the frame file. Dave will update the daq overview screen to help minimize the differences. This is under workpermit 6303.
As Dave was reworking the DAQ overview screen we noticed an artifact of the daqd fw code. The framecpp version information is only written to full frames (science/commissioning) not to trend frames. So the switch to a newer FrameCPP version introduces a difference in checksum and file length in the science frame as the version string has changed. However there is no change to the minute or second trend files. It would probably be good to have the version string injected into the minute/second trend as well to help figure out issues (if they arise)...
Nutsinee, Stefan
As suggested by alog 31304, we set up a 26:74 mixed input matrix element for PRCL in the next lock:
POP_A_RF9_I to PRCL = 0.0091
REFL_A_RF45_I to PRCL = -849 (yes, a minus sign)
This gave us the expected additionbal slight improvement in PRCL sensing, see the attached plot.
Indeed, this auxiliary noise reduction seems to have given us a range increase of about 5% to 75Mpc.
More importantly though, suddenly the range seemed to be rock-sold, without any up- and down drifts - see the last hour in the attached range plot.
Still to do: PRCL FF & possible modulation depth increase.
After this first step the return will not be as big in terms of range, but the improvement in range stability by itself makes it worth the effort.
We put all this into Guardian (NOISE_TUNINGS), but we didn't test the Guardian yet (the interferometer was too steady).
This is a follow up comparing the ADC noise, the dark noise and measured spectra. ADC noise is about 0.005 cts/√Hz at the input of the filter module. The following table gives the ratio of dark to ADC noise and the ratio of measured noise to dark noise above ~20 Hz.
Photodiode Channel |
Whitening Stages |
Ratio dark/ADC |
Ratio |
---|---|---|---|
REFL_A_RF9 | 2 | ~10 | ~4/3 |
REFL_A_RF45 | 1 | ~4 | >3 |
POP_A_RF9 | 1 | ~2 | >3 |
POP_A_RF45 | 1 | ~30 | >2 |
The strange gain ratio for the POP9/REFL45 combination is partially explained by a cts2V filter bank that is enabled in REFL45.