Had doubted what I had been told last week by an INFICON service tech. that our gauge could only tolerate 80C bake when the external electronics were removed. I was able to confirm this in INFICON's published Operating Manual BAYARD-ALPERT PIRANI GAUGE tina46e1-a (2010-03) which also specifies this 80C limit even when the external electronics are removed (why?)-> I don't see anything in the materials exposed to vacuum list that would explain this low temperature limitation so I sent them an email requesting that they confirm.
J. Kissel, E. Goetz The roaming PCALX calibration line was turned off for hardware injections over the weekend (LHO aLOG 31861). It looks like we have enough data at 5001.3 Hz (started at LHO aLOG 31738), so I'm restarting the line at the low frequency end (1001.3 Hz) and re-running through the lower half of the schedule in order to gather data at 30 [W] instead of the inconsistent 25 & 50 [W]. I include the old completed schedule for reference as well, just in case we don't get enough data before the run starts. 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 28 2016 17:20:44 UTC 1501.3 35k 02:00 39322.0 2001.3 35k 02:00 39322.0 2501.3 35k 05:00 39322.0 3001.3 35k 05:00 39322.0 3501.3 35k 05:00 39322.0 4001.3 40k 10:00 39322.0 4301.3 40k 10:00 39322.0 4501.3 40k 10:00 39322.0 4801.3 40k 10:00 39222.0 5001.3 40k 10:00 39222.0 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 for caveats) 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 Nov 20 2016 16:54:32 UTC days @ 30 W (see LHO aLOG 31610 for caveats) 4801.3 40k 10:00 39222.0 Nov 20 2016 16:54:32 UTC Nov 22 2016 23:56:06 UTC days @ 30 W 5001.3 40k 10:00 39222.0 Nov 22 2016 23:56:06 UTC Nov 28 2016 17:20:44 UTC days @ 30 W (line was OFF and ON for Hardware INJ)
The IFO has been locked in low noise for ~7 hours now. However, from 15:58-16:33 11/28/16 UTC (7:58-8:33am PT just this morning) the flow signal dropped down from 3 to 1.5 and then recovered back up to 3. The lasers kept on chugging through this. This caused an alarm to the operator who notified me - upon inspection, I see that chiller is still reading 4.0 flow at the chiller. So all seems ok right now again...
REMINDER: O2 officially starts this Wed.
SEI: BRSx needs to be looked at opportunistically
SUS: nothing
CDS: PEM work @ mids
CDS software: Matlab license update Tues., DAQ work Tues.
PSL: PZT mount work today
OpLev: EX OpLev glitching
VAC: PT180 work ongoing
FAC: nothing
PEM: injection ongoing
LVEA walkthrough scheduled for tomorrow after maintenance activities complete.
TITLE: 11/28 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 70.5897Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
Wind: 32mph Gusts, 23mph 5min avg
Primary useism: 0.10 μm/s
Secondary useism: 0.73 μm/s
QUICK SUMMARY: Locked for the past 6+ hours. Robert is still here, so we'll see how long that lasts.
State of H1: locked in NLN on POP WFS
State of H1: NLN, running al2
Outgoing Ops: TJ
Activities:
TITLE: 11/28 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: After the earthquake the useism and wind have picked up a bit, I just made it to Coil Drivers before losing it. Wind may be trending down so there is hope.
LOG:
I've scheduled 5 more burst injections. They're spaced 70 minutes apart. The first one begins at 8:10 UTC (12:10 PT). Here are the updates to the schedule file:
At LHO, the first two injections failed due to an unlocked IFO. The last three were successful. However, the last two injections (ADI-e_12_0.4.txt and ADI-e_16_0.9.txt) were the only ones coincident with L1.
The relevant sections of the INJ_TRANS log are attached.
After the EQ the microseism started to rise, and the wind has picked up. I couldn't get past the CARM reduction steps so I attempted an initial aligmnet.... this didnt go so well. It may be a combo of the environment, but it wouldnt lock PRX and after it eventualy did, I had to go through SRC align step by step to keep it stable. Now I am trying to lock DRMI but it seems hard to hold the Xarm in green. Without BRSX this may get very difficult.
Just lost lock from an earthquake that isn't on USGS yet. The BLRMS make it seem as if was a close one. Only HAM6 tripped so far, but I put the SEI_CONF into Earthquake_V2 to hopefully help from others tripping.
4.9 off the coast of Oregon. USGS link
Today I made RF injections. The RF was not showing up strongly enough in the radio channels: I think we may need to amplify the antenna signal before going into the mixer, as we did in iLIGO. I would like to get this going and reinject. In addition, I think we need to remeasure some vibration coupling since Sheila zeroed the PIT offset in POP A last night. I got in a measurment today but would like to do a couple more. There is also the replacement of the piezo mount. And, we havent got to site anthropogenic yet, though if we dont get to these injections, I think we can assume the same sensitivites as we found for O1. Finally there are some more HEPI injections, though they are low on the list.
Peaks associated with BSC2 are the second largest source of environmentally driven peaks in DARM (next to the jitter peaks from vibration at the laser input) that we have found so far. We noticed that peaks in DARM at about 70, 105, and 198 Hz were amplified by acoustic injections in the LVEA. We tracked this to the beam splitter chamber and found that these peaks, as well as other peaks in DARM at 619.5 and 620.5 Hz, were increased by HEPI but not ISI injections (see Figure 1). This suggests that the culprit is on stage 0 of the seismic isolation, which is excited by HEPI but much less excited by ISI injections. The ITM elliptical baffles, hanging from stage 0 (Figure 2) are the most likely sources, either through scattering or clipping. Scattering would be our first guess, but I think we should also consider clipping because the peaks are not quite as broadened by sidebands as is typical of high Q peaks coupling through highly nonlinear scattering. The elliptical baffles have been previously implicated by a similar HEPI/ISI test (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=26016).
To be sure that the peaks were associated with stage 0 and not the table top, we made sure that the shaking was greater at the stage 2 GS13s for the ISI shaking than for the HEPI shaking, on all 3 axes, at the peak frequencies. Even though the shaking of the table was greater for the ISI injections than for the HEPI injections, the peaks were only increased by the HEPI injections (Fig. 1).
If we have time, we would like to try minimizing the peaks by putting DC offsets into HEPI.
Anamaria, Robert
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.
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.
A follow up email from company tells us that there is a build-in calibration board at the sensor.