TITLE: 08/31 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
Wind: 6mph Gusts, 4mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.16 μm/s
QUICK SUMMARY:
Kyle & Bubba are prepping for GV20 opening at EX (after work permit signed) this morning.
As of last night the game plan for the morning was also to have charge measurements run for ETMx and then start locking late morning/afternoon.
IFO Status:
Kyle, John Two additional discharge cycles, in addition to yesterday's single cycle, were completed by D. Sigg, J. Kissel and N. Mavalvala today. Following the final gas admission, and with the X-end pressure at ~16 Torr or so and the TMDS port isolated, John and I decoupled the Surface Disharge Ionizer from BSC9 and installed a 2.75" blank in its place. I then opened the 1.5" TMDS port gate valve and "burped" these few ccs of room air into the X-end vacuum volume. This valve was then left open. I roughed down using the QDP80 to 0.5 Torr < pressure < 1.0 Torr before spinning up the Turbo. This is the same approach as was used for the previous two pump downs. I am leaving the X-end on the Turbo overnight and plan to execute WP #7134 in the morning.
Daniel, Marc, Paul, Fil
Making good use of IFO down time today, we installed squeezer modifications to both Corner 4 and Corner 6 chassis. In theory, this completes the squeezer modifications to slow controls in the CER.
TwinCAT was down overnight due to a problem with the EK1100 on corner 6 right rail. We swapped the terminal and it is now working.
TITLE: 08/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY:
Gate Valve for EX has been closed all day today for TMDS work. This allowed for active work on the floor throughout the site. The plan is to open EX gate valve in the morning, measure charge, and then try to locking H1 in the afternoon. In parallel staging for TMDS at EY may happen tomorrow.
LOG:
J. Kissel, N. Mavalvala, K. Ryan, D. Sigg We've successfully completed the third and final cycle of the Test Mass Discharge System on H1 SUS ETMY (BSC9/BSC5). All methodology and numbers ran very similar to the second session (LHO aLOG 38453), and the latter half of the first session (LHO aLOG 38430). Because I was operating the knobs, my electrometer square wave voltage when measuring the ion "current" was 22.4 V (the maximum), instead of the previous runs in which Nergis measured with 12 V. After noticing the difference, we checked the electrometer's measured ion "current" at both 22.4 and 12 V, and measured similar values, so I stuck with 22.4 (cause it was easier just to crank the dial to max vs. find where 12 V was on the scope). See the attached notes for any further detail. Also of note, we noticed about a factor of 2 (maybe 1.5) increase in electrometer-measured ion "current" (voltage) from +/-4.5 to +/-9 [Vp] when the TMDS system's scroll pump is ON vs. OFF (while the whole system is still valved off to the chamber). Maybe the scroll pump is sucking up ions from the electrometer? Still no explanation as to why we're getting a factor of 1.5 less "current" than LLO -- again, Ryan's report during their Jul 2016 TMDS run (LLO aLOG 35636, they were able to get upwards of +/- 12 to 13 [V]. Nergis suggests it's a function of calibration on the electrometer.
The input impedance into the D1500061 electrometer board is 1e9 ohms. While this is relatively low in terms of the issues with contamination associated with electrometers having 10 to 100 times this input impedance, it is still feasible that somewhere in the chain of components from the pickup electrode to the input pin of the electrometer IC, that there is some parallel resistance associated with either moisture, or contamination. This would cause an apparent decrease in the measured current. A simple calibration might be possible by ordering a glass encapsulated 1e9 ohm resistor, cleaning it well, and using it as part of a voltage divider. The voltage divider formed by this glass resistor and the input impedance to the electrometer might be used to check the calibration via the normal electrometer output.
753 channels added. 8 channels removed. List attached.
I went back to EY again this morning and was successfully able to recenter BRSY this time. Because I was still a little sore from yesterday, I rethought my positioning at the viewport for the adjustment. I used the yellow stool from the ISC table and some foam to make myself a comfortable bench to lie down on and used the side of the stool to support my elbows. I also moved the workstation to the floor so I could see it more easily. Much better than curling up as small as I could, cross-legged on the floor for hours at a time.
Two things I still wish I had for this : a tablet or laptop that I could see the diagnostic plots on in the box so I didn't have to turn away from the viewport and a couple of padded c-clamps that I could use as wrist rests. I had one on the right side (this is clamping down the table for a co-located sts2) and my left shoulder is sore, I think from a combination of holding my left arm up and looking left continuously to see the diagnostic plots. Not a big deal for a couple minutes, but if you're camped out for a couple hours...
J. Kissel, N. Mavalvala, K. Ryan, D. Sigg We've successfully completed the second cycle of the Test Mass Discharge System on H1 SUS ETMY (BSC9/BSC5). Operation went much more smoothly today that yesterday. We were open to the chamber sending ions in by 08:00a PDT, and valved out by 08:30a PDT. We decided only to go up to a BSC chamber pressure of 15 [Torr], partially due to person-power constraints, but mostly because the bulk to the ion neutralization happens when the TMDS is first valved in; as more clean air is in the chamber, the ionic mean free path to the test mass decreases. This should also help us a little on pump-down time. All other settings were identical to what worked well yesterday (see LHO aLOG 38430): - clean air flow rate of ~70 [L/min] (or "slm") - ion "current" (voltage) occasionally measured by the electrometer with high-amplitude square wave (12Vp amplitude) of +/- 8 [V] - pressures inside the TMDS of ~100 [Torr] as measured by the baratron Attached are the raw notes (but they're not very exciting -- just 4 measurements of the ion "current" during the 1/2 hour discharge cycle). Based on the current pump-down rate, we expect to perform our third and final cycle around 01:00p PDT today.
Received "TCSX [& Y] CO2 laser output off" Verbal Alarms at 1702utc. (this was followed by a timing system error Verbal Alarm for SYS-TIMING_C_GPS_A_ERROR_FLAG).
Attached is a 1-hr trend of the TCS CO2 lasers which show a glitch, but are still close to the powers they had been running at.
yesterday at 10:00 PDT I modified h1susey's BIOS setting for 'Power Technology' from 'Max Performance' to 'Disabled'. The CPU usage of several models subsequently ran about 1uS longer showing the setting was indeed changed. The hope was that this would stop the occasional IOP model glitching, where we see either a transient ADC error (STATE_WORD=4) or a combined transient ADC and Timing error (STATE_WORD=6).
Trending SUS-EY IOP STATE_WORD (listed below) shows glitches after this change was made. I am masking out the upper bits of the STATE_WORD, only showing the first 3 bits to remove reporting on Overflows. EX glitches are also shown for comparison as an unmodified machine.
h1iopsusey STATE_WORD:
Aug 28 2017 17:17:42 PDT 6
Aug 29 2017 05:57:42 PDT 6
Aug 29 2017 08:12:42 PDT 6
Aug 29 2017 08:13:42 PDT 6
**** BIOS Modified 10:00 PDT
Aug 29 2017 13:50:42 PDT 6
Aug 29 2017 13:51:42 PDT 6
Aug 29 2017 14:23:42 PDT 4
Aug 29 2017 14:24:42 PDT 4
Aug 30 2017 03:23:42 PDT 6
Aug 30 2017 03:24:42 PDT 6
Aug 30 2017 05:36:42 PDT 6
Aug 30 2017 06:25:42 PDT 6
Aug 30 2017 06:26:42 PDT 6
Aug 30 2017 07:24:42 PDT 6
h1iopsusex STATE_WORD:
Aug 28 2017 21:28:42 PDT 6
Aug 29 2017 17:19:42 PDT 6
Aug 29 2017 17:20:42 PDT 6
Aug 29 2017 18:43:42 PDT 6
Aug 29 2017 18:44:42 PDT 6
Aug 30 2017 00:00:42 PDT 4
Aug 30 2017 00:01:42 PDT 4
Aug 30 2017 00:44:42 PDT 4
Aug 30 2017 00:45:42 PDT 4
Aug 30 2017 05:20:42 PDT 6
Aug 30 2017 06:23:42 PDT 4
Aug 30 2017 06:24:42 PDT 4
Aug 30 2017 07:12:42 PDT 6
Aug 30 2017 07:13:42 PDT 6
Aug 30 2017 09:49:42 PDT 6
Aug 30 2017 09:50:42 PDT 6
HAM CPS's: Do not see any high frequency effects worth noting. HAM CPS spectra attached.
TJ, TVo
We opened the CO2 laser tables to look at the direction of the picomotor actuation in order to confirm the ITM HWS orientation based off of aLOG-35336.
Picomotor Counts Request | Actuation Screw Direction |
+YAW | Clockwise |
-YAW | Counterclockwise |
+Pitch | Counterclockwise |
-Pitch | Clockwise |
Comparing our results to Aidan's, we match in pitch but disagree in yaw.
The above table is true for both ITMX and ITMY (as expected). If correct, this means that the aLOG-35336 analysis of the point absorber would have a flip in the horizontal direction and would predict the point absorber is on the lower right of ITMX as viewed from the BS. We will double check this with Aidan.
Edit: To clarify what I mean by "Picomotor Counts Request", I only used the readback from the channels denoted in attached screenshot by a blue ellipse:
H1:SYS-MOTION_C_PICO_F_CURRENT_X_POSITION & H1:SYS-MOTION_C_PICO_F_CURRENT_Y_POSITION
where X-axis is referring to YAW & Y-axis is referring to PITCH.
Is it possible to have this changed in software? I would think it'd be more consistent if clockwise was adopted to be the + direction for both yaw and pitch, rather than having to remember that it's positive for one and negative for the other.
Here are a few pictures and a link to a video of the knobs moving with our audio.
Video: LIGO-G1701750
1st attachment: Wide view of steering mirror
2nd: view if threads. These appear to be standard and not reversed.
We started having timing errors about 10 hours after the conclusion of O2, and today we started having end station timing errors at the same time at around 16:30 UTC or 9:30 local time. It seems like the end station witness GPS units are not locked.
The GPS timing error is due to a change of the default mode. LLO uses Position Hold, whereas the LHO units are configured for 3DFix. We need to reconfigure our GPS units to use Position Hold. Bottom line: GPS units work fine.
Sheila plans to come in and lock the IFO this afternoon, so that I can try to finish these detchar safety injections. I've schedule 7 injections, the first one will begin at 16:06:22 PDT, and the last at 16:51:22 PDT. Here is the update to the schedule:
1187824000 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187824450 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187824900 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187825350 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187825800 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187826250 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
1187826700 H1 INJECT_DETCHAR_ACTIVE 0 1.0 detchar/detchar_27July2017_PCAL_{ifo}.txt
The IFO should be left out of observation mode. Also, I'm not sure if the PCALX 1500Hz line gets turned back on, but this also needs to be turned off. Simply typing the following on the command line will do the trick:
caput H1:CAL-PCALX_PCALOSC1_OSC_SINGAIN 0
caput H1:CAL-PCALX_PCALOSC1_OSC_COSGAIN 0
The interferometer is locked in Nominal low noise and the PCAL X 1500 kHz line is off as of 22:55 UTC. I hope that the BS ISI will not trip during the injections. (alog 38382)
The interferometer unlocked just before 1187825964, so I think that 4 or 5 of these injections would have completed before it unlocked. I don't know why it unlocked.
According to the guardian log (see attached), the first 5 of these injections made it in. The fifth one ended at 1187825913 (about 50secs before the lockloss). This should be enough injections for now. Thank you Sheila for coming in on a Saturday afternoon and locking the IFO for us!
Short version: I made omega scans for the 5 sets of injections that were done above andyou can find them here: https://ldas-jobs.ligo-wa.caltech.edu/~jrsmith/omegaScans/O2_detchar_injections/ (note that after the first set the rest of sub-directories of the start time for each set).
Long version: The Injection files are here: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/detchar/. These are timeseries sampled at 16384 Hz and they start at the injection times listed in the original entry above. Times of the injections start 0.5s after times given in alog, and are separated by 3s each. Some simple Matlab to plot (attached) the injection file and print a list of times is:
% Plot hardware injections fnm = 'detchar_27July2017_PCAL_H1.txt'; data = load(fnm); t = 0:1/16384:(length(data)-1)*1/16384; figure; plot(t,data) xlabel('time [s]') ylabel('amplitude [h]') title(strrep(fnm,'_','\_')) orient landscape saveas(gcf,'injections.pdf') % Print times of injections t_start = 1187824000+0.5; times = t_start:3.0:t_start+106; fprintf('%.2f ',times)
To submit the omega scans I used wdq-batch like so: (gwpysoft-2.7) [jrsmith@ldas-pcdev1 O2_detchar_injections]$ wdq-batch -i H1 times-1.txt, then submitted the resulting dag to Condor.
OmegaScan results are here: https://ldas-jobs.ligo-wa.caltech.edu/~jrsmith/omegaScans/O2_detchar_injections/
These will take some hours to run and we will then look at the results to see if there are any obvious unsafe channels. In addition we'll look statistically using hveto.
This is the equivalent comment to the comment for L1's detchar injections hveto safety analysis on page 35675
I ran hveto_safety on the injections mentioned above, looking for coincidences within 0.1sec time window.
The results of the analysis using >6 SNR omicron triggers can be found here: https://ldas-jobs.ligo-wa.caltech.edu/~tabbott/HvetoSafety/H1/O2/safetyinjections/D20170826/results/H1-HVETO_omicron_omicron-1187823990-125/safety_6.html
The configuration for the analysis can be found here: https://ldas-jobs.ligo-wa.caltech.edu/~tabbott/HvetoSafety/H1/O2/safetyinjections/D20170826/results/H1-HVETO_omicron_omicron-1187823990-125/H1-HVETO_CONF-1187823990-125.txt
I missed that there we 4 extra sets of injections, so I've redone the hveto safety analysis on the complete set of 180 injections.