V. Sandberg & R. McCarthy
The SUS-TMSX OSEM Satellite Box was driving a ~2kHz oscillation on its DC power line again. (See https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=20428) This time we replaced the satellite box. Verified that H1:SUS-TMSX_M1_OSEMINF_RT_IN1 and H1:SUS-TMSX_M1_OSEMINF_SD_IN1 were behaving themselves. Work was done during the interval 18:00 - 18:45 UTC (11:00am - 11:45am PDT).
Apologie: I failed to follow my own rules and neglected to notify the operator on duty before we left and changed out the satellite box at End X. Shame and humiliation duly noted. :-( Fortunately, no damage was done.
We made a state a week or so ago that offloads the ASC in full lock to the alingment sliders. This offloads the top mass of every optic that we control with ASC (except PR3) to the alignment sliders. We are not offloading PR3 since it moves so much due to wire heating.
We've tried this a few times and it works and we are able to relock afterwards, so I've added it to the main guardian path, ater the transition to DC readout.
Kyle, Gerardo Today we replaced the decomposing vibration isolators, vented the y-mid turbo and removed the motor electrical feed through flange that had the 10-5 torr*L/sec leak -> The O-ring was dirty with lots of particulate but otherwise typical -> We cleaned the sealing surfaces of the mating flanges and installed a new O-ring that we had "slathered" with Krytox - > Pumped volume with QDP80 for 90 minutes followed by full spin up and spin-down of the turbo -> we then isolated the turbo volume from the foreline and observed the pressure rate of rise -> it appears that we reduced the leak but it is not clear if the pressure rise observed is due to a reduced air leak, wet surface out gassing or a combination of both -> the observed pressure after 24 hours will help answer this
h1susex re-install original computer WP5430
Dave, Carlos, Jim:
The original h1susex front end computer was re-installed at EX to fix the glitching seen with the newer faster computers. The script which was clearing the EX glitch errors has been stopped, any FEC errors will now latch on until cleared by the operator.
h1tcscs model change WP5422
Duncan, Nutsinee, Dave:
The new L1 TCS model was installed on h1tcscs. A new TCS_MASTER.mdl was used. The h1tcscs.mdl file was modified to: add the ez_ca_read parts to get TCS CO2 and Ring Heater channels from the Beckhoff computers (corner and end stations) into the model; add new inputs to the CO2 parts for RH input; add ODC output from the CO2 parts; add new ODC block; add SHMEM ODC sender (to be injested by h1odcmaster model).
I discovered that there is a naming mis-match in the Beckhoff Ring Heater channels in the corner station slow controls system. There is no mismatch in the end station Beckhoff systems. I modified h1tcscs use use the H1 names.
Conlog channel reconfiguration
Dave:
After the TCS, CAL and ASC model changes I rescanned the channel lists for Conlog. It still showed a disconnection for the Guardian LSC_CONFIG node, which I tracked down to a very out-of-date autoBurt.req file for h1guardian0 target. I updated the autoBurt.req file and reconfigured Conlog, it is now happy.
H1LSCAUX filter coeff load
Dave:
The h1lscaux model was reporting a modified filter file. I took a look and could not see any difference between the current file and the archived file. I pushed the coeff-load button to clear this.
DAQ Restart
Dave:
After the TCS, CAL and ASC model changes, the DAQ was restarted. There were no GDS frame broadcaster changes made today (ECR is pending).
CDS overview is nice and green. The only red we expect are the TIM bits on the ETM Quad Suspension models now they are running on slower computers (a rate of about four per day is anticipated). We are investigating offloading the violin mode monitors from these models to resolve this.
I have updated the RCG Versions MEDM screen, all models are running RCG SVN version 4054 (2.9.6)
Dave mentioned to me if you notice a red TIM error on the ETM models (i.e. H1SUSEY [EX]), click the button for the offending ETM (i.e. H1SUSETMX_GDS_TP.adl). Here you will notice a red CPU Max value. To clear this, hit the Diag Reset button on the upper right of the window (under the GPS time).
I did this for ETMx at around 6:50utc (23:50pt).
model restarts logged for Tue 11/Aug/2015
2015_08_11 08:37 h1calcs
2015_08_11 08:57 h1iopsusex
2015_08_11 08:57 h1susetmx
2015_08_11 08:57 h1susetmxpi
2015_08_11 08:57 h1sustmsx
2015_08_11 09:00 h1alsex
2015_08_11 09:00 h1calex
2015_08_11 09:00 h1hpietmx
2015_08_11 09:00 h1iopiscex
2015_08_11 09:00 h1iopseiex
2015_08_11 09:00 h1iscex
2015_08_11 09:00 h1isietmx
2015_08_11 09:00 h1pemex
2015_08_11 10:15 h1asc
2015_08_11 12:03 h1tcscs
2015_08_11 12:54 h1broadcast0
2015_08_11 12:54 h1dc0
2015_08_11 12:54 h1fw0
2015_08_11 12:54 h1fw1
2015_08_11 12:54 h1nds0
2015_08_11 12:54 h1nds1
no unexpected restarts. CAL model change, SUS-EX computer swap-out, ASC model change, TCS-CS model change, supporting DAQ restart.
This morning, the ASC system was found to be blasting signals out after the model change because the inputs and output switches in the main loops were still ON even though all of the Guardians were set to DOWN for maintenance day. So, I set the SDF to capture that the h1ascsafe.snap should restore the INPUT switches to OFF, then the Guardian will turn them on when appropriate later. I watched the guardian turn them on during transition, just now, so all is good.
The AA chassis D1500176 with PI band Pass filter was installed at EX/EY this morning. Units were installed in rack SUS-C2 slot U21. Units installed: S1500143 - EY S1500144 - EX Filiberto Clara
I checked the LTS containers in the LVEA today, I increased the flow to the SUS cluster and included a recent dew point plot.
Chris Soike assisted me with the annual lubrication of the axial vane supply fans today.
Elli, Alastair, Nutsinee
The CO2X IR temperature sensor doesn't behave like it should. I turned the variable resistor while pointing the sensor out to the room until it tripped, turn it back a quater turn to untrip it, put my hand infront of it and it didn't trip. Then I tried 1/8th of a turn (still required a quarter turn from the tripping point to untrip the alarm), still couldn't trip it. Eventually I turned the resistor so close to the tripping point and still was not able to trip it with my hand. We didn't have this problem with the CO2Y IR sensor we installed last week. We are suspecting bad sensor and now looking for a spare. Hope to try again next Tuesday (given the spare sensor is found). The sensor mount has been installed on the viewport.
New ASC model was installed.
SDF showed more than 6000 channels that are not available in the frame. These were either deleted in this model uptate (entire Initial Alignment System, some Alignment Dither System signals etc.) or obsolete channels from long time ago (e.g. all ASC-ALS signals that were moved to ALS model a long time ago).
Betsy made a new snapshot and we confired everything in SDF for new channels.
Note that the ASC MEDM screen is NOT updated. Functionality of the new model is exactly the same as before (new things introduced at LLO are terminated at the top level at LHO except new dither system).
Just after I wrote the above entry, I was looking at the old model file again and caught something that I didn't yesterday: The output matrix signal order was funny (OM1, OM2, TMSX, TMSY, then OM3).
I went back to the new model, and unfortunately it turned out that the new model from LLO "fixed" the funny order by reshuffling TMSX, TMSY and OM3 signals in the matrix. What used to be the matrix elements for TMSX, TMSY, OM3 are now for OM3, TMSX, TMSY, i.e. the TMSX signal is now sent to OM3, and TMSY signal to TMSX.
Since the guardian is not touching this output matrix, we decided to just manually change the output matrix (not the model, but the epics values for corresponding matrix elements). After this change, new output matrix MEDM screen was pulled from svn and everything was fine.
New ASC master medm was also pulled from svn and it looks OK.
I updated the input matrix MEDM, but everything was white on that one so I put the old one back.
And, SDF has been updated to capture the new matrix elements in the ascsafe.snap
A few SDF bugs for the next upgrade please:
1) Today, in SDF I needed to UNMONITOR 2000 channels on H1 LSCAUX. However the SELECT ALL - MON button at the top of the column of 40-per-page does not let you mass-select channels from the the FULL TABLE view. You can only mass-select from the DIFF table. However, if there are no diffs on the channels, they don't show up. Likely this is because the FULL LIST is a mixed bag of monitored and unmonitored channels. Maybe we need to add a MONITORED table to the drop down options?
2) Sometimes channels get moved into the CHANS NOT MON list with or without a setpoint. (See attached.) Probably not a big deal, but annoyingly inconsistent. Today, I moved many of the channels shown in the attached picture to the not mon list and only some of them have a setpoint.
This was necessary as most had somehow been snaped while fully isolated. While at it, most all medms were looked at and unnecessary offsets, switches and settings were zero'd, turned off, and checked. All STATE_GOOD values where available were corrected as needed so these can be used to confirm settings--green is good. GAIN_GOOD/BAD does not work for non unity gains so rely on SDF. All SDFs were verified for appropriate NOT_MONITORED channels and greened. SEI is ready to go.
WP 5427 Old raw minute trend files have been copied from the the SSD RAID array to the /frames directory to make room for continued writing in the SSD array. The h1nds1 daqdrc file has been modified to allow h1nds1 to read the relocated data, this change will take effect when the DAQ is restarted at the end of maintenance.
While looking at a few big glitches, I noticed that many have a curious post-glitch feature around 300Hz. The post-glitch ring seems to match the periscope frequencies we usually see noise at... could this be a hint as to the source of some of our glitches? Maybe this was fixed last night, maybe not.
Looking at all the glitches previously indentified, it runs out that only 17 out of 151 show an excitation of the periscope peaks, as found by Matt. Here are the times:
1117617558.82
1117690781.51
1117713007.28
1117754567.25
1117873501.47
1117888336.85
1118320556.34
1118336224.73
1121762741.96
1121942076.77
1121966658.37
1121986392.35
1121991554.23
1122466633.18
1122474562.14
1122479776.82
1122484101.65
Shivaraj, Darkhan
Summary
We replaced whitening filters on Delta L_{res} output channel with 2 zeros and 2 poles zpk, and Delta L_{ctrl} with 3 zeros and 3 poles zpk.
Details
Madeline uses FIR filters to dewhiten Delta L_{res} and Delta L_{ctrl} in GDS scripts. To make it easier to generate shorter dewhitening FIR filters for these channels she requested to replace the existing 5 zeros and 5 poles zpk filters in both of these channels with simpler, less poles and zeros zpk's.
Shivaraj designed new FIR filters for both of these channels, and we implemented them today around 1pm.
Power spectrum of H1:CAL-CS_DARM_DELTAL_CTRL_WHITEN_OUT before applying new whitening filter plotted in attached "H1-CAL-CS_DARM_DELTAL_CTRL_WHITEN_OUT_z5x1_p5x100_MAG.pdf". After applying new whitening filter, zpk([1; 1; 1], [500; 500; 500], 1), unfortunately the interferometer wasn't stable to take a spectrum measurement after I changed the filter, so I couldn't evaluate "whiteness" of the output in this channel.
Power spectrum of H1:CAL-CS_DARM_RESIDUAL_WHITEN_OUT before applying new whitening filter plotted in "H1-CAL-CS_DARM_RESIDUAL_WHITEN_OUT_z5x1_p5x100_MAG.pdf". After applying zpk([1; 1], [500; 500], 1), the spectrum of the same channel is given in "H1-CAL-CS_DARM_RESIDUAL_WHITEN_OUT_z2x1_p2x500_MAG.pdf".
We also plan to implement similar whitening filers on new (not yet existing) channels for Delta L_{TST} and Delta L_{PUM/UIM}.
Below are plots showing the effect of differnet whitening filters including the one that was being used unitl now (5 x 1Hz zeros and 5 x 100 hz poles). These plots are the basis for new filters for DeltaL residual and DeltaL control. In those plots blue curve corresponds to actual data and other colors represent different whitening filters applied to the data.
With the new filters installed we looked at the DeltaL residual and DeltaL control during a recent lock. Below we have attached the spectrum of both along with DeltaL external as a reference (which is still being used with old 5 x 1 Hz zeros and 5 x 100 Hz pole filter). In the plot the channels are dewhitened with the corresponding filters.
The S number and S/N for the "old" satellite box for SUS-TMSX_M1_OSEM SD and RT channels are:
S-number bar code S1100176
S/N 3202-022
The identifiers for the new box will be obtained at a future oportunistic entry to the EX electronics racks area.