I meant to post this last night, will update soon.
Sheila, Keita, Jenne
A more complete alog will be coming, but this afternoon we once again measured the sensing matrix for refl WFS. THen we attempted to increase the recycling gain by changing SOFT pitch offsets (not very effective) and using the PR3 spot move (equivalent to change POP A offsets). We were able to increase the recycling gain from about 30.25 to around 31 by moving PR3 spot position. As we did this, the jitter peaks changed, with the peaks around 300Hz become better, the 260 Hz peak that we can tune away with IMC DOF1P offsets getting worse, and perhaps the broad lump coming back somewhat. (I think that we have moved back towards the alignment where the lump was a problem, but will check latter).
Moving the spot position on PR3 using yaw was more effective at increasing the power recycling gain (we approached 32), and I didn't see a change in the noise while doing this.
Since the noise was worse after these changes, I took them all out. If I get a chance latter, I would try moving yaw and not pitch to see if we can get some more recycling gain without making the nosie worse.
WP 6328 This morning we turned ON filaments of RGAs at EY and corner......from the control room! Gerardo will set the IP address for EX to complete WP. I was disappointed to find that we cannot connect to multiple devices at one time to monitor multiple scans in RGA software. Contacted vendor about this. Analog signal monitoring via CDS will help (ECR 1600307).
JeffK & HughR
This is to be ready for changes resulting from the A2L running on a regular basis. While at it I snapped a view of the TMs L2 Drive Align L2P filter banks.
These channels should probably be re-monitored. You've unmonitored the L2Ps, when it's actually the P2Ls (and Y2Ls) that will change when we run A2L. The P2L and Y2L gains are already not monitored for all the test masses. I have re-monitored the L2P gains.
Doh! Smackforehead.
Whoever is in the chair next when we have to relock (days from now I'm sure...), please:
Thanks a bunch - the past few days of everyone helping play this long timescale PI game has been super helpful.
When you say a2l, do you mean the trio of them or just the one original, main one?
Ya just the main one: a2l_min_LHO. Thanks Ed.
General comment for operators:
when you run a2l make sure you take the observatory mode to commisioning first, then you can put it back when the script finishes. This way we can avoid confusing people. Once we have SDF tied into the intention bit this would automatically drop us out of observing.
Many of the gain changes I just accepted into the LSC OBSERVE.snap are showing as differences in the safe.snap. With conference of JeffK, we are pretty positive these are values changed by Guardian. So, I am adding these values to the safe.snap Not Monitored list--see attached. They are ASAIR, POPAIR, POP, REFLAIR, & REFL: A & B, RF18/90/9/45, I & Q gains. 18 total channels. This makes 125 not monitored channels yet with these additions, there are only 62 differences for all setpoints.
I think these should be re-monitored in the safe.snap file. These values (the ones that are the setpoints in the safe.snap screenshot) are written in the ISC_LOCK DOWN state. If they are not correct, we may have trouble locking. They are then changed by guardian to the values in the Observe.snap screenshot when we reduce the modulation depths of the 9 and 45 MHz. So, the values that we want will be different in the safe and observe snap files, but we probably want to be monitoring them in both.
Actually, rethinking on it, Hugh's not-monitoring of these channels in the safe.snap file is totally consistent with everything we've been doing lately (not-monitoring channels that are written explicitly by guardian). Whether our current strategy makes any sense is a larger conversation, but these channels are probably fine not being monitored.
Raised the Heater setpoint from 8ma to 9ma. We had approximately a 1/2 deg F drop in temperature in the VEA last night. Also raised AHU-3 heaters from 3ma to 5ma to turn one stage on.
I noticed that the LVEA dipped a little yesterday morning so I increased 1A, 1B, 4, 5 all by 0.5 ma to 8.0 ma.
Beautifully high duty cycle over the past few says. Nice work team! Current Schedule Status: Frequency Planned Amplitude Planned Duration Actual Amplitude Start Time Stop Time Achieved Duration (Hz) (ct) (hh:mm) (ct) (UTC) (UTC) (hh:mm) --------------------------------------------------------------------------------------------------------------------------------------------------------- 1001.3 35k 02:00 39322.0 Nov 11 2016 21:37:50 UTC Nov 12 2016 03:28:21 UTC ~several hours @ 25 W 1501.3 35k 02:00 39322.0 Oct 24 2016 15:26:57 UTC Oct 31 2016 15:44:29 UTC ~week @ 25 W 2001.3 35k 02:00 39322.0 Oct 17 2016 21:22:03 UTC Oct 24 2016 15:26:57 UTC several days (at both 50W and 25 W) 2501.3 35k 05:00 39322.0 Oct 12 2016 03:20:41 UTC Oct 17 2016 21:22:03 UTC days @ 50 W 3001.3 35k 05:00 39322.0 Oct 06 2016 18:39:26 UTC Oct 12 2016 03:20:41 UTC days @ 50 W 3501.3 35k 05:00 39322.0 Jul 06 2016 18:56:13 UTC Oct 06 2016 18:39:26 UTC months @ 50 W 4001.3 40k 10:00 39322.0 Nov 12 2016 03:28:21 UTC Nov 16 2016 22:17:29 UTC days @ 30 W (see LHO aLOG 31546) 4301.3 40k 10:00 39322.0 Nov 16 2016 22:17:29 UTC Nov 18 2016 17:08:49 UTC days @ 30 W 4501.3 40k 10:00 39322.0 Nov 18 2016 17:08:49 UTC 4801.3 40k 10:00 5001.3 40k 10:00
The 1083.7 Hz calibration line was turned OFF for a brief period (~1-2 hours) during this current 4501.3 Hz stretch. See LHO aLOG 31610 for details.
1083.7 Hz calibration line restored just after the lock loss at 2016-11-18 23:30 UTC.
First attachment is the ASC changes accepted. All the ones accepted are gains that have been rounded off to 4 places rather than 10. I did miss one matrix value (circled) but I've corrected that in the file directly and reloaded that to the FE. The 23 remaining differences are filters, offsets and matrix changes requiring more scrutiny.
For the LSC, the same applies. There is one offset difference remaining--see attached.
The one channel remaining in the LSC SDF was H1:PSL-POWER_SCALE_OFFSET, which is changed by the LASER_PWR guardian as it changes the PSL power into the vacuum. This will be different every lock, so I have un-monitored it in the Observe.snap file. Also, TJ has changed the guardian to round it to 4 decimal places, which is more than plenty of precision.
Looking right now, everything left in the ASC SDF is stuff that is actively being worked on (SOFT offsets, input matrix for PRC2, etc), so we don't know yet what we'll run with for O2. These should all stay monitored.
All of the filters in the DC loops were notches that were turned on for a sensing matrix measurement, and should have been turned off. When I turned the notches off, the diffs went away, so we already had the correct settings accepted.
Thanks for the fine-tuning and details--just what we need for good control--Thanks Jenne--H
SEI - All good.
SUS - All good.
ISC - Sheila and Nutsinee were moving PR3 last night to increase optical gain. Pop beam diverters are still open due to REFL WFS trouble.
CDS - HW - Running, anemometers are all up except at EY. Heading to the vault today.
- SW - Stable. Working on installing Debian8 on various work stations. Seems sucessful so far. Impressed enough that they may want to replace everything with it, please be giving them feedback.
PSL - Still running. TCS as well.
Vac - Today Chandra would like ot tune the filaments on the RGAs, can be done from the CR. Looking for partial pressure changes in locklosses.
Fac - If you find something broken, please just call the appropriate person rather than emailing because they may not get to the email in a timely manner.
Cal - Got the last set of measurements last night, about ready to update the calibration.
Reviewed Fault reports
Robert and Annamaria will be coming to do PEM injections next week.
if you see cds macbooks 3 & 7, please bring them back to Carlos or Jim B.
TITLE: 11/18 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 66.2053Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Locked for 22 hours and counting.
LOG:
07:50 Started ITMX HWS script (left it off to test some other script on Wednesday and forgot to run it)
08:01 Increased violin mode damping gain for ETMY 508.585
08:08 Chaged CO2Y power upper limit so the ODC bit is green. Accepted the change in SDF.
12:43 LLO lost lock. Took IFO out of Observing so I can do some PRM test for Sheila. Here's what happened:
13:36 LLO back to Observe. Slowly revert PRM gain and took some DARM spectrum in the process.
13:51 Back to Observing
~15:20 Joe moved a ladder from Mid of sec1 Y beamtube to Y12.
15:10-15:15 Weird noise in AS90/POP90 (see attachment). I was looking at Sheila's Build_ups striptool and only POPAIR_B_RF90 seems to see this.
Aidan, Terra
A continuation of alog 30522
Previously we'd found that frequency drift over a lock stretch is mode dependent - differential drumhead mode drifts more than that same optic's drumhead mode - but surmised that the ratio of (change of frequency / frequency) between two modes would be constant. However, this assumed a spacially uniform change in temperature --- fm = g(T) --- when a more realistic assumption is some radial dependence of T, so:
fm = g(T(r)), where r is radial vector
Since the energy distribution of a given mode is also dependent on r, we can expect some modally unique self heating response. In other words, the more overlap between a given mechanical mode and the hot spots of the optic, the larger the frequency drift we'd expect that mode to have.
I've looked at ETMY 15009 Hz diff drumhead mode shift compared with ETMY 8158 Hz drumhead shift during twelve hours of a recent lock. 15009 Hz relative frequency change is larger than drumhead relative change and the ratio begins to level off towards a constant after about six hours. We expect (and model) the opposite - the drumhead mode would have more thermal overlap and thus would shift more. This assumes a mostly centered beam spot (or equivalently, assumes r = 0 at the center of the optic). Looking at Jenne's recent beam spot investigation, ETMY spot position was fairly centered during this time, off in yaw by a few mm. The 15009 Hz mode is differential in pitch. (I still suspect some dependence on torsional vs. longitudinal mode movement as suggested in alog 30522.)
We've started having operators run a2l more regularly and before and after powerup at times to get assurance of beam spot position.
Quick look at the frequency drift for ETMY 15009 Hz and Drumhead during the first 12 hours of the current lock. Ignore the giant vertical line of glitch terribleness. Also I tried fitting the Drumhead df/f with a sum of weighted exponentials (though note that tau == b is the same for each series element) as a very preliminary comparison with thermal lens response to power step.
TITLE: 11/18 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: OBSERVING
OUTGOING OPERATOR: Corey
QUICK SUMMARY: H1 has been locked 16 hours and counting. Sheila sent me an instruction and asked me to play with PRM. I'm waiting for LLO to be out of Observing before doing that. If that doesn't happen I will do it towards the end of shift.
After getting wack values for PI mode ring ups (many orders of magnitude off from expected) earlier in the week, I've refit ring ups and taken new ones and gotten much more reasonable values (I wasn't looking at long enough time stretches to get accurate ring up data before). Note that we haven't had any instability in Mode3 in many days so I haven't been able to remeasure it.
Mode # | Freq | Optic | tau | Q |
3 | 15606 Hz | ITMX | TBD | TBD |
26 | 15009 Hz | ETMY | 316 s | 15 M |
27 | 47495 Hz | ETMY | 92 s | 5 M |
28 | 47477 Hz | ETMY | 89 s | 5.2 M |
Mode 3 hasn't been unstable in many days and Modes 27 & 28 are only unstable during the initial ~ 1-2 hours of transient. Attached are two 30 hour stretches of the damping output of the three modes during recent long locks (Mode3 had no output so I left off) and the simulated HOOM spacing to get an idea of when the modes are ringing up enough to engage damping loops. Left is a few days ago and right is the current lock. Note that Mode26 looks continuously unstable during the 11/16 lock, but it could be that the damping gain is triggering below an actual unstable amplitude; compare to the current lock where we set the gain for Mode26 to zero just after 19:30 (so there would be no damping output) but it has remained stable and low since then with no need to damp.
Operators and myself are currently turning off gain and measuring ring ups during different times of lock stretches to get gains at different stages of the thermal transient.
Current damping status of this now > 25 hour 32 W lock: no damping required after the first 2 hours. Attached plots again show damping loop output over the past 26 hours and HOOM spacing for reference.
The attached plots show the frequency noise seen by the reference cavity (green), the IMC (red), the REFL port (blue) and the POP port (brown). The first plot also shows the estimated in-loop suppressed noise in a lighter color as well.
The second plot shows uncalibrated traces but with a 30 kHz bandwidth. The peaks at ~7250 Hz and at ~13.6 kHz are already present in the IMC spectra when the interferometer is unlocked, and, therefore, are not introduced by the REFL servo. The I' channels are the DAQ sensor channels closest to true in-phase signals.
A few notes to the calibrations:
I've added a Weeklies screen to the Sitemap to make it easier for the operators to do FAMIS tasks. It can be found under the OPS tab. Pretty simple, there are a number of buttons that launch different scripts for different FAMIS tasks, so operators don't have to navigate from the command line. Operators and detector engineers should feel free to add tasks to this screen, I added the ones I could think of. Hopefully we can rely on this screen to make sure that operators use 1 version of a script, and give cognizant engineers some control over which version is used.
I also encourage anyone with any artistic inclinations to make it look nicer. I got nothin'.
There are now THREE a2l scripts that we will be running once during EACH lockstretch. Patrick mentioned them in his time log. I'm tagging Opsinfo with the information again.
cd /opt/rtcds/userapps/release/isc/common/scripts/decoup ./a2l_min_LHO.py ./a2l_min_PR2.py ./a2l_min_PR3.py
that is all :)
A note on the (3) A2L measurements.
As of this week, we want to run the ...LHO.py file at the beginning of locks (i.e. right after we reach NLN). It takes on the order of 10min.
Sometimes you might not want to run it. If the DARM specrtra looks good around 20Hz, then you are good. It's a judgement call, but in general, this helps with sensitivity. Will put this in the Ops Sticky Note wiki & should get in the Ops Checksheet soon.
(Thanks to Jenne & Ed for sharing the alogs about this!)