With the noise and problems we have been having with ALS X I attempted to Clean the fiber ends at all junctions between the LVEA and the End station. I used a FiberScope to look at the end before and after cleaning. The attached pdf shows one of the worse. This was the fiber that runs from EX patch panel to the Table. This is the patch panel end. All fibers showed visual improvement after cleaning.
I did not take apart the patch panel main runs. This would be the next step if we find this helps.
X end got better, now it's similar to Y. See the first plot (top) showing the past 18 hours or so, zero-power period corresponds to the maintenance. You need to look at peak to peak, ignoring the spikes.
Don't worry about spikes as far as fiber is concerned, that's the result of failed locking attempts after the maintenance (IMC loses lock, FSS is kicked). See 2nd attachment.
TJ is transitioning to LVEA to LASER HAZARD
Since it wasn't posted yesterday:
|
[reply] [−]Descriptionbetsy.weaver@LIGO.ORG 2018-10-01 15:30:08 CDT This morning, TJ went to check the TCS chiller fill levels and discovered that the X one was showing nearly empty. He filled it up, and went to inspect the table and lines. Indeed, he found a 1 sec drip which had developed on one of the t-joints just inside the table enclosure where the lines enter the table and split into 2 directions. The leak caused a puddle on the table in the corner of the leak. He and TVo cleaned up the leak. We then added a trough to catch the water for now while we gear up for a fix tomorrow during the Tuesday Maint window. We'll continue to monitor the trough fill level this afternoon. We may need to turn the chiller off after commissioning completes tonight to avoid the case where the trough fills overnight. |
J. Bartlett, T. Shaffer, J. Oberling
The new fitting has been installed and the leak is tentatively fixed. One of us will check on it near the end of the maintenance window to make sure there are still no drips. We will also monitor the new fitting over the next couple days before declaring final victory, but so far we are leak-free.
With the new fitting in place, the leak seems to be fixed. We will monitor during today and the next few days to make sure before closing the FRS out.
I've attached some pictures of the table after I found the leak.
Jeff Bartlett is on the case this morning, hunting down the last remaining black plastic t-fitting which looks to be a replacement for what is currently leaking on the TCSX table.
Most models which are Dolphin'ed computers in the corner station crashed at 05:03:44 PDT (12:03:44 UTC) Oct 02 2018.
For most computers, all the user models stopped with ADC timeout errors. For some, not all models crashed.
here is the CDS overview before we started the recovery process.
Rolf asked for some information on the cpu cycle count through the glitch. I've two plots of the cpu meter from h1iopsusb123, h1iopsush2a, h1ioplsc0, h1iopasc0. The first plot is in dataviewer and gives the mean round the glitch, the second is from ndscope is is raw data (cpu_meter + cpu_meter_max).
A summary from nds_query giving raw numbers:
Data for 5 seconds starting at GPS: 1222517040
Channel type nWords units
H1:FEC-28_CPU_METER int_4 80
Channel: H1:FEC-28_CPU_METER type: int_4 nWords: 80
0 5 5 5 5 5 5 5 5
8 5 5 5 5 5 5 5 5
16 5 5 5 5 5 5 5 5
24 5 5 5 5 5 5 5 5
32 5 5 5 5 5 5 5 5
40 5 5 5 5 5 5 5 5
48 5 20228 20228 20228 20228 20228 20228 20228
56 20228 20228 20228 20228 20228 20228 20228 20228
64 20228 6 6 6 6 6 6 6
72 6 6 6 6 6 6 6 6
Jonathan, Dave:
Recovery process:
Took h1psl0 out of the Dolphin fabric before restarting the models. Disabled its IXS600 switch port and pulled the IX cable at the rear of the computer. This should insulate the PSL from any further corner station Dolphin issues. We will re-attach when the system is more stable.
Replaced h1asc0's Dolphin cable (this machine reported a Dolphin Gen1 issue). Powered h1asc0 down, replaced 2m cable with new 1m cable temporarily ran directly from IX600 switch C0 port 8 to cpu.
Systematically restarted all models on all computers with errors.
When h1iopseib1 was starting, the computer froze. SSH session was unresponsive, local console was dark. Disabled IXS600 switch port and power cycled computer.
There were DAC errors on h1seib2 and h1seih16, so these IOP models were also restarted.
By the end of the day, h1seib3 was the only Dolphin'ed corner machine which did not get anything restarted on it.
I've started a wiki page to overview these recent front end issues: https://cdswiki.ligo-wa.caltech.edu/wiki/FrontEndCrash
Note that there are expected IPC errors on h1psliss and h1lsc following the disconnection of h1psl0 from the Dolphin network.
h1psliss receives two IPC channels from h1lsc (TRX and TRY normalised photodiode signals). Used for ISS third loop, not needed in the short term.
h1lsc receives one IPC channel from h1psldbb (FF_JITTER). Used to add to OMC-DARM signal. Has not had a useful signal for some time.
Rick is transitioning EX to LASER HAZARD
WP 7842 Updated system managers and PLC code on h1ecatc1, h1ecatx1, and h1ecaty1 to changes made in preparation to migration to TwinCAT3. These include: - Created TwinCAT libraries for the wind fence speed and direction sensors. There are now channels for 8 wind speed sensors and 8 wind direction sensors. Only the first four wind speed sensors and the first wind direction sensor are connected to hardware. - Replaced the input and output structures for the weather, fiber polarization correction, TCS chiller readback, and video control libraries with EL6inData22B and EL6outData22B structures. - Removed AlsCExtra1, AlsCExtra2, LscCAsSpare_E, and LscCAsSpare_F channels from h1ecatc1 PLC2. - Changed IscExtraEnd to IscEndExtra in the end station PLC2 code. A DAQ restart still needs to be done.
J. Kissel Not clear if the end stations need to be rebooted this morning after the corner station front-ends seems to have crashed, but I'm reconciling the ALS EX and ALS EY front-end models with their settings definition files. It is dreadfully obvious from the time stamp that a few filters in ALS WFS control (DOFs 1 and 2) are turned on and off by guardian during the lock acquisition sequence, namely FM9, a -14 dB gain filter. As such, I'm unmonitoring FM9 in the ALS-[X/Y]_WFS_DOF_[1/2]_[P/Y] filter banks. Note that these are filter banks, so I can individual monitor / unmonitor this filter module only, so I have. I've also consistently unmonitored the inputs to these filter banks, which are also guardian controlled, and weren't consistently unmonitored in any of the 6 filter banks. There remains several diffs that are either - related to the fact that we're currently ignoring ALS WFS on the X arm because they're broken LHO aLOG 44206, which appears to be coded into the guardian, or - because (surprisingly) some of the elements of the ALS Y WFS sensing matrices have changed. I attach the remaining diffs that I'm leaving present.
Both X and Y end ALS WFS sensing matrices were changed on September 26th, as reported in 44178.
The new values should be accepted.
The following models / PLCs are planned to be booted today and have differences against their settings definitions file (SDF).
OAF
ASC
CS ECAT PLC2
CS ECAT PLC3
CS ECAT PLC4
EY ECAT PLC2
EX ECAT PLC2
I've screen captured those differences below. For those whom are doing the booting (Jenne, Jeff, Dave, Patrick) try to make sure you've reconciled these changes BEFORE you get started with boots. For the record, the IFO ws in the DOWN state when these SDFs were captured. It also appears as though the entire front-end world has crashed last night, but that does not seem to be affecting the reporting of differences in settings.
We also plan to boot these processes, but they don't have any differences with there current reference file (safe)
CAL EY
CAL CS
I, finally, attach a screen cap of the SDF overview.
ECAT settings don't come back up exactly the same after PLC restart. See attached screenshots of ECAT CS PLC2 and PLC4 after Patrick finished his prep work for TwinCAT 3 this morning in which he had to restart all IFO-related PLCs. Compare these agains the above screenshots taken before the boot.
The TwinCAT system saves its values once minute. After a reboot it will restore to the last set point automatically—in most cases. If the code was changed significantly, it may choose to ignore the old settings and start fresh with all zeroes. The above screens indicate the former, where the settings were restored to the last settings, but probably the sdf was and is outdated. TwinCAT will never use an EPICS/SDF saverestore, this has to be done by a user.
Sheila, Haocun, Terry, Nutsinee
We moved the PSL feed forward summing point so that it happens before the OPO frequency servo filter bank.
WP#7845
Model attached.
Stefan, TVo, TJ, Danny
Stefan has the idea of significantly reducing the amount of time it takes a test mass to reach a final lens by utilizing the ring heater step response and carefully designing an inverse filter to realize the inverse response. We tested the idea in a previous post using Comsol data and were able to get a time series of the ring heater settings necessary to achieve a "step lens". To test this with measured data I took a time series from H1:TCS-ITMY_HWS_PROBE_SPHERICAL_POWER after the ring heater settings had been changed by a reasonably large amount and attempted to perform the same procedure. The matlab zpk model of the system filter and inverse filter are attached figures. There are also comparison figures of the ring heater inputs and another figure their respective responses.
Testing the new ring heater time series:
With an initial lens around 3 microdiopters, the following figure shows convergence to a final lens of approximately -16 +/- 3 microdiopters within the first three hours but is about 1/2 the predicted lens. I might need to take another look at my model to see why this might be.

I cut the script the short because there will probably be commissioners coming in tomorrow so I am using this method (on workstation ZOTWS2) in attempts to restore the original ITMY lens by tomorrow morning (but will run till 9/31 00:00 PST to maintain the lens).
Could the same missing 50% explain why the preloading was off?
Sorry Daniel. This 50% was due to a couple of ridiculous mistakes on my part. The first mistake was that I assumed that the initial step response was caused by a ring heater step of 1 watt when in reality it was caused by a step of 3.13 watts (please see attached image for updated plant zpk model with new gain). The second, and most glaring mistake, was not thinking about the additive power from both of the upper and lower portions of the ring heaters so this left a factor of two missing in my model. I've attached time series of the measured data of the ring heater power compared to the time series from the updated model. I've attached a spherical power time series comparison as well. The final differential lens that the model suggests is 18.98 microdiopters.
In regards to pre-loading, I can update you on how these time series compare to the TCS simulation time series whose input parameters are used in the pre-loading estimates.
The model of the pre-loading estimates use the calibration in diopters/watt on the TCS simulation page.
Spherical power (udiopters) = [ 2*(-9E-6) + 0.9E-6] * P_RH = -17 udiopters for 1 Watt
The first coefficent in the equation is the substrate lens (the factor of 2 for double passing) and the second coefficient is the radius of curvature change.
Here is a comparison plot with the added TCS simulation time series. The simulation appears to be converging to a differential lens of 18 +/- 1 microdiopters.