Today I was able to get down to the lab to finish up the processing of the new AERM-06 (ETMY reaction mass replacement). Before the corner station vent, Gerardo and I were only able to finish the LLO AERMs and part of this AERM-06. I'll need to make time to do the ETMX one prior to needing it after the ETMY vent.
Bubba has transitioned the LVEA to laser HAZARD
Kyle and I turned on purge air skid at EY in preparation for venting Monday.
Dew point measures -44.5degC.
Replaced check valves on compressors #1 & #2.
The DAQ EDCU is currently not connecting to the two old channels on h1ecatc1plc3 (needs DAQ restart), and none of the HWS ITMY system. TJ and TiVo report that the HWS code for ITMY (which runs on h1hwsmsr1) is not stable, whereas the ITMX code on h1hwsmsr is stable. Both computers are running Ubuntu-14, albeit with slightly different kernel versions
h1hwsmsr 3.19.0-49-generic #55~14.04.1-Ubuntu SMP Fri Jan 22 11:24:31 UTC 2016
h1hwsmsr1 3.19.0-73-generic #81~14.04.1-Ubuntu SMP Wed Oct 19 00:03:45 UTC 2016
Both models on h1susauxh56 stopped running at 15:14 PST yesterday presumably due to CER work. I restarted both models this morning to get the auxiliary data flowing to the DAQ again.
Greg, TJ, TVo
We've aligned the ITMX side and got a retro-reflection back and an image on the HWS, however, I'm not entirely convinced we're looking at the HR surface of ITMX since the beam looks smaller than it did before so we're still investigating that. We probably still need to do more fine tune adjustment of the alignment, it's a lot harder without the green beams from the end station to help get our injection beam on-axis with the arms.
Attached are the images taken, they're in different spots because I played around with the picomotors on the periscope a bit to avoid some clipping.
TITLE: 01/05 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
Wind: 1mph Gusts, 0mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.37 μm/s
QUICK SUMMARY: HAM5 HAM6 South door removal has started. Bubba transitioned the LVEA to SAFE earlier this morning.
IMC/IOT2L alignment - progress and an alignment issue to be resolved tomorrow
- Jenne, Keita, Cheryl
J. Kissel I've run detailed analysis on the post-vent transfer functions for all HSTSs -- MC1, MC2, MC3, PR2, PRM, SR2, SRM -- taken in LHO aLOGs 39975 and 39993. All suspensions are free of rubbing at a corner volume vacuum level of ~1e-6 Torr. A few oddballs in the results are due to measurement error: - The gains on the P and Y TEST bank (through which excitation is driven) of PRM were not set to unity, so the P to P and Y to Y transfer functions look like they have higher response than previous measurements, but the scale difference is exactly the extra TEST gain. - SRM transfer functions were taken with the HAM5 ISI in DAMPED only, not ISOLATED, so the second zero in the T to T transfer function shows a cross coupled mode of the ISI. Both are non-issues. Note, I've made a pretty major overhaul to the comparison script /ligo/svncommon/SusSVN/sus/trunk/HSTS/Common/MatlabTools/plotallhsts_tfs_M1.m namely, I've rearranged the measurement list to be alphabetical by IFO, then by optic. This has a few benefits: (1) The optics that we aren't measuring regularly, the LIGO India Optics are at the top. Since they don't get any new measurements ever added, we don't have to increment the measurement counter. We had to before, because they were interspersed between the other IFOs. (2) LLO gets to be at the bottom, so they don't have to increment LHO's measurement numbers when they add a new SUS measurement (3) The list is grouped by IFO, so once you add your IFOs new suspensions, it'll be more obvious if the other IFO's numbers have gotten screwed up. This is a step toward some future better way of handling this gigantic list of data. We'll get there one day! The changes have been committed to the SusSVN repo.
TITLE: 01/04 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: IMC Trans work, CDS cabling, and a temperamental h1ioplsc0 are the highlights of the day. In other work, EY clean room is set up and running, corner station HWSX table is aligned (Y is still in progress), and TCS Y chiller sprung a leak.
LOG:
Measured -30.4 deg C
(CDS team)
The cables for the squeezer were pulled. This should include all cables within the CER, SQZ-R1 and in-between. All cables going to the optics table are in the cable tray towards the squeezer bay. The TT/OFI cables still need to be finished.
I wanted to try restoring the controls configurations of all of the ISI, so I changed the SEI_CONF manager to windy, which caused the EX configuration node to complain about the state of the BRSX. When I opened the BRSX overview, the driftmon was railed at -16k. I logged onto the beckhoff machine and found the C code dead. Looking at time series for the driftmon and cbit it looks like BRSX started getting glitchy, then the C-code crashed on New Years Day. Not sure what happened, but the spikes on the driftmon channel kind of remind me of what happens when someone stays connected the the beckhoff machine and walks away for a couple days. Something also seems to repeatedly ring the BRS up, maybe a result of some code mini-crashes? I don't know, weird stuff. I'm filing an FRS to track this.
[TVo, Jenne, Cheryl]
The IMC is still flashing nicely from yesterday, so we left the MC mirrors alone and worked on aligning the IMC Trans path. We moved the trans path periscope and all of the optical elements in the path toward the PSL enclosure by 3 holes, so all of the path lengths are roughly preserved.
After this, Cheryl removed the HWP that was in the PSL enclosure to rotate us to the wrong polarization (to make IMC flashes easier to see). So, now we're at the correct polarization, but we're still working on getting the alignment back, since that was a pretty thick optical element.
J. Kissel I've taken standard rubbing-check, top-mass to top-mass transfer functions for all suspensions in HAM4, HAM5, and BSC2 now that we're down to about 1e-6 Torr (which is sufficient a vacuum that the suspension positions won't change further from buoyancy). Good news: All suspensions are free of rubbing after pumpdown, including SRM, SR2, SR3 and BS Data files are listed below. Detailed results will be processed and posted in due time. /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR?/SAGM1/Data/2018-01-04*.xml /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/2018-01-04*.xml /ligo/svncommon/SusSVN/sus/trunk/BSFM/H1/BS/SAGM1/Data/2018-01-04*.xml As a teaser / proof, I attach screenshots of each M1 Pitch to M1 Pitch transfer functions for the Triples.
J. Kissel Detailed transfer function analysis of SR3. Everything looks fabulous -- no complaints!
J. Kissel Detailed analysis of the beam splitter's transfer functions also show no problems. Free and clear!
I restarted the h1lsc0 models today. Dave Barker is trending the timing information and state word and may have more to add. But at this point we suspect it is likely a glitch in the IRIG-B as seen yesterday. The system was not responsive via the network via ssh or EPICS CA. The MEDM screen on the control room wall showed everything green, but trying to view the medm screen from another computer (a new connection) failed with the channels not connecting. Going to the console showed that the repeated error 'nf_conntrack: table full, dropping packet'. The system was set to track 64k connections. I changed the limit (until reboot) to 100,000. At that point new connections could be made and the medm screens went red with IPC. I am suprised by this behavior, I would have though the IPC bit would have gone bad on the other machines irregardless of the state of the lsc machine. At this point I killed all the models and restarted them. Then TJ and I went through and cleared all the IPC errors through the site after verifying that they where related to h1lsc0. Reviewing the dmesg output and filtering out nf_conntrack errors showed an ADC TIMEOUT on h1lscaux, h1omc, h1sqz, h1omcpi, h1lsc at 7246965.68s since boot.
BTW: the network filter connection tracking problem seen on h1lsc0 today was also seen on h1oaf0 in November 2016.
alog: Link
The EDCU is configured to read two EPICS channels from the h1ioplsc0 model via channel access (H1:FEC-7_STATE_WORD and H1:IOP-LSC0_ADC_DT_OUTMON). Of the two, the latter should be constantly changing and would show if it froze to a single value. Trending this channel shows that the EDCU did not lose its connection to h1ioplsc0 this morning, but the hourly autoburt could not connect at 10:10 PST. The autoburt could however connect to the user models on h1lsc0 at this time (only the IOP model was disconnected).
Restarted the models again around 22:50 UTC. They are working in the CER moving fibers and such around so we expect this glitch was caused by this work.
J. Kissel I've taken standard rubbing-check, top-mass to top-mass transfer functions for all suspensions in HAM2 and HAM3, now that we're down to about 1e-6 Torr (which is sufficient a vacuum that the suspension positions won't change further from buoyancy). Good news: All suspensions are free of rubbing after pumpdown, including MC1, MC2, MC3, IM1-4, PRM, PR2, and PR3. Data files are listed below. Detailed results will be processed and posted in due time. /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/MC?/SAGM1/Data/2018-01-03*.xml /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PR?/SAGM1/Data/2018-01-03*.xml /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/SAGM1/Data/2018-01-03*.xml /ligo/svncommon/SusSVN/sus/trunk/HAUX/H1/IM?/SAGM1/Data/2018-01-04*.xml As a teaser / proof, I attach screenshots of each M1 Pitch to M1 Pitch transfer functions for the Triples.
Detail results for IM1, IM2, IM3, and IM4, plus the collection are attached. This detailed analysis confirms that they're free of rubbing.
Detailed results for PR3. Note that these latest transfer functions were taken *after* the repaired T3 LF RT SD Top mass coil driver has been re-installed (See LHO aLOG 39946). Everything looks good. This should be enough evidence to close out FRS Ticket 9497. The only that catches one's eye are the apparent extra L resonances in the Yaw to Yaw transfer function. We've seen such features before, and we usually attribute it to the benign effect of poor common mode subtraction in the LF and RT OSEMs. In other words, Yaw is a differential measurement of the horizontal rotation about the vertical center of mass, and it has been polluted by the common mode horizontal measurement which contains Longitudinal. If (a) the sensors / flags are laterally misaligned, (b) the sensor gains are not well matched, or (c) the suspension rotates about an axis that is misaligned with the cage location of the OSEMs, then you would see such an effect as we see. I'd say all are plausible, and again all are benign.
Over the last week we have noticed an anomalous peak in the amplitude spectrum of various sensors on ETMX-ISI, reminiscent of the 0.6Hz peak on HAM 2(?) back when
Looking more closely it seems to be mostly showing up on a few of the CPS channels, St1-H1, ST2-H2 and H3, see the attached screen shot. This data is with the loops on
A little documentation, first(only?) plot shows all five sets of ISI sensors and which channels show the 0.085Hz peaks (a close comparison show that they some channels behave differently from the previous plot)
The second plot is with the ISI in damping only, and the 85mHz peak is gone, not really sure what to say
While looking for something else, I noticed that
ETMY had a similar feature at 0.7 Hz in Aug 2016. Jim and Jeff did some work on it.
see alog 28960.
Not sure if we resolved that one, but maybe it is interesting. I log it here so I don't forget.
Never mind - the previous issue was with a Trans Mon Suspension which had been left undamped and caused a feature at about 0.73 Hz. This feature is at 0.085 Hz, not 0.85, so is not related.