TITLE: 11/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
Wind: 13mph Gusts, 10mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.35 μm/s
QUICK SUMMARY: Smooth sailing and PEM work.
TITLE: 11/27 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Locked at NLN, Commissioning mode for injections
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Locked for all of the shift except for a brief ~30 min. lockloss.
LOG:
18:03 Robert starting injections, out of Observe.
20:11 Running a2l.
20:25 Closed ASAIR and REFL beam diverters at Robert's request, Robert to LVEA.
20:38 Lockloss.
21:15 Locked at NLN. Only had to do some tweaking of PRMI to get locked. Changed phase of PI mode 28 from -20 to 180 and phase of mode 27 from 120 to 100. Staying in Commissioning mode for Robert.
21:30 Closed beam diverters again for Robert.
21:40 Robert to LVEA.
~1535 -1542 hrs. local -> Kyle in and out of LVEA, accidentally drug ladder across BSC8 dome a little, turned LVEA lights off @ 1542 hrs. local Reduced variac outputs by ~15%
We were locked for almost 9 hours until Robert started his injections for the day . . . or maybe that was just a coincidence.
TITLE: 11/27 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 71.4912Mpc
OUTGOING OPERATOR: Nutsinee
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.29 μm/s
QUICK SUMMARY: Locked in Observing for the past 5 hours.
TITLE: 11/27 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Travis
SHIFT SUMMARY: Struggle to lock in the beginning but eventually got to NLN. POP90 jump during Noise Tuning even with SRC1 P loop oepn (I thought it's supposed to prevent the jump?). BNS range was slowly drifting downward so I gave SRM a bit of touch but eventually reverted the alignment. The range became stable after an hour or so.
LOG:
12:41-12:56 moved SRM P (and a bit in yaw) in attempt to recover the drift in range. I was afraid that it would drift too far and break the lock. I didn't go out of Observing due to an on going scheduled injection.
13:09-13:12 slowly moved SRM P back after I realized I made the noise worse. Also didn't go out of Observing.
POP90 still jumped during Noise Tuning but I haven't seen a jump during NLN.
I moved SRM while the intent bit was set hoping it would stop the range from drifting. The range continued to drift downward during the first hour into the lock, I was afraid that it might be due to SRC1 P loop being open. I moved SRM pitch hoping that it would make things better (or slow down the drift). However, turned out I made the noise worse. I moved SRM back in pitch to where it started off at NLN and was able to improve the range a little. Because of an ongoing scheduled injection I didn't take H1 out of Observing (sorry DQ shifter, this is why I tagged you!). I also tried to move SRM yaw a little bit since it was also drifting (even with SRC1 Y loop close). The time of alignment change is 12:41-12:56 UTC and 13:09-13:12 UTC. I didn't move SRM yaw all the way back to where it started off since it seems to have become stabilized (and so was the range).
We have been struggling to lock all day today.
I think the root of the problem is that our alingment references are not giving us a good power recycling gain after inital alingment. The soft loops bring us back to a good alignment, but it seems like our references for the green arms are off and may need to be reset in DC readout. This means that we have had a lot of random locklosses durring the CARM offset reduction, especially durring the analog CARM transition. We have added some extra sleeps here, since we have had more sucsess doing this step by hand.
I zeroed the pit offset in POP A, because looking at the last 2 weeks of algnment, no pit offset gave us the best ranges, and the recycling gain was a bit better than the current -0.2 offset. This hasn't improved the recycling gain when we first lock much, but it does reduce the amount that the recycling gain drops when we engage CHARD, which has caused a few of our locklosses today.
We also had some bugs in the SRM_ASC high power state, which Kiwamu and I changed earlier today for the new SRM dither loop. For now I have commented out the line where it sets the gain, this morning we used a gain of -100 if anyone wants to try turning it on by hand later.
I think that the next step might be to lock at the alignment references (next time we reach DC readout) but don't want to start changing references now, so we will leave it for tonight.
I've scheduled 9 burst injections to be injected coherently into both IFOs. They will begin at 10:10 UTC (2:10 PT) and are spaced 20 minutes apart. The IFO will need to be in observation mode for these injections to go in. Here are the relevant lines in the schedule file.
1164276617 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_9_0.2.txt
1164277817 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_13_0.6.txt
1164279017 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-c_20_0.99.txt
1164280217 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_12_0.4.txt
1164281417 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_16_0.9.txt
1164282617 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_LongDuration/ADI-e_20_0.9.txt
1164283817 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_4.0e-22_8.9_70.txt
1164285017 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_2.0e-22_8.9_153.txt
1164286217 H1L1 INJECT_BURST_ACTIVE 1 1.0 config/Burst/Waveform/ER10_ShortDuration/SG_2.0e-22_8.9_285.txt
The waveforms are on the hardware injection svn. The schedule file gives the path to the text files from the Details directory.
If for some reason these injections need to be stopped, follow these instructions:
Here is a link to the Burst groups ER10/O2 hardware injection plans - https://dcc.ligo.org/LIGO-G1601528
In the schedule file - ADI = Acretion Disk Instability, SG = Sine Gaussian.
At LHO, the first injection that went in was the 6th scheduled injection (ADI-e_20_0.9.txt). Unfortunately this was the only injection that went in at LHO, and the only one that was coherently injected at both sites. The remaining three injections were stopped by the guardian because there was an external trigger alert, which I'm guessing was due to the injection itself.
I've attached the relevant section of the INJ_TRANS guardian log.
For some reason a +50 degree filter was turned on in the ETMY top mass damping on October 12th, it was not good and we got no real top mass damping. Nutsinee and I just turned it off, so the settings are now the same as for ETMX. This fixed the problem
J. Kissel, B. Weaver We've investigated what we could of this, but there is no aLOG evidence that these phase adjustment filters were intended to be used in the design (what's now left is the same semi-low noise design I made a few years back: see G1300537). They also don't make any sense upon first glance individually, but after staring at the design strings and names it has slowly become clear. We can also narrow down who would attempt such sophisticated trickery without aLOGging, maintaining SDF, committing filter changes to the svn repo, or otherwise cleaning up after they're done... There are four filters that I've now cleared/completely removed from the H1SUS ETMY M0_DAMP_V filter bank: FM6 BS1_4 ellip("BandStop",5,1,40,1,4) FM7 -90deg zpk([-9.8],[9.8],1,"n") FM8 +50deg zpk([5],[50],1,"n") FM9 bouncetest ellip("BandPass",4,1,55,9.5,11)gain(45,"dB") Guessing what the intent was by the frequencies in question it looks like someone was exploring damping the highest vertical mode (a.k.a. "*the* bounce mode") from the top mass, using top mass OSEMs as the error signal. I'm not surprised it didn't work! Potentially related aLOGs: Corey's midnight issue on Thanksgiving: LHO aLOG 31828 My cleanup of ODC state vector Oct 25, where I blindly accepted the new state as OK: LHO aLOG 30849 The last attachment shows a trend of the filter state. The bottom trace is merely a report of the current filter state, and the top trace shows the user-entered EPICs record that is compared against when establishing whether ODC thinks there's OK status. The bottom trace confirms Sheila's suggestion that the filter bank status was changed on Oct 12th 2016 at ~16:50 UTC (which is Oct 12 2016 09:50:00 PDT).
TITLE: 11/27 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY: There was one nice 2hr lock during my shift, but other than that we have been struggling to find what has been causing us to drop during various parts of acquisition. Not sure if this is some remnant of the Beckhoff problems from earlier, but we have only been locked once since then. We have gone through one initial alignment, numerous DRMIs, and some DC Readouts. Sheila is working hard and has some theories about the recycling gain, I'm sure there will be an update when there is more news. PEM is done for the night.
LOG:
Commissioners and the PEM crew are working when we have the IFO up, but we have had a few unknown issues causing locklosses in some of the states after DRMI making it take a bit longer to get there. Currently working to get back up to resume PEM work.
Sheila, Kiwamu
Since last wensday, we have had several sudden changes in SRC alingment that started in the middle of the week and have continued (31865 31849 31844 31823) We don't know what causes this, but it only shows up in the alignment of SRM and SR2, (as well as the OMs and OMC) and it seems to be a pitch problem.
One likely suspect is the AS36I sensing, allthough we don't have any reason to suspect it changed mid week. We decided to try running a dither loop on SRM pitch for a few days as a test. We changed the demodulated signal to SRCL control, which has a higher SNR than any of the build ups. We reduce the amplitude of the dither line from 600 counts on the clock gain to 100 counts, use a gain of -100 and no 60dB filter (FM1). We set the lock point of this loop by adjusting the P2L gain in SRM M3, which we set to -1.3 for now to get the best build ups.
We are hoping to see if problems continue in the next few days with this on, or if there are jumps in the AS36 I signals. We have added it to guardian but this is not tested yet.
Is it possible that the excess motion in ITMY pitch, that was fixed last week, improved AS36I sensing in the same way that the pitch dither on SRM ASC is this week?
Last week the excess motion in ITMY pitch was identified, alog 31675 , and the filter causing it was turned off, alog 31701.
In searching the alog, I happened to find my own alog from June 2015, alog 18930, where I noticed the ASC ITMY pitch signal was about 3 times larger than ITMX's, at 500pp and 150pp (counts?) respectively. This may have changed since that alog, but if that was still true before the ITMY fix last week, it gives a scale of how much bigger ITMY was vs ITMX, which might be helpful in comparing to what the SRM ASC needs now.
CDS: The python nds2 client that the script uses could not get data today and yesterday.
FAMIS#:4703
Since the script was not working, I had to do this the old fashioned way. I'm glad this was made into a script!
ITMX P, ETMY P are getting close to out of bounds, but other than that it all looks good.
Sheila, Kiwamu,
This is a follow up of the latest AS90 jump incident reported in 31844.
We think this anomalous behaviour started in this past Wednesday (31804). This time, we looked into some other signals and found elevated noise in SRCL, although we are still unable to localize the issue.
[Time line]
[Some observations]
The symptom is very similar to what was reported in 31804. The POP 90 increased from 13 cnts to 16 cnts. Since the AS diverter was closed, it is hard to say whether there is a jump in AS90 or not. The jump also seems to have caused misalignment in SRC1 as was the case in 31804. The first attachment is trend of some relevant signals. The leftmost vertical line in each column represents the time when the POP90 jumped. The second vertical line represents the time when TJ opened the SRC1 loop and did manual alignment. Similarly to 31804, the POP90 became noisier after the jump. The LO signals in AS36 WFSs didn't show any obvious glitch or abrupt change.
This time we looked at the spectra of the AS A 36 signals and the SRCL error signal. See the second attachment. In each panel, the blue curve is taken before the jump or at evaluation point #1 (see the above list). The green curve is taken right after the jump or at evaluation point #2. Finally the red curve is taken after TJ's fix or at evaluation point #3. I was hoping to see an obvious change in the spectra that might indicate some electronics issue, but the AS 36 signals didn't really show an obvious change as far as the spectra are concerned. However, on the other hand, we found a difference in the SRCL length error signal although this is not easy to interpret. Right after the jump the SRCL noise increased in 3 - 30 Hz by roughly a factor of two. This cannot be explained by the change in the optical gain beucase the increased POP90 should mean a lower optical gain for seinsing SRCL. Another explanation might be a worse A2L coupling contaminating SRCL due to the different spot positions on the SR mirrors.
I was curious to see how the BRSX was doing, so attached is a quick 5 day trend. It seems that it may be slowly ringing down after Jim vistied on Thursday.
Even better today. Might be time to turn the damper back on soon.
