I measured the beam spot positions on MC1, MC2, and MC3, using the procedure in alog 31402.
I have made a new guardian code called ISC_PRMICA which we will use on this coming Thursday to do a high power PRMI test. The code is based on ISC_DRMI with some modifications to load different set of locking parameters. The code is not tested yet. It lives at
/opt/rtcds/userapps/release/isc/h1/guardian/ISC_PRMICA.py
Using MCMC fitting to the sensing function measurements made in ER10 and O2, we can establish an estimate on the variation of the optical response parameters. The table below gives the typical (simple mean), maximum, and minimum of the measured maximum a posteriori values from the MCMC fits.Parameter typical maximum minimum --------------------------------------------------- Gain (ct/m) 1.143e6 1.166e6 1.085 Cavity pole (Hz) 347.1 358 341 Time delay (usec) 0.5 2.5 -1.3 Detuned spring (Hz) 7.3 8.8 4.9 Detuned spring 1/Q 0.04 0.08 1e-3This covers measurement dates from Nov 07 2016 through Mar 06 2017. Attached are plots showing these trends for ER10 and O2. Note that I have added--where possible--the GDS calculated values for kappa_C and f_c (black crosses). Note that these values do not come with error bars because the uncertainty would need to be computed from the measurement uncertainty of what goes into the calculate of kappa_C and f_c. It would be useful to have calibration lines running during the measurements to see if there is any trend or drift during the measurements themselves.
Attached are trend plots for all ER10 and O2 measurements.
The plots are stored at:
${CALSVN}/aligocalibration/trunk/Runs/O2/H1/Results/SensingFunctionTFs
The script to produce plots is:
${CALSVN}/aligocalibration/trunk/Runs/O2/H1/Scripts/SensingFunctionTFs/runSensingAnalysis_H1_O2.m
The HWS machine got rebooted so I restarted the code. I edited the code not to take new reference centroids but the tmux session didn't seem to recognize the change in the script so it ended up taking a new reference centroids anyway (to fix this issue I probably should have just exit the session and come back in). HWSX data starting from Tue, 21 Mar 2017 17:35:48 UTC now have new reference centroid taken during cold IFO (down time). All the optics were aligned.
I reset both PSL power watchdogs at 17:24 UTC (10:24 PDT). This closes FAMIS task 3642.
WP 6489 The tconvert program was updated for Debian 8 workstations to a version that can correctly convert dates containing the month of October. This version can also correctly obtain Bulletin C for leap second updates, using https.
TITLE: 03/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
Wind: 9mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.14 μm/s
QUICK SUMMARY: Starting maintenance day. Been locked since my shift yesterday.
TITLE: 03/21 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
At 15:00 utc, took H1 PREVENTATIVE MAINTENANCE for Maintenance Day. H1 was locked over 19 hrs. Did NOT hit Load Coefficients for Sheila's filter change since we were locked entire shift.
LOG:
Relatively quiet & smooth sailing. L1 was knocked out by a 4.6 Guatemalan quake (we rode through it and it didn't show up on our seismic BLRMS signals). Have been locked over 15hrs with a range hovering around 69Mpc.
I'm taking a quick walk over to my office for about 10-15min.
TITLE: 03/21 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
Wind: 16mph Gusts, 13mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.15 μm/s (really quiet & below 50%)
QUICK SUMMARY:
Approaching 12hrs of being locked.
Jeff informed me of a To Do item for the next lockloss (Load Coeff for new filter files, as noted in Sheila's alog#34954); or it can be done during Maintenance Day.
Shift Summary: Ran A2L DTT check – Pitch is rung up a bit, Yaw is OK. Ran the A2L DTT check at the end of the shift. Pitch is approaching 0.8, Yaw is still at or near the reference. PI Mode-23 rang up a couple of times, but self-damped almost immediately. No other issues arose during the shift.
Been in Observing for first half of the shift. The microseism and wind were laying down a bit, but is the past half hour or so they have started to climb back up. Range is OK at 65.5 Mpc. PIs have been behaving, with only one very quick up and down for Mode-23. The A2L Pitch is up to around 0.65, Yaw is just slightly above the reference. At this time no issues or problems to report.
TITLE: 03/20 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 60Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Three lock losses my shift. The first I don't know the reason for. the second I couldn't get to PI in time, and the last the PSL went out (see alog34950). Seimic noise has been an issue for us today cause caused by trucks along Route 10 (see alog34944). Locked for 3hrs
LOG:
While the laser was down this morning, I took a quick measurement of the ETMX pit oplev damping loop. It has about 5 dB of damping in a narrow range around 0.46Hz, and has zero phase and -10dB of gain at 1.5 Hz with no light in the arm.
Because the noise from these loops is limiting DARM at 10 Hz (alog 34735), I made a slightly more aggressive cut off (LP8 is intended as a replacement for LP10) which can be tried next time we have a chance. This is the reason there are unloaded changes in the filter files for all 4 quads right now.
I used this measurement to update the quad model with gain of the electronics and software between the PUM pitch actuators and the optical lever. See CSWG log 11209.
The gain was found simply by comparing the measured loop gain to the modeled loop gain with the installed filter, and scaling the model until matched the measurement. The gain applied to the model to make them match is 1/1500.
More measurements like this for the other suspensions will be useful for telling us if this gain factor is the same for all suspensions, or at least the same across sites.
Thanks for including the measured data, that made the analysis a lot easier.
Very good, quiet 4 days. Overall duty cycle was 91.4%, with range reaching just over 70 Mpc at times
- 2 24+ hour lock stretches
- Some wind issues Thursday morning (UTC) and Saturday evening (UTC)
- Strange trend in low-frequency noise on Sunday: started low, peaked at 0800-1000 UTC, then came back down slowly; possibly periodic with 24-hour period, uncorrelated with microseism
Summary of the data quality shift for Monday March 13 to Wednesday March 15, 2017 (inclusive):
This morning I saw some noise in the 60-200Hz area on DARM that lastest for a few minutes and then went away. I came back about an hour later, and an hour after that as well. The SEI BLRMS are clearly coincident with this breathing noise, and with the slight drop in range. Robert is thinking this may be tilling or truck traffic on the Hanford site.
I attached a plot of some of the BLRMS. It is seem the most in the corner station, but the ends see it a bit as well.
Robert and I watched with the roof camera and saw that there are about 5 large trucks that will pass the site on Route 10 within a few minutes of each other. The trucks are the kind that haul dirt/gravel/rocks and have two trailers (excuse my lack of truck terminology there). As these trucks pass, noise is DARM is clearly seen, and in the 3-10 and 10-30Hz SEI BLRMS as well. This much ground motion caused by trucks is abnormal, and we are hoping that it was a only for today. Our range has definitely seen this ground motion and it is show as going from 48-68Mpc for the last 3 hours, and is also seem in the previous lock ending around 16UTC. I attached a 24hr trend of some of the SEI BRLMS and range attached.
While I was watching for trucks to go by, I also saw a FedEx delivery truck show up on site. As this truck made the turn from Route 10 onto our driveway, it raised DARM similarly like the above trucks. On the straight the noise dropped, then the turn toward the LSB it rose again, and finally it had to backup and the noise popped back up.
EX had a dip in pressure around March 9th from 97.7 to 97.5, but other than that all looks good.
I forgot to link to FAMIS4530
Closed
Looking over the past week, the daily EY gliches are at 20:44 PDT (03:44 UTC). On Saturdays a second glitch occurs at 21:04 PDT (04:04 UTC). Attached plots show 03:25 to 04:10 UTC for 3/19 and 3/12 (two successive saturday evenings in local time).
Here are data from End Y with most of the pressure channels and the controller output to the pump motor.
The attached plot gives support to this argument:
Something is happening with either the Pump motor or the VFD causing an increase in pressure out from the pump. This is evident by the increasing delay in pressure response as we proceed down the Pump Station Manifold. PRESS1 is the first after the Pump, the rest are after Laminar flow resistors and the filter. BSCSUP_PRESS is way down the line at the Chamber. The PRESS1 clearly leads the down stream pressures and it steps more sharply than the others. So this is a real pressure change increasingly softened by the accumulators and resistors etc as the wave moves down the line.
The VOUT signal is the PID loop responding to the differential pressure (diff between BSCSUP and BSCRET[not shown].) There is a big step down on this channel just before the pressure step up but that wouldn't cause an increase in pressure. So, I don't believe the motor is being directed to drive harder.
I'll look over the VFD manual to see if it has any scheduled items that might cause this? That just hardly makes sense...
Edit--Extra--If the output voltage of the PID controller could actually be manipulated without the VOUT data signal registering it, that too would be a possibility...Dave is looking closer at the computer.
I analyzed the HWS data for the lock-acquisition that occurs around 1173641000. The "point source" lens appears very quickly (within the first 60s) and then we see a larger thermal blooming over the next few hundred seconds. I've plotted the data below (both gradient field and wavefront OPD). There are a few obviously errant spots in the HWS gradient field data. Since I'm still getting used to Python, I've not managed to successfully strip these off yet. However, it is safe to ignore them.
Check out the video too. Next step is to match a COMSOL model of thermal lensing with a point absorber to the data to get a best estimate of the size of absorber and the power absorbed (preliminary estimates are of the order of 10mW).
FYI: this measurement compares the system before, during and after a lock-acquisition (ignore the title that says "lock-loss"). The previous measurement, 34853, looked at lens decay before, during and after a lock-loss.
For your amusement I've attached a GIF file of the same data. My start time is 79 seconds prior to Aidan's "current time".
The integrated gradient field data for H1ITMX is contained in the attached MAT file. It shows the accumulated optical path distortion (OPD) after 2.75 hours following the lock acquisition around 1173640800. This is the total accumulated OPD for a round trip through the CP+ITMX substrates, reflection off ITMX_HR and back through ITMX+CP substrates.
Note: this image is inverted. In this coordinate system, the top of the ITM is at the bottom of the image.
Here is the wavefront data with the superimposed gradient field. The little feature around [+30mm, +20mm] does not appear in the animation of the wavefront or gradient field over much of the preceeding 2.75 hours. My suspicion is that this is a data point with a larger variance that the other HWS data points, rather than a true represtation of wavefront distortion.
I fitted, by eye, a COMSOL model of an absorber (14mm diameter Gaussian, ~25mW absorbed) to the measured HWS data. I then removed this modeled optical path distortion to get the following residual (lower left plot). I then fitted a COMOSL model of 30mW uniform absorption to this model and subtracted it to get the residual in the lower right plot.
Here's the total fitted distortion from the sum of two COMSOL models (point absorber + uniform absorption):
