Stefan, Dave:
we temporarily hooked up two timing signals in EY this morning and early afternoon. After acquiring data we have reverted the system back to its original configuration.
IRIG-B signal in frame.
To acquire the IRIG-B signal into the DAQ frame, we used the PEM channel H1:PEM-EY_MIC_VEA_MINUSY_DQ for this measurement. This channel was recording the IRIG-B signal between the times:
19:45 - 21:53 UTC.
To route the IRIG-B from the computer rack we borrowed the BNC coax cable which normally routes the 1PPS from the TCT to the first channel of the timing comparator. Therefore this comparator channel did not have any useful signal between the times 19:45 to 22:45 UTC. It is now restored to its running condition.
Local GPS receiver into Comparator.
To check what would happen if a local GPS receiver's 1PPS were to be connected to the timing comparator, we hooked the Symmetricom GPS receiver (which is in the VEA CDS rack and connected to an iLIGO GPS antenna on the roof) to the second comparator port. To acheive the connection, we found a long BNC coax cable which runs under the roll-up door between the CER/EBAY and the VEA. It was disconnected both ends. The GPS receiver was already powered on and had green LED indicators, so we assumed it has good satellite coverage. The comparator recorded a time difference of about 100nS. After the conclusion of the test, the long BNC coax cable was disconnected both ends and re-coiled.
Ops Day Summary:
As of 2:00PM
as of 2:06PM
as of 4:00OM
I updated the fmcs alarm config file to put the RO Water system in it's own catagory, so it's easier to see, and easier to differentiate RO Water from alarms that are truely CRITICAL the moment they trigger.
New RO_WATER Guidance:
$GUIDANCE
Reverse Osmosis Water System is in alarm.
The site may have potable water for
a while, but eventually will run out.
Call John or Bubba
$END
Channels removed per John's OK:
CHANNEL CRITICAL H0:FMC-MY_CY_H2O_SUP_DEGF
$ALARMCOUNTFILTER 300 300
CHANNEL CRITICAL H0:FMC-MY_CY_H2O_RET_DEGF
$ALARMCOUNTFILTER 300 300
CHANNEL CRITICAL H0:FMC-MX_CY_H2O_SUP_DEGF
$ALARMCOUNTFILTER 300 300
CHANNEL CRITICAL H0:FMC-MX_CY_H2O_RET_DEGF
$ALARMCOUNTFILTER 300 300
No longer CRITCAL alarms, and do not need to be in the fmcs alarm handler.
The high-voltage power supplies for the PSL servos ( in rack PSL-R2 ) were relocated to the CER mezzanine. Effected boards are: PSL Injection Lock Servo - T0900577 PMC Locking Servo - T0900577 TTFSS Fieldbox - D1100367 Peter King was able to lock PMC after our work was complete.
In an email conversation Norna had asked what we could do to reduce motion on the HAM's in the RX/RY dofs at 25-35 hz. This morning I took a few measurements to design a FF filter. I've taken a first pass at it and I think I have something that works. Attached spectra are of the ground STS X and GS13s in RY the first png, then both sensors in X on the second plot. The live measurements are with FF on, references are from a quiet time last night, FF off.
The third attachment is a plot from the script I used to do the filter fit. Blue is the filter, green is the ideal fit from the St0 L4C's to the ISI GS13's, red is the fit from the HEPI L4C's to the ISI. The design approach is exactly the same as I talked about in my alog 18045.
I also have Y and Z feedforward working on the SRC HAMs. I attach performance plots (taken at the same time as the plots from my main post). These have been running on HAM4 for a little while (sometime after ER7 ended), but I never got around to doing the alog and I was a little more organized when I installed them on HAM5 today. First plot is Y, second is Z. Active measurement is with FF on, reference is FF off. Again, we really need a cavity to say if these are good enough, but I leave them running for now.
I've looked at X, RX and RZ, but RX and RZ show low coherence and X looks... messy, see last plot.
That was quick! Looking good. Thanks.
J. Kissel, J. Warner Some additional information and/or a "current status:" ISIs HAM2 and HAM3 do not have any ST0 / HEPI L4C feed-forward running. ISIs HAM4 and HAM5 have Y, Z, and RY ST0 L4C (not HEPI L4C) feed-forward running. (HAM6 is currently vented and the ISI and HEPI are locked.) The HAM4 and HAM5 filters, for Y, Z, and RY live in FMs 2, 3, and 4 respectively. The gain for all DOFs on both HAMs is 0.5. Norna's designing / modelling how adding blades between the HSTS's lowest stages will improve performance in the SUS's vertical displacement. The input motion for the SUS's suspension point in vertical is composed of the ISI's center of mass moving in Z, RX, and RY (see T1100617). She noticed from the results Jim posted (T1500289), that at 25-30 [Hz], the input V motion was dominated by RX / RY of the table. So, among other ways to improve the performance at these frequencies (see them discussed in SWG aLOG 11327), Jim tried improving the RY DOFs today -- and won! Nice work, as always, Jim!
There was a problem with HAM5 at the time I took this data. I've taken new measurements from HAM4, see alog 19343. Conclusions remains the same, I think, but the data is cleaner.
Committed the change to svn and restarted all of the code. Burtrestored to 6:10 this morning.
J. Oberling, E. Merilh
We swapped the oplev laser for ETMx; power cycling the laser did not improve its behavior. Old laser SN 197, new laser SN 106-1. The old laser will be bench tested to see if we can find out what's wrong and if there's anything we can do about it here (possible return to MicroLaser)
We installed the 50lb lead vibration absorbers on the ITMx and ITMy oplev receiver piers. The ITMx oplev did not need to be realigned after the installation; we did however realign the ITMy oplev after installation. All lead vibration absorbers are now installed at LHO (ETMx, ETMy, ITMx, ITMy).
Added 262 channels. Still 707 channels unmonitored since restart of end X TwinCAT code.
Dave restarted the gateway and the channels have reconnected.
Updated C:SlowControls on h1ecatc1, h1ecatx1 and h1ecaty1 to latest revision in svn. Restarted all TwinCAT code. Required multiple restarts. Burtrestored all to 6:10 this morning. A number of channels at end X have not yet reconnected. WP 5298.
Everything operating as expected. ISI also nominal.
From Ed's summary yesterday, assumed to be the same, since no emails about changing to Laser Hazard:
We are currently LASER SAFE in the corner and the ends. PSL is shuttered, CO2 LASERs are OFF. End station Viewports and tables are closed and locked. Not sure about the on/off statues of the ALS.
Timeline - Last night:
Timeline - This morning:
I had forgotten to mention the Pcal LASERs.
With a mix of old, really old, & non-functioning, I went ahead and replaced all H1 door handles and installed them such that all of these tables and the TCS tables are consistent (i.e. door handle opens the same way). I gave a pile of keys to Richard (who will probably pass on to Peter K, LSO). All tables are currently locked.
Calum, Matt, Kate
The floors around HAM6 were so spotless you could eat off of them. Thank you Karen and Christina!!!
A 4th cleanroom was added onto the current setup, along with 2 tables. We finished rinsing the last 2 panels with methanol. Drag wiped both uncoated and coated side of each panel at least 2x, and then added hardware.
Particle counts:
Particle Size (μm) | |||||||||
0.3 | 0.5 | 0.7 | 1.0 | 2.0 | 5.0 | Humidity | Temp | Notes | |
1:30 PM | 10 | 0 | 0 | 0 | 10 | 0 | 30% | 75 F | starting work |
3:35 PM | 30 | 10 | 0 | 20 | 0 | 0 | 35% | 71 F | |
4:30 PM | 0 | 0 | 10 | 0 | 0 | 0 | 37% | 70 F | before break |
5:17 PM | 30 | 0 | 0 | 0 | 0 | 0 | 37% | 70 F | after break |
6:29 PM | 0 | 0 | 0 | 0 | 20 | 10 | 35% | 69 F | end of day |
A while ago there was a request for representative spectra of current HAM ISI performance at LHO. I posted a number of documents like pngs, ascii data files and DTT xmls to T1500289 in the DCC. I've now posted a similar document for the ETMX BSC-ISI at T1500318. The data is from about 8 AM on June 11, during ER7, and it's not exhaustive, but useful for a quick snapshot of the BSC's current performance.
Forgot to mention: all plots are calibrated in nm/nrad.
I set up an accelerometer on the beam tube and measured the accelerations as I simulated the tapping that I observed during cleaning, and my tapping experiment mentioned here: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=19038. Examination of the time series indicated that accelerations during typical taps reached about 1 m/s^2. I suspect that some taps reached 1g. The figure shows spectra for metal vs. fist taps. The above link notes that I was unable to produce glitches while hitting the beam tube with my fist. The fist and metal taps both had about the same maximum acceleration of 1 m/s^2 (ambient acceleration levels are about 4 orders of magnitude lower), so the source of the difference in liberating the particles is probably not acceleration. Instead, it may be the change in curvature of the beam tube, which would be expected to be greater at higher frequencies. The responses from metal taps in figure 1 peak at about 1000 Hz while the fist taps peak at about 100 Hz. These results are consistent with a hypothesis that the metal oxide particles are liberated by fracture associated with changes in curvature rather than simple vertical acceleration.
When I was producing glitches in DARM for the link above, I noticed that we did not get glitches every metal tap but every several metal taps. I tried to quantify this by making many individual taps at several locations along the beam tube. Unfortunately, we lost lock with the first loud glitch and I did not get a chance to repeat this before the vent. Nevertheless, it would be good for DetChar to look for smaller glitches at the time of the taps given below. Allow a 1 second window centered around the times given below for my tap timing uncertainty. I tapped once every ten seconds, starting at ten seconds after the top of the minute so that there were six taps per minute.
UTC times, all on June 14
Location Y-1-8
20:37 - 20:38 every ten seconds
20:47 - 20:50 every ten seconds
Next to EY
20:55 - every ten seconds until loss of lock at 20:56:10
I don't think the IFO stayed locked for the whole time. The summary page says it lost lock at 20:48:41, and a time series of DCPD_SUM (first plot) seems to confirm that. I did a few spectrograms, and Omega scanned each 10 seconds in the second series, and the only glitch I find is a very big one at 20:48:00.5. Here is an Omega scan. The fourth tap after this one caused the lock loss. Detchar will look closer at this time to see if there are any quiet glitches. First we'll need to regenerate the Omicron triggers... they're missing around this time probably due to having too many triggers caused by the lockloss. I'm not sure why there's a discrepancy in the locked times with Robert's report.
Any chance this could be scattered light? at 1 m/s^2 and 1 kHz, it is a displacement of 25 nm, so you don't need fringe wrapping.
I think that you would expect any mechanism that does not require release of a particle to occur pretty much with every tap. These glitches dont happen with every tap.
Daniel and I looked at three of the locklosses from Travis's shift last night, from 14:40, 14:02 and 11:33 UTC. The earlier two both seem to be related to an alignment drift over 2-3 minutes before the lockloss, which shows up clearly in SR3 PIT. (there is currently not feedback to SR3 PIT) According to the witness sensors, this drift is only seen on M3. No optics saturated until after the lockloss. The DC4 centering loop, as well as both of the SRC alignment loops respond to the drift.
Its unclear what causes the drift to accelerate in the minutes before the lockloss. There is also a drfit of SR3 when we power up, as we noted yesterday, but this happens on a slower timescale than the dirfts that preceed a lockloss (3rd screenshot). Also, there is a longer, slow drift that happens whenever we are locked.
With Patrick and Cheryl I have engaged a DC coupled optical lever for SR3 PIT, we will see if this helps. The last screen shot attached shows the MEDM screen used to turn this on or off.
If the operators need to disable this (due to an earthquake, a trip, or if the optic becomes misalinged for any other reason) you can get to this screen from SR3, M2 OLDAMP.
Turning off:
turn off FM1 (labeled DC), then the input
Turning it back on:
Once the optic has settled and the beam is back on the oplev QPD, turn on the damping loop (with FM1 still off). Average INMON (in a command line tdsavg 10 H1:SUS-SR3_M2_OLDAMP_P_INMON), type -1 times the average into the offset, make sure the offset is engaged, and finally turn on FM1 to make the loop DC coupled.
Since this is just a trial, Jeff is not including these changes in his current SDF cleanup campaign.
Looking at the initial power up, we can see that an increase of a factor of ~10 causes ~0.7 µrad of pitch misalignment. During the accelerated drift in the last 3-5 minutes before the lock loss another 0.4 µrad of pitch misalignment was acquired with only ~10% of power increase. One might wonder, if we see a geometrically induced wire heating run away.
I modeled how much the two front wires have to heat up to casue a bottom mass pitch of 1 microradian. A very small temperature increase is needed to predict this.
* Assuming a constant temperature profile along the wire length (I'm sure this is not the case, but it is easy to calculate), it is
0.003
[C]
* Assuming a linear temperature profile where with the max temperature is in the middle, and the ends of the wire have no temperature increase
0.006
[C]
So we can say an order of magnitude estimate is greater than 1 mC / urad and less than 10 mC / urad.
Calculations:
From gwinc, the thermal coefficient of expansion for C70 steel wire is
alpha = 12e-6 [1/C].
From the HLTS model at ../SusSVN/sus/trunk/Common/MatlabTools/TripleModel_Production/hltsopt_wire.m
wire length L = 0.255 [m]
front-back wire spacing s = 0.01
[m]
The change in wire length for pitch = 1 urad is then
dL = s * pitch = 0.01 * 1e-6 = 1e-8
[m]
* For uniform wire heating of dT, this change comes from
dL = alpha * L * dT
So, solving for dT
dT = dL / (alpha * L) = 1e-8 / ( 12e-6 * 0.255 ) = 0.0033
[C]
* For a linear temperature increase profile (max at middle, 0 at ends), I break the wire into many constant temperature segments of length Lsegment.
The temperature increase profile is a vector defined by
dT = dTmax * TempPrile
where TempProfile is a vector of the normalized shape of the temperature prodile. It is triangular, 0 at the ends and 1 at the peak in the middle. Each element of the vector corresponds to a constant temperature segment of the wire. dTmax is a scalar representing the maximum temeprature increase at the middle of the wire.
The change in wire length is then given by
dL = sum( alpha * Lsegment * TempProfile ) * dTmax
solving for dTmax
dTmax = dL / sum( alpha * Lsegment * TempProfile )
with 101 segments, this gives us
dTmax = 0.0063
[C]
about double the uniform heating case.
* I also considered that since the wire has significant stress due to the test mass weight, the Young's modulus's temperature dependence might cause a different effective thermal expansion coefficient alpha_effective
. This appears to be a negligible effect.
From gwinc, the temperate dependence of the young's modulus E is
dE/dT = -2.5e-4
[1/C]
and young's modulus E is
E = 212e9
[Pa]
from https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=12581, we know that the change in spring length due to the modulus of eleasticity dependence is
dL = -dE/dT
* dT * Tension / Stiffness
where Tension is the load in the wire and Stiffness is the vertical stiffness of the wire.
The Stiffness is given by
Stiffness = E * A / L = E * pi * r^2 / L
where A is the cross sectional area of the wire, and r is the radius.
So plugging this in above
dL = -dE/dT * dT * Tension * L / ( E * pi * r^2 )
We get the correction on alpha by dividing this by L and dT, which eliminates both from the equation. From the HLTS model, the bottom mass is 12.142 kg and the wire radius is 1.346e-4 m.
Tension = 12.142 * 9.81 / 4 = 29.8
[N]
The correction on alpha is then
-dE/dT * Tension / ( E * pi * r^2 ) = 2.5e-4 * 29.8 / (212e9 * pi * 1.346e-4^2) = 6.2e-7
[1/C]
This changes alpha from
12e-6 to 12.6e-6
[1/C]
Not enough to matter for the estimates above.
Localizing the heat source:
I made a calculation of the heat absorption by wires.
Based on Brett's temperature estimate, assuming the radiation as the only heat dissipation mechanism, the heat the front wires should be absorbing is about 1uW total per two wires when SR3 tilts by 1 urad regardless of the temperature distribution.
If you only look at the power, any ghost beam coming from PRC power (about 800W per 20W input assuming recycling gain of 40) can supply 1uW as each of these beams has O(10mW) or more.
I looked at BS AR reflection of X reflection, CP wedge AR both ways, and ITM AR both ways. I'm not sure about the first one, but the rest are mostly untouched by anything and falls on SR3 off centered.
The attachment depicts SR3 outline together with the position of CP wedge AR (green) and ITM AR (blue) reflections, assuming the perfect centering of the main beam and the SR3 baffle on SR3. Note that ITMX AR reflection of +X propagating beam falls roughly on the same position on SR3 as ITMY AR reflection of +Y propagating beam. Ditto for all ITM and CP AR reflections. The radius of these circles represent the beam radius. The power is simply 20W*G_rec(40)*(AR(X)+AR(Y))/4 (extra factor of 2 due to the fact that the AR beam goes through the BS) for ITM and CP, and 20W*40*AR/2 for BSAR of -X beam.
I haven't done any more calculations and I don't intend to, but just by looking at the numbers (total power in green and blue beams in the figure is about 240mW, 5 orders of magnitude larger than the heat absorbed by wires), and considering that the centering on SR3 cannot be perfect, and that SR3 baffle is somewhat larger than SR3 itself, and that CP alignment is somewhat arbitrary, it could be that these blobs seeps through the space between the baffle and the SR3 and provide 1uW.
The red thing is where BSAR reflection of -X beam would be if it is not clipped by the SR2 scraper baffle. If everything is as designed, SR2 scraper baffle will cut off 90% of the power (SR2 edge is 5mm outside of the center of the beam with 8mm radius), and remaining 10% comes back to the left edge of the red circle.
Any ghost beam originating from SRC power is (almost) exhonerated, because the wire (0.0106"=0.27mm diameter) is much smaller than any of the known beams such that it's difficult for these beams to dump 1uW on wires. For example the SRC power hitting SRM is about 600mW per 20W input, SRM AR reflection is already about 22uW.
Details of heat absorption:
When the temperature on a section of wire rises, the stretching of that section is proportional to the length of that section itself and the rise in temperature. Due to this, the total wire stretch is proportional to the temperature rise integrated over the wire length (which is equial to the mean temperature rise multiplied by the wire length) regardless of the temperature distribution as is shown in effect by Brett's calculation:
stretch prop int^L_0 t dL = mean(t) * L
where L is the length of the wire and t is the difference from the room temperature.
Likewise, the heat dissipation of a short wire section of the length dL at temperature T+t via radiation is
sigma*E*C*dL*[(T+t)^4-T^4] ~ 4*sigma*E*C*dL*T^3*t
where sigma is Stefan-Boltzmann constant, E the emmissivity, C the circumference of the wire, T the room temperature (about 300K). The heat dissipation for the entire length of wire is obtained by integrating this over the length, and the relevant integral is int^L_0 t dL, so again the heat dissipation via radiation is proportional to the temperature rise integrated over the wire length regardless of the temperature distribution:
P(radiation) ~ 4*sigma*E*T^3*(C*L)*mean(t).
I assume the emmissivity E of the steel wire surface to be O(0.1). These wires are drawn, couldn't find the emissivity but it's 0.07 for polished steel surface and 0.24 for rolled steel plate.
I used T=300K, t=3mK (Brett's calculation for both of the temperature distributions), C=pi*0.0106", L=0.255m*2 for two front wires, and obtained:
P(radiation) ~ 0.8uW ~ 1uW.
ITM AR:
ITM has a wedge of 0.08 deg, thick side down.
ITM AR reflection of the beam propagating toward ETM is deflected by 2*wedge in +Z direction. For the beam propagating toward BS, ITM AR reflects the beam, deflecting down, and this beam is reflected by ITM and comes back to BS. Deflection of this beam relative to the main bean is -(1+n)*wedge.
AR beam displacement at BS is +14mm for +Z-deflection and -17mm for -Z-deflection. Since the BS baffle hole "radius" seen from ITMs is 100+ mm, and since the beam radius is about 53mm, AR beams are not blocked much by BS baffle and reaches SR3.
ITM AR reflectivity is about 300ppm.
CP AR:
Similar calculation for CP except that they have horizontal wedge, thick part being -Y for CPX and -X for CPY.
CP wedge is about 0.07 degrees.
I only looked at the surface of CP that is opposite of the ITM, and assumed that the surface facing ITM is more or less parallel to ITM AR, within an accuracy of O(100urad).
I assumed that S1 is the surface close to the ITM, and took S2 AR numbers from galaxy web page (43.7ppm for X, 5ppm for Y).
BS AR propagation:
BS wedge is 0.076 degrees, with a reflectivity of 50ppm.
Deflection of BS AR reflection of -X beam relative to the main beam is NOT -2*wedge as BS is tilted by 45 degrees. With some calculation it turns out that it is about -0.27 degrees, with a displacement of +48mm (positive = +X).
This beam is not obstructed at all by the BS baffle, hits SR3 and makes it to SR2 baffle edge. What made it to the SR2 surface doesn't go to SRM and instead comes back to SR3 as SR2 is convex and the beam is heavily off-centered.
If there's no SR2 baffle and if SR2 is much larger, the center of the reflected beam is going to be 50cm in -X direction from the center of SRM, which happens to be on SR3.
I don't know what happens to the edge scattering and the reflection from SR2, but both of these are highly dependent on SR2 centering.