Although Jeff and I reduced the appearance of triple bounce and roll modes in DARM by adding notches to the top mass damping for the HSTS (30970), there are still a few modes that show up.
The largest in our last lock was at 28.2 Hz, which belongs to PR3 according to the resonances wiki and Jeff's measurement in 30646. We had no notches for the HSTSs so I have added notches 1 Hz wide centered around 28.2Hz and 44.2 Hz for PR3 and SR3.
The other thing which is large in our spectrum from last night is the remaining 40.9375 Hz mode from PR2. I am not sure why the PR2 mode shows up in DARM larger than the others. I looked at spectra of the osems to see if there is more noise on the PR2 osems. The attached screenshot shows that the top mass osems for PR2 aren't any more noisy than PRM, but there is extra noise in the lower stage osems for PR2, and a large comb. This might be noise in the readback only.
I made the notches in the damping loops 20dB deeper for PR2, we will see if this helps in the next lock.
Last updated Nov 11, 2016
https://lhocds.ligo-wa.caltech.edu/wiki/Violin_Mode_Table_v2
TITLE: 11/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: 16hr lock ended a few hours before the end of my shift. Things seemed to be misaligned after and it took me a bit, and with much help, to get it through an initial alignment. Handling off to Corey who may need to do another IA.
LOG:
TITLE: 11/16 EVE Shift: 0:00-08:00 UTC (16:00-0:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
Wind: under 5mph
Primary useism: Not changing much over last 24hrs
Secondary useism: --
QUICK SUMMARY:
TJ is still here and he & Jenne are addressing issue with Initial Alignment (current issue is with SRC Align). This is all after a 16hr lock.
Next up: IM alignment tweak from Cheryl (& then tweak Initial Alignment to address that tweak....so skip Green Arms/ALS & start with INPUT_ALIGN).
Then we'll go back to locking.
Significant exhaust thermal couple response in 19 seconds after changing the as found control valve setting of 16% open to 50% open. Chandra's adjustment to 16% following yesterday's LN2 delivery looks to be an ideal value for the current LN2 column height in the storage tank.
After I left them off for camera glitch investigation (alog31456). Both IX and IY. ETM hws code also restored after hwsmsr restarted. I don't remember having to restart ETMY by hand. Maybe I did but I just forgot that I did.... Or it could be a glitch in the Matrix. I'll keep this in mind for next time.
After a week's worth of struggle with the h1oaf computer, and alignment loop instabilities, we've been blessed with another 16 hour lock stretch. As such, we've got sufficient amount of data for the roaming calibration line to move it from 4001.3 Hz to 4301.3 Hz. Though the line has been at 4001.3 Hz for 5 days, I recommend only using data from the two long lock stretches in that time from Nov 12 2016 05:00:00 UTC to Nov 12 2016 21:00:00 UTC and Nov 16 2016 06:00:00 UTC to Nov 16 2016 22:00:00 UTC. However, note that the mean laser power is different from the one lock stretch to another -- 29.5 [W] for the Nov 12 stretch, and 31.1 [W] for the Nov 16th stretch. 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 4301.3 40k 10:00 39322.0 Nov 16 2016 22:17:29 UTC 4501.3 40k 10:00 4801.3 40k 10:00 5001.3 40k 10:00
Began replacing the Anemometers on the weather stations. Taking longer than anticipated as the stations are not in the same orientation as they were pre roofing. The corner station is done and EndX is complete. I had to rotate the mounting hardware so the Anemometer could point in the proper direction for 0deg. Everything seems to be functioning. This may also explain the complaints about the wind direction being broken in previous posts.
Here's a BruCo scan for last night lock:
https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_lho_1163325617/
Focusing on the band between 20 and 50 Hz, there isn't any large coherence. However:
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'.
model restarts logged for Tue 15/Nov/2016
2016_11_15 10:06 h1fw0
2016_11_15 11:45 h1susauxb123
2016_11_15 12:13 h1broadcast0
2016_11_15 12:13 h1dc0
2016_11_15 12:13 h1fw0
2016_11_15 12:13 h1fw1
2016_11_15 12:13 h1fw2
2016_11_15 12:13 h1nds0
2016_11_15 12:13 h1nds1
2016_11_15 12:13 h1tw1
Maintenance day. new frame-cpp version on fw0, new auxb123 model, daq restart.
model restarts logged for Mon 14/Nov/2016 - Thu 10/Nov/2016
Many h1oaf0 model restarts. Please see attached log text files for details.
model restarts logged for Wed 09/Nov/2016 No restarts reported
model restarts logged for Tue 08/Nov/2016
2016_11_08 08:24 h1iopoaf0
2016_11_08 08:24 h1oaf
2016_11_08 08:24 h1odcmaster
2016_11_08 08:24 h1pemcs
2016_11_08 08:24 h1tcscs
2016_11_08 08:25 h1calcs
2016_11_08 08:25 h1iopoaf0
2016_11_08 08:25 h1ngn
2016_11_08 08:25 h1oaf
2016_11_08 08:25 h1odcmaster
2016_11_08 08:25 h1pemcs
2016_11_08 08:25 h1susprocpi
2016_11_08 08:25 h1tcscs
2016_11_08 09:51 h1iopoaf0
2016_11_08 09:56 h1iopoaf0
2016_11_08 09:56 h1tcscs
2016_11_08 09:58 h1calcs
2016_11_08 09:58 h1oaf
2016_11_08 09:58 h1odcmaster
2016_11_08 09:58 h1pemcs
2016_11_08 09:59 h1ngn
2016_11_08 10:00 h1susprocpi
2016_11_08 10:06 h1pemex
2016_11_08 10:11 h1fw2
2016_11_08 12:32 h1iopoaf0
2016_11_08 12:34 h1calcs
2016_11_08 12:34 h1iopoaf0
2016_11_08 12:34 h1ngn
2016_11_08 12:34 h1oaf
2016_11_08 12:34 h1odcmaster
2016_11_08 12:34 h1pemcs
2016_11_08 12:34 h1susprocpi
2016_11_08 12:34 h1tcscs
2016_11_08 12:39 h1iopoaf0
2016_11_08 12:39 h1oaf
2016_11_08 12:39 h1pemcs
2016_11_08 12:40 h1calcs
2016_11_08 12:40 h1ngn
2016_11_08 12:40 h1odcmaster
2016_11_08 12:40 h1tcscs
2016_11_08 12:41 h1calcs
2016_11_08 12:41 h1iopoaf0
2016_11_08 12:41 h1ngn
2016_11_08 12:41 h1oaf
2016_11_08 12:41 h1odcmaster
2016_11_08 12:41 h1pemcs
2016_11_08 12:41 h1susprocpi
2016_11_08 12:41 h1tcscs
2016_11_08 13:00 h1dc0
2016_11_08 13:00 h1fw0
2016_11_08 13:00 h1nds1
2016_11_08 13:02 h1broadcast0
2016_11_08 13:02 h1fw1
2016_11_08 13:02 h1fw2
2016_11_08 13:02 h1nds0
2016_11_08 13:02 h1tw0
2016_11_08 13:02 h1tw1
2016_11_08 19:35 h1calcs
2016_11_08 19:35 h1iopoaf0
2016_11_08 19:35 h1oaf
2016_11_08 19:35 h1odcmaster
2016_11_08 19:35 h1pemcs
2016_11_08 19:35 h1tcscs
2016_11_08 19:36 h1ngn
2016_11_08 19:36 h1susprocpi
Maintenance tuesday. New frame-cpp code for fw2. ADC install in h1oaf0 starts the instabilities. DAQ restart.
model restarts logged for Mon 07/Nov/2016 - Fri 04/Nov/2016 No restarts reported
After switching to the down to check things and then going back to the OBSERVE, e-16 differences pop up that reflect the precision difference of the file and front end. This will really hobble the commissioners/operators and jeopordize the configuration and IFO lock. I know this is not a new problem.
The safe (for the lock) solution is to Accept the values in the FE to the file; but, this is temporary: the FE thinks the value in the file is the same even though it can not write that precision. Next time the FE reads the file, the problem returns. A more permanent fix is to revert the FE to the file but this requires the FE to change its value and potentially (maybe pretty small) break a lock. Some argue we just not monitor these channels but I say that is risky for the configuration as we stop seeing actual problem channel changes.
The real solution is to have the FE code (RCG?) actually write the file at the precision of the FE so all these problems go away.
This channel will be different each lock (PerComm-JWarner.)
Here is the snap of the current 3 differences with the mask removed.
For the OMC safe/down, there are 114 Not Monitored channels and yet only 15 of those currently have differences. FWIW.
We already know that the BRS's help us out, but here is a nice screenshot from yesterday of the ALS arm power in 40mph winds. Xarm (blue) has BRS sensor correction on and Yarm (green) had it turned on at around -50. The immediate difference really amazed me and I had to share.
Long lock, steady, looks like a good setting to call good. This is not the safe, just the OBSERVE.
Attached are all the differences, even the not monitored channels.
As far as the safe or down, loading the down, (soft & down in target linked to userapps down,) there are 20 diffs--should not these be Not Monitored? When I remove the mask, allowing all channels to be checked for differences, there are 60 total differences. So only 40 of the Not Monitored channels have differences. I would say that likely many of the 67 Not Monitored channels now showing No Differences could be monitored. Sure, many channels might end up back where they started after all the scripts. Still does it even matter?
TITLE: 11/16 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Locked at NLN for my entire shift. Darkhan doing some PCal line work for the first half of the shift. Observing for the second half.
LOG:
11:53 Turned off PCal lines. Start Kissel's PCAL2DARM measurement.
Saved as /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/PCAL/2016-11-16_H1_PCAL2DARMTF_4to1200Hz_fasttemplate.xml
12:08 Start Kissel's DARMOLGTF measurement.
Saved as /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/DARMOLGTFs/2016-11-16_H1_DARM_OLGTF_4to1200Hz_fasttemplate.xml
12:28 Turned PCal lines back on.
12:57 Observing.
Operator information:
I've added the Reduce RF9 modulation depth state back into the normal guardian path, but if you are having locklosses durring this state or right after you can try skipping it. If you skip it, you might want to keep the beam diverters open so you can see that the SRC1 loops are OK (ie, the ratio of AS90/POP90 is staying reasonably high over the lock). You might need to open the SRC1 loops if you skip reducing RF9 modulation depth.
I've also moved PR3 REFL WFS out of the normal path, so that it will be skipped for now if you just request nominal low noise.
In the morning POPX DC PIT was routed to PRC2. Didn't make sense (POPX DC is controled by its own centering loop), so manually zero-ed it.
Should have had no impact on anything as POPX DC is at least 4 orders of magnitude smaller than POPX RF over the entire frequency band.
Seems like this was puched in by hand last night.
Combination of ASC-REFL_B_RF9I and 45I was routed to unused DC7 as a fake PRC2 on REFLB.
I measured the phase between this DC7 and PRC2 (which is POPX_I) in nominal low noise, and the YAW was out of phase for microseismic peak but not above 3Hz or so (first attachment left) though PIT was pretty good.
By changing the mixing ratio of REFLB RF9I and RF45I for YAW, the coherence between DC7 and PRC2 improves and the phase becomes saner (but never as good as PIT). The second attachment shows when the relevant input matrix components were [0.14, -0.08], i.e.
DC7_YAW= 0.14*REFL_B_RF9I_YAW -0.08*REFL_B_RF45I_YAW.
(Nominally this was [0.14, -0.2].) The change was put in the guardian, I and Jenne were able to manually switch. Now PR3 is on REFL WFS instead of POPX.
This made ASAIR_B_RF90_I bouncier, but IFO seems to run. We'll run a2l and we'll also measure the sensing matrix