Status of H1: down for inspection of PSL / HPO
Activities:
- tomorrow the biggest Mantenance activities are
~21:01 UTC I turned off the camera, frame grabber, then powercycled the computer (then turned the frame grabber and the camera back on). Only HWSX code is running at the moment. Things look good for now.
May 3 16:44 UTC Stopped HWSX code and ran HWSY code alone. HWSX code had been running fine since yesterday.
May 5th 18:20 UTC I noticed HWSY code stopped running. There has been many comuter and front end restart since I left it running so it was unclear what caused it to stop. I reran it again and going to leave it again for another day.
May 2 12:08:37 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Data too long for column 'value' at row 1: Error code: 1406: SQLState: 22001: Exiting. Coincident with Bechoff restarts?
Restarted.
Restarted again. Same error.
This may be different, but we also ended up with a couple of corrupt autoburt files. There the problem seems to be that string values are not properly escaped. A carriage return character in a string will force a line break in the autoburt text file. A burt restore will then complain that the string is not terminated by double quotes.
There are 4 T240 proof masses out of range ( > 0.3 [V] )!
ETMX T240 2 DOF X/U = -0.581 [V]
ETMX T240 2 DOF Y/V = -0.554 [V]
ETMX T240 2 DOF Z/W = -0.433 [V]
ITMY T240 3 DOF Z/W = -0.43 [V]
All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = -0.008 [V]
ETMX T240 1 DOF Y/V = 0.027 [V]
ETMX T240 1 DOF Z/W = 0.026 [V]
ETMX T240 3 DOF X/U = 0.014 [V]
ETMX T240 3 DOF Y/V = -0.188 [V]
ETMX T240 3 DOF Z/W = -0.011 [V]
ETMY T240 1 DOF X/U = 0.004 [V]
ETMY T240 1 DOF Y/V = -0.076 [V]
ETMY T240 1 DOF Z/W = -0.029 [V]
ETMY T240 2 DOF X/U = -0.203 [V]
ETMY T240 2 DOF Y/V = 0.001 [V]
ETMY T240 2 DOF Z/W = 0.12 [V]
ETMY T240 3 DOF X/U = -0.038 [V]
ETMY T240 3 DOF Y/V = -0.033 [V]
ETMY T240 3 DOF Z/W = 0.059 [V]
ITMX T240 1 DOF X/U = 0.056 [V]
ITMX T240 1 DOF Y/V = 0.159 [V]
ITMX T240 1 DOF Z/W = 0.126 [V]
ITMX T240 2 DOF X/U = 0.118 [V]
ITMX T240 2 DOF Y/V = 0.18 [V]
ITMX T240 2 DOF Z/W = 0.182 [V]
ITMX T240 3 DOF X/U = -0.289 [V]
ITMX T240 3 DOF Y/V = 0.153 [V]
ITMX T240 3 DOF Z/W = 0.15 [V]
ITMY T240 1 DOF X/U = 0.154 [V]
ITMY T240 1 DOF Y/V = 0.031 [V]
ITMY T240 1 DOF Z/W = 0.062 [V]
ITMY T240 2 DOF X/U = 0.172 [V]
ITMY T240 2 DOF Y/V = 0.232 [V]
ITMY T240 2 DOF Z/W = 0.173 [V]
ITMY T240 3 DOF X/U = -0.059 [V]
ITMY T240 3 DOF Y/V = 0.186 [V]
BS T240 1 DOF X/U = 0.011 [V]
BS T240 1 DOF Y/V = 0.029 [V]
BS T240 1 DOF Z/W = 0.145 [V]
BS T240 2 DOF X/U = 0.103 [V]
BS T240 2 DOF Y/V = 0.164 [V]
BS T240 2 DOF Z/W = 0.18 [V]
BS T240 3 DOF X/U = 0.054 [V]
BS T240 3 DOF Y/V = 0.057 [V]
BS T240 3 DOF Z/W = -0.05 [V]
All STSs prrof masses that within healthy range (< 2.0 [V]). Great!
Here's a list of how they're doing just in case you care:
STS A DOF X/U = -0.0 [V]
STS A DOF Y/V = -0.0 [V]
STS A DOF Z/W = -0.0 [V]
STS B DOF X/U = 0.081 [V]
STS B DOF Y/V = -1.167 [V]
STS B DOF Z/W = 0.038 [V]
STS C DOF X/U = -0.0 [V]
STS C DOF Y/V = -0.0 [V]
STS C DOF Z/W = -0.0 [V]
STS EX DOF X/U = -0.036 [V]
STS EX DOF Y/V = 0.557 [V]
STS EX DOF Z/W = -0.001 [V]
STS EY DOF X/U = -1.875 [V]
STS EY DOF Y/V = 0.258 [V]
STS EY DOF Z/W = 1.458 [V]
FAMIS 4606 closed.
I assumed that the same noise is present in all 16 coils, but is incoherent, i.e. the scaling factor was sqrt(16)=4. Note that the 10Hz and harmonics are due to pick-up, and thus likely coherent at least in the ITMs. Thanks to the alternating magnet polarity, this coupling likely cancels to some degree for length noise, i.e. the attached plot is an over-estimate.
Superseded. See alog 26948.
(For future reference) The 2 1/2" all metal angle valves used for the VE vent/purge valves and for some of the VE RGA isolation valves are Kurt J. Lesker Co. valves. These are the ones whose only markings are a hand-scribed "CR60R". These are rated for 300C bake out when closed and while under vacuum on both sides of the seat and have operating closing torque range of 14 - 22 (ft*lb).
Because we were focused on the QUAD-centric susaux model changes last month (alog 25313), we screwed up the DAQ channel lists for the HAM models (h1susauxh2, h34, h56) after a change to the master FOUROSEM library part. We turned the NOISEMONs for this library part into filter banks so they needed an _OUT in their channel names. I fixed these today for the 3 sus ham models and Dave recompiled. We have more work to do on these models as per existing ECRs. See attached for an example of how I've left these DAQ channel lists. Note, we still need to deal with the VOLTMONs and switch the T SIXOSEM library part Noisemons.
With Kissel, continued more cleanup work to remove VOLTMONs and add filterbanks to the NOISEMON and FASTIMONs of the h1susauxh2, 3h34, and h56 models. Will continue tomorrow morning to finish tweaking the DAQ channel lists of these. All under ECR E160003.
The last time TCS safe.snap file was updated was April 20th so I accepted TCS SDF differences when TCS guardian nodes are nominal (the one with chiller and ISS servo). Then I unmonitored the channels since the values of these channels are changing slightly all the time as they're being adjusted by the servo.
Before the RCG 3.0.1 Reboot (probably later today), there was an action to go through the SDF System to clean it up, check, or atleast note DIFFS. This is because when the RCG change occurs, ALL front ends will be rebooted! After a reboot, the frontends should check the safe.snap files and restore the systems to a "SAFE" state determined by these safe.snap files.
So this is a best effort to make sure we come back to a safe state, with no major surprises and possibly maintain all accepted changes we had.
SDF file checks were primarily addressed by Subsytem experts:
It is sounding like others are ACCEPTING diffs for their subsystems so their SDFs will look green (assuming they have the safe file selected on the SDF).
I picked a few subsystems to help lighten the load for others. Since I am not an expert on these subsystems, I only took snapshot images of all the DIFFs observed on SDF. SO, these will have some RED DIFFs!
PSL SDFs came up with these files as default on the SDF Overview: DBB(safe), FSS(safe), ISS(down), PMC(safe)
ISS came up with the down file, but it also has a safe file as well (the other ones do not have down files).
Did NOT ACCEPT any DIFFS since I am not familiar with channels here. Jason/Peter are out today so did not want to ACCEPT anything without them.
Took snapshot of:
CS ECAT came up with these files as default on the SDF Overview: PLC1(OBSERVE), PLC2(down), PLC3(OBSERVE)
All had OBSERVE files, but some did/didn’t have safe & downs.
Did NOT ACCEPT any DIFFs. Daniel/Patrick said that would be OK.
Took snapshot of:
EX ECAT PLC1(observe), PLC2(down), PLC3(observe)& PEM (safe)
The ECATs mainly had OBSERVEs (plc2 had a down though).
Took snapshot of:
EY ECAT PLC1(observe), PLC2(down), PLC3(observe)& PEM (safe)
The ECATs mainly had OBSERVEs (plc2 had a down though).
Took snapshot of:
Jenne and I have cleared out all of the SUS DOWN.snap SDF screens. Note, there are no DOWN files for the HTTS, IM, and SR3 SDF screens so we cleaned house on the SAFE.snap for these. All suses are sitting in the DOWN file with the exception of these 3 which are on SAFE. We have left red:
- Some benign diffs on the MC2 SDF because this SUS is misaligned (not a usual state for the SAFE.snap to be looking at)
- Some benign diffs on the IM SDF, commiss message, and MASTER ON/OFF - safe wants the masters to be OFF but we haven't set the sus actually to safe yet.
Other findings which we cleared out were:
- Lots of TRAMPS
- Some alignment settings
- The ITMX and ITMY L2_Drivealign P2L Gain tweek
- The ITMX R0 Opticalign Y offset
See snapshot attached of all the SDFs before we started (minus the IM which Cheryl worked through a bit for mostly alignment and TRAMPS).
I accepted the 2 CAL diffs. See screenshot for what they were.
H1 SEI was cleaned up at about 9:30 local this morning. Rich is currently working on some stuff on the BSC's, but we shouldn't lose too much at this point if it doesn't get captured before any model restarts.
as of last lock 4 April 2016 | |
IM1 p | 187 |
IM1 y | 1118 |
IM2 p | 603 |
IM2 y | -204 |
IM3 p | 1966 |
IM3 y | -79 |
IM4 p | -3865* |
IM4 y | -624* |
*IM4 is currently at p=-3867, y=-615, this is within the expected alignment window required for IM4 to aim the beam into the IFO.
Morning Commissioning:
Rotation Stage:
--- motion has changed, so speeds in programs that control the stage need to be change
--- feature to watch out for: stuck in busy, requires "abort" to end
--- setting home as minimum - requires rotating the optics in the rotation stage mount, not a priority
Guardian - new states need to be verified as safe
EY SEI is drifting
--- working on filters and other electronic signals
--- UW crew is coming tomorrow to do a mechanical alignment
Site Activities:
- Bubba/Chris - LVEA - 3IFO racks
- Fil - LVEA - temperature sensors BSC1 and BSC3
Morning Meeting
- Laser is down through tomorrow
- LVEA is laser safe
- using time to look for noise sources
Subsystems:
- computers will be down today, for an unknown amount of time
- tomorrow morning, ALL CR machines are being rebooted, now the routine is to reboot every Tuesday Morning
- contact CDS if you have questions about specific workstations
Vacuum:
- bake ovens are down, fix is in the works
- beam tube: baking the RGA in the Vertex, which is a 48 hours bake, starting today, so going until Wednesday
Work Permits:
- closed:
--- Bubba, patch and paint
--- Bubba, Mx Inst Air
--- Jammie, Guardian upgrade main process
--- Kawabe, escort film crew
--- TJ, Guardian addition, Hardware injection node, ChrisB
OpLev Trends for past 7 days.
(see also alog 26902)
I measured the PUM coild driver noise of the ITMs at the coil driver output.
Bottom line:
- All 8 chammels (4 ITMX & 4 ITMY) show the same nosie.
- There is significant pickup in the cable running from driver to coil. This corresponsds to the 10msec bursts every 100msec mentioned in alog 26902)
- This pick-up leads to 10Hz and harmonics.
- There is some residual pickup of the same signal in the coil driver, but significantly less.
- above 10kHz there is a huge amount of junk flying around (10uV/rtHz and more !)
The 4 traces in the plots correspond to
Blue: Coil driver output, terminated with 50Ohm.
Red: Coil driver output, with cable and coil attached.
Yellow: Only cable and coil attached. Coil driver disconneced.
Purple: Measurement noise. (Only terminted breakout box)
Attached are
plot 1: 0-200Hz (for example ITMY coil 3)
plot 2 & 3: 0-100kHz (for example ITMY coil 1 & 4) Note the 3kHz line - it corresponds to a 100cts 3kH length drive, resuling in about +-2ct at the ADCs.
Stefan - can you add:
- what state the coil drivers were in for these measurements?
- state of the CD inputs: terminated; connected to AI; connected to DAC/AI; ... ?
Peter:
- The L2 cois drivers were both is state 3: Acq Off, LP On, which is the run mode. They are never switched for the ITMs. (Binary IO medm screens attached).
- The coil driver inputs were left connected to the DAC/AI. I also sent a 100ctpk, 3kHz signal into H1:SUS-ITM[XY]_L2_DRIVEALIGN_L2L_EXC, corresponing to a 2.6ctpk signal on the DAC. I did this to make sure the DAC is as least flipping bits, which raises its noise level. You can also see that signal in the plots at 3kHz. Note though that at 15Hz the total coil driver electronics + DAC noise is still less than what we pick in the cable - blue is below yellow in plot 1.
Superseded. See alog 26948
22:31UTC - Gerardo to CP3 to fill