Cyropump #4 was generating alarms today, both before and after Dewar fill. After trending signals, it appears the LLCV and exhaust noise has been growing over time. Pump fill level and LLCV setting stabilized after I opened the bypass exhaust valve. Wondering if the check valve is faulty. Will test tomorrow. I have removed and reinstalled it a couple times in the last month with TC testing.
Kyle, Chandra We ran all QDP80 roughing pumps on site today for maintenance and for refresher (WP 6269); checked for gross leaks in foreline/turbo volumes. Found one at MX. EY as found pressure foreline = 14 Torr turbo = 0.58 Torr after rough pump down and following valve isolation foreline = 0.040 Torr turbo = 0.036 Torr MY as found pressure foreline = 2.3 Torr turbo = 0.60 Torr after rough pump down and following valve isolation foreline = 0.013 Torr turbo = 0.022 Torr LVEA - vertex as found pressure foreline = 2.2 Torr turbo = 0.67 Torr after rough pump down and following valve isolation foreline = 0.017 Torr turbo = 0.022 Torr LVEA - Xbeam manifold as found pressure foreline = 12 Torr turbo = 0.63 Torr after rough pump down and following valve isolation foreline = 0.021 Torr turbo = 0.039 Torr LVEA - diagonal as found pressure foreline = 5.4 Torr turbo = 0.54 Torr after rough pump down and following valve isolation foreline = 0.026 Torr turbo = 0.039 Torr LVEA - Ybeam manifold as found pressure foreline = 5.4 Torr turbo = 0.48 Torr after rough pump down and following valve isolation foreline = 0.025 Torr turbo = 0.034 Torr MX as found pressure foreline = 780 Torr turbo = 1.0 Torr after rough pump down and following valve isolation foreline = leaking turbo = 0.084 Torr EX as found pressure foreline = 6.6 Torr turbo = 0.43 Torr after rough pump down and following valve isolation foreline = 0.017 Torr turbo = 0.026 Torr The leak in the X-mid fore line is between the Turbo Header isolation valve and the Turbo fore line Safety Valve. Removed and examined the NW seals but nothing obvious. We verified each QDP80 shuts down with the absence of N2 purge seal gas supply except the Y-end QDP80 which did not shut down. Y-mid pump turned off due to overheating because cooling water was not valved in initially. It leaked a small puddle of coolant and ran OK upon cooling. We pumped down the purge air line in LVEA unintentionally.
FRS 4559
WP 6247
EX:
1. Placed HWS camera on seperate power supply. The power supply is underneath the ISCTEX table.
2. Finished cabling for RGA at EX.
LVEA:
1. Placed HWS cameras (X & Y) on seperate power supplies.
2. Terminated network cable for RGA in LVEA. Network cable is pulled to SUS-R3. Connection to switch needs to be made in CER.
2. Placed power distribution boxes (24V regulated down to 12V) for the ITM spool cameras, for both X and Y arms.
2. Placed junction box and landed power cables on top of H1:SUS-R5. This is part of the ongoing work for the 24V digital power distribution.
3. Started work on junction box on top of H1:SUS-R6.
The software for the HWS cameras needs to be restarted.
F. Clara, E. Merilh
[Changed the power level on PDA]
I went into the PSL today and changed the ND filter that was screwed on the PDA photodetector module (30415) in order to change the power level of the photo diode. Before the change the PDA DC singal read a relatively small value of 2.2 V. After the change, the DC signal became 3.8 V which is close to what PDB says 3.9 V. Indeed, the voltage readouts for the two diodes shown in the medm became close to each other (~ 4.5V). The new ND filter is actually a stuck of 0.2 and 0.5 abrorptice ND filters. It was an ND1 before.
[New setting for ISS inner loop]
The gain slider now should be 18 dB (which used to be 30 dB, 30415). This gain gives us a UGF of 54 kHz. This means that the open loop transfer function is almost identical to the one with PDB used as the in-loop sensor (29942) as expected. In fact, we can now switch the sensor between PDA and PDB without changing the reference offset or gain while keeping the loop closed. Though this typically changes the diffraction power by a few %. The new gain is now accepted in SDF.
The attached is a plot of the measured open loop transfer function with PDA. Also the raw data is attached. Also, I attach a noise spectrum seen at one of the analog output for measuring the transfer function.
M. Pirello, A. Ramiez, E Castrellon
Work Permit 6271
Per ECR E1600292 we applied the VCO capacitor mod to all 5 VCO's in the corner station and one at each end station. This process includes replacing the 10nF capacitors on C79 and C80 with 2uF capacitors, and checking the voltage rails to verify elimination of the 420kHz oscillations.
Corner Station Units:
S1200563, S1200559, S1200560, S1200564, S1200558
End X:
S1200561
End Y:
S1200566
Notes:
End X, there was a very inconvient clean room pole directly in the path of extraction for the VCO from the rack. We had to relocate 2 chassis to angle the VCO enough for removal. All chassis were put back in their original positions before leaving.
End Y, this VCO required more capacitance to remove all of the 420kHz noise on the -24V Rail, with the addition of a 2nd 2uF capacitor, the noise was eliminated.
After going through my notes, the following should also be logged.
VCO S1200563 is outfitted with a PLL board. This board is attached to the existing board via an SMA-T connector on the Low Noise VCO Board. This connector was very loose when we opened up the chassis, and the end that is supposed to connect to the PLL board was disconnected and wedged between two VCO modules. The SMA was very loose here. We showed Richard this and he advised us to remove the SMA-T and the SMA jumper cable which was disconnected, we then used an SMA cable torque wrench to ensure proper torque on the connectors.
When we worked on the 2nd PLL VCO chassis (S1200564), we noticed that the SMA-T was torqued, and the SMA jumper was attached to the PLL board.
We checked the cleanliness of the double paned port between the PSL and HAM1. The photo shows a smudge on the outside surface that extends into the center of the port. We think that a cleaning would help. There is dust on the inner pane, but I think the smudge on the outside is the most dangerous.
Robert, Cheryl, Gerardo
TITLE: 10/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Entire shift was dedicated to maintenance activities.
LOG:
15:17 Kissel taking SUSes down for model work
15:25 Joe D to mids and ends for first aid kit maintenance
15:26 Fil, Ed to EX HWS camera work
15:30 Marc, Richard to LVEA
15:33 Cristina and Karen to ends
15:40 Gerardo to EY
15:52 Fan lubing complete
15:54 Kyle to EX
15:55 Cintas on site
15:56 Chandra to LVEA
15:59 Marc and Alfredo VCO work
16:04 Hugh to LVEA
16:07 Gerardo to EX
16:08 Pcal team to EY
16:13 Bubba and Richard to LVEA
16:20 Keita, Evan to EX then EY for timing measurements
16:26 Richard out
16:30 Betsy to LVEA
16:32 Robert to LVEA
16:42 Jason resetting Purple People Noise Eater
16:45 Joe D done
17:00 Cristina back, going to LVEA
17:01 Ed, Fil to back, going to LVEA
17:05 Hugh done
17:12 Corey to LVEA 3IFO inventory
17:17 Karen to LVEA
17:20 DAQ restart
17:46 Corey out
17:49 Betsy out
17:58 Chandra working on vacuum roughing pumps
18:11 Norco on site
18:17 Robert to EY
18:30 Kiwamu to PSL
18:41 Richard to EY for RGA work
18:46 Evan G and Keita to EX, Marc done
18:56 Hugh done
19:06 Jason and Peter to PSL picomotor work
19:26 Evan G and Keita done
19:36 Fil to beer garden for RGA work
19:57 Marc, Liz to EX, then EY VCO work
20:18 Peter, Jason out
20:28 Dave to both ends
20:49 Kyle to EX
20:51 Corey to both mids
20:54 Hugh to LVEA
21:02 Chandra to MY
21:04 Dave out, Kiwamu out, Hugh out
21:17 KIwamu to LVEA OLTF of ISS
21:25 Jason, Peter to PSL, Sheila to PSL racks
22:07 Kiwamu, Kyle done
22:29 Fil, Ed done
22:40 Sheila, Ed to look at TCSX laser
22:48 Marc, Liz done
I added 500ml of water to TCSY chiller.
[Stuart A, Jeff K] While debugging and commissioning the LLO ITM LV ESD monitoring I noticed that there is an ADC channel discrepancy in the h1susauxb123 model (see below, just ITMX shown). It is noted that there is an unorthodox convention for the order of the LV ESD monitor channels (as given in D1500464), which is already taken account of in the library LVESD_STAGE_MONITOR_MASTER part (see below). However, in h1susauxb123, the ordering for the ESD quadrants assigned to ADC_7 mistakenly switch the order n.b. this occurs for both ITMX and ITMY LV ESD monitoring. Therefore, I've made the correction to the l1susauxb123 model (see below, just ITMX shown), and LLO shall rebuild, reinstall and restart the model at the next opportunity.
Ticket open in FRS: #6511.
The power supplies for the h1isce[x,y] timing slave cards were inadvertently glitched this morning during maintence when diagnostics equipement was being plugged in. We have labeled these power outlets to prevent future occurance. Models were restarted with no problems.
as part of the cleanup following the filling of /opt/rtcds on Sunday, this afternoon at 12:50 PDT I started a 'zpool scrub rtopt' file system cleanup on h1fs0. At the time of this alog the system is predicting the will complete in 8 hours (11pm PDT).
If anyone notices any slow down of EPICS data from front ends, please contact me.
Pumps will continue to run at X-end RGA for a few more days. Closed cal-gas isolation valves. Manually reducing variac's by ~10% every 2 hrs. today. Bake Summary: Approximately 90% of surface area soaked between 180C < temperature < 210C for 96 hrs.. Additional 72 hrs. manual incremental ramp up. ~10% surface area tapered down to ~90C at turbo inlet line-of-site during soak period. .
(Carlos, Richard, Gerardo)
Y-End RGA is ON.
By "on" I assume that the electronics are energized (i.e. the fan is running) but not the filament?
That is correct, Kyle.
WP6263 SUS model updates
Jeff, Jim, Dave:
Every H1 SUS model was rebuilt and restarted with a new DAQ configuration. Note that the HAM SUSAUX models were sped up from 2K to 4K to permit writing their channels at 4096 to the DAQ (h1susauxh2, h1susauxh34, h1susauxh56)
WP6264 add new DAQ diag channels to the DAQ
Jonathan, Dave:
I upgraded the H1EDCU_DAQ.ini file to add all of Jonathan's new daqd diag channels to the DAQ for trending. I have a python script to generate this file (create_edcu_daq_ini_file.py).
WP6260 add more memory to virtual machine server
Carlos:
Additional memory was added to cdsproxmox. Required restart of matlab server, fmcs ioc, dust monitor ioc, autoburt.
WP6273 Additional Beckhoff diagnostics channels
Daniel, Dave:
Beckhoff PLC code change on all three systems to create new diag channels.
WP6275 New NDS2 client code in control room
Jim B:
New nds2 client code installed for U12 and U14 workstations.
WP6272 DAQD code tests on h1fw2
Jonathan, Jim, Dave:
Testing new cpu affinity/priority code on h1fw2 in order to remove retransmission requests.
DAQ Restart
Dave:
Restarted the daq to support the above tasks.
model restarts logged for Mon 24/Oct/2016 No restarts reported
model restarts logged for Sun 23/Oct/2016
2016_10_23 09:21 h1susitmx
2016_10_23 09:26 h1susbs
2016_10_23 09:26 h1susitmy
2016_10_23 09:28 h1suspr3
2016_10_23 09:28 h1susprm
2016_10_23 09:30 h1susmc2
2016_10_23 09:30 h1suspr2
2016_10_23 09:32 h1sussrm
2016_10_23 09:33 h1isibs
2016_10_23 09:35 h1susetmy
2016_10_23 09:37 h1iscey
2016_10_23 09:37 h1susetmx
2016_10_23 09:39 h1alsex
2016_10_23 09:39 h1asc
2016_10_23 09:39 h1iscex
2016_10_23 09:40 h1ascimc
2016_10_23 09:42 h1lscaux
2016_10_23 09:42 h1lsc
2016_10_23 09:42 h1omc
2016_10_23 09:44 h1psliss
2016_10_23 09:59 h1sysecatc1plc2sdf
2016_10_23 09:59 h1sysecatx1plc2sdf
2016_10_23 10:01 h1sysecaty1plc2sdf
2016_10_23 11:33 h1alsex
2016_10_23 11:33 h1calex
2016_10_23 11:33 h1iopiscex
2016_10_23 11:33 h1iscex
2016_10_23 11:33 h1pemex
2016_10_23 11:34 h1susetmx
2016_10_23 11:36 h1hpietmx
2016_10_23 11:36 h1sustmsx
2016_10_23 11:39 h1isietmx
2016_10_23 11:41 h1iopseiex
2016_10_23 11:43 h1hpietmx
2016_10_23 11:43 h1iopsusex
2016_10_23 11:43 h1isietmx
2016_10_23 11:44 h1susetmx
2016_10_23 11:44 h1susetmxpi
2016_10_23 11:44 h1sustmsx
full /opt/rtcds disk system caused 08:00 - 10:00 restarts. h1iscex ran out of network connections which prompted the restart of all Dolphin'ed models at EX.
model restarts logged for Sat 22/Oct/2016
2016_10_22 18:24 h1fw0
2016_10_22 18:26 h1fw1
unexpected restart of h1fw0 appears to have caused h1fw1 to restart, resulting in loss of frames.
model restarts logged for Fri 21/Oct/2016
2016_10_21 16:25 h1fw0
2016_10_21 16:57 h1fw0
2016_10_21 18:53 h1fw0
unexpected fw0 restart prompted a preemptive power cycle of h1ldasgw0 (not shown). Did get a second unexpected fw0 restart later in the evening.
We recorded AI output of PCAL injection as well as PCAL_DAC_FILT thing together with witness GPS 1pps using Tektronics MSO4043 (1 sec with 1Msample per channel, and 2 sec with 1Msample per channel).
We also recorded the digital output of the PCAL injection as well as digital input of the PCAL_DAC_FILT thing.
Evan will look at the timing comparator data.
These will be analyzed in the near future for further timing sanity check.
Data is stored at /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Measurements/timing. Analysis forthcoming...
Analysis complete. See LHO aLOG 30965.
Andy, Jess, Josh, TJ Following up alog 30790 and comments (range drop may be related to excess RM motion), we've found some very strange motion with apparently quantized jumps in frequency. This motion is seen in accelerometers near HAM1, in the nearby HAM HEPI L4Cs, in the RM mirror motion, and in some REFL and POP DC signals. Some of this motion seems to show up in DARM as well. The first plot is a zoom in frequency on the kind of motion that we see in these channels. It looks like several lines which sometimes jump suddenly in frequency, then jump to another frequency, then another. It looks like a MIDI music file (or a music box). We've found this in many channels, but the clearest so far is in the HAM1 floor accelerometer. It's also in the ISCT1 accelerometer, and the RM OSEMs see it in some degrees of freedom (which is how we first noticed it). The HAM1 and HAM2 HEPI L4Cs see some of it, see second and third plots. Even the HAM6 accelerometer sees some of it, so it's not local just to HAM1/2 - but we haven't checked exactly how widespread it it. We've also checked at least in the HEPI that this was there at an earlier time in the day, and also two weeks prior. The last plot is DARM, showing that this seems to couple at least in the 10 to 20 Hz region. That could be through the RMs somehow, or maybe through scatter from ISCT1. Since the beam diverter was closed (alog 30835), the next locks can check if this is through ISCT1. What's causing this motion? It looks really peculiar. It's hard to pick it out in just a few minutes of data, because the lines are narrow and don't wander - they jump suddenly. So it may have gone un-noticed before, but it would be nice to understand it even if the coupling to DARM is easily fixed.
This is a movie of me fading in and out between seismic and DARM just to show that the seismic features do weakly show up in DARM in the 10-30Hz range. It's a bit too big to attach to the alog, so here's a link.
TITLE: 10/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Aquisition
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Locking DRMI/PRMI was not easy, it required large adjustments and waiting a good amount of time. useism is also getting pretty high so I tried the WINDY_USEISM state, brought it back to WINDY because I couldnt tell which was better. Aside form that the commissioners are working.
I should probably just remove or rename the WINDY_USEISM state. It may have a use, but I think people are taking the configuration guide on the SEI_CONF screen too literally. I'm reluctant to try to make the guide more accurate because I'm not a cubist. The WINDY_USEISM state should be thought of as a more wind resistant state than the high microseism configuration we used during O1 (USEISM in SEI_CONF). Anyone remember how hard locking was with 15mph winds and high microseism during our first observing run?
We are getting into new territory with the current configuration (implemented during the windy, low microseism summer), but looking at the locks last night, it looks like the WINDY configuration is still what we want to use. The five attached plots are the ISC_LOCK state, SEI_CONF state (40 is WINDY, 35 is WINDY_USEISM), the ETMX Z 30-100mhz STS BLRMS (in nm, so 1000=1 micron) and the corner station windspeed. The last plot shows all four channels together, red is the ISC state, blue the SEI_CONF state, green is the STS BLRMS, black is the wind. It's kind of a mess, but it gives a better feel for the time line.
Microseism was high over this entire period (around 1micron RMS), wind was variable, so this was a good time to test. I think the take away is that the WINDY state was sufficient to handle the high microseism for the 2 NLN locks over this stretch, and is very probably more robust against the wind than the WINDY_USEISM state.
This is great to know. I was pretty sure that you said WINDY is good for almost every situation, but I thought it worth a try.
Tagging OpsInfo so we can get the lastest