24 channels added. 95 channels removed. (list attached)
TITLE: 09/07 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC STATE of H1: Commissioning INCOMING OPERATOR: None SHIFT SUMMARY: End X HEPI, ISI & TMS were tripped upon arrival (see alogs 38549, 38554). Have been trying unsuccessfully to get back to NLN all day. Have not made it past ENGAGE_DRMI_ASC. Sheila and TVo continuing to diagnose. LOG: 15:02 UTC Peter to optics lab 15:10 UTC Richard to Biergarten to retrieve equipment 15:14 UTC Set ISI config to SC_OFF_NOBRSXY 15:23 UTC Richard back 15:26 UTC Set ISI config back to WINDY 15:29 UTC Reset IOP DACKILL WD for TMS, then SEI, then HEPI WD, then ISI WD 15:31 UTC Peter back 16:42 UTC Peter to optics lab 17:31 UTC Kyle to end Y VEA, then end X MR 17:47 UTC Corey to LVEA to drop off periscope in squeezer bay 17:49 UTC Running ditherAlign.py TMSX 17:51 UTC Corey back Dither align script did not find photodiodes. 18:01 UTC Kyle back 18:39 UTC Peter done 19:15 UTC h1ecaty1 EPICS IOC crashed. Restarted. 19:28 UTC Initial alignment done. 19:31 UTC Lock loss from ALS DIFF 19:33 UTC Christina to end X (not VEA) then mid X. 19:35 UTC Lock loss from ALS DIFF (ramping DARM1_GAIN to 400). 20:22 UTC Lock loss (same) 20:25 UTC Ed to mid Y 21:34 UTC Elizabeth to LVEA to retrieve equipment 21:40 UTC h1asc model restart (WP 7142) 21:42 UTC DAQ restart Elizabeth back 22:40 UTC SRM tripped
The original PERL script cds/common/scritps/beckhoff_gang_whiten no longer works on the new Debian8 machines. As per ECR E1700056, when we find broken PERL scripts we re-write them in PYTHON.
beckhoff_gang_whiten is now a python script. I think there was a bug in the PERL scipt which with an invalid argument could cause FE whitening digital switching without its corresponding Beckhoff analog switching, which I fixed in the new code. There was also some redundency in the code which I removed.
Sheila tested the new code on ASC, it appears to work.
FAMIS6539
No water was added to either chiller, both were full. Looks like it was filled two days ago so this makes sense. Filter was clear and water looked good
Work Permits:
https://services.ligo-la.caltech.edu/LHO/workpermits/view.php?permit_id=7141
https://services.ligo-la.caltech.edu/LHO/workpermits/view.php?permit_id=7142
Hang, Daniel, TiVo, Sheila, Patrick, Dave:
The isc/common/models/WFS.mdl file was edited to modify the WFS_DOUBLE_DEMOD part (only used by the h1asc model). h1asc was compiled, installed and restarted.
New h1ecatc1plc2 code was installed, which complements the front end h1asc change.
A new H1EDCU_ECATC1PLC2.ini file was installed into the DAQ, along with a new H1EDCU_GRD.ini which removes the temporary nodes (bounce, als-esd).
The DAQ was restarted to use new H1ASC.ini, H1EDCU_ECATC1PLC2.ini and H1EDCU_GRD.ini. Only slow channels were added/removed.
This is an update on my investigation into alignment of HAM2 SEI and the alignment of the IMs on HAM2, both when the chamber is vented and when under vacuum.
In May 2017, the IM optics were aligned and damped during the vent, and the ISI was in it's nominal state before the vent, and briefly when the chamber was vented, while the IMs were still aligned and damped.
Using the numbers from that vent, I calculated the largest alignment change in IM optics, 160urad for pitch, 108urad for yaw, and the total change in the HAM2 optical table alignment, 15urad.
For vented alignment, with doors off, and a level and centered beam through the IO optics, I used the SEI and IM alignment data from the 2014 vent when Kiwamu aligned and recorded the IM alignments in the alog.
For current alignment under vacuum I used the alignment in May 2017, when I did an IMC beam spot measurement.
Using the vented 2014 data and under-vacuum data from May 2017, the change in the SEI (HEPI + ISI) is 142urad.
I set the maximum expected change due to SEI equal to 300urad (~SEI change * 2).
In May 2017 the IMC beam centering was measured, and found to be off-center on MC3 by -5.7mm in yaw, and from this I calculated that the beam on IM1 was -6.6mm off-center in yaw.
I calculate the position and angle changes of the beam on CW1 of the IO Faraday, and the position results from my Matlab code are shown in the table below:
IMC beam centering | IM1 and IM2 alignment changes in Yaw (2014 to 2017) | beam position from center on CW1 |
calculated, centered | M1 = -737urad, IM2 = -90.5urad | 1.1mm |
measured, off-center | no change to IM1 or IM2 alignment | 6.9mm |
measured, off-center | IM1 = -737urad, IM2 = -90.5urad | 8.0mm |
measured, off-center | IM1 = -737urad, IM2 = -90.5urad, and +/-300urad on one or both | smallest value was 7.4mm |
The measured off-center beam on MC3 is consistent with the loss of the IMC Trans beam. My diagram showing this, is in my alog 36408.
Some changes to IM1 and IM2 alignment have been made since May, however those changes are small compared to what would be required to recover a centered beam on the IO Faraday. From the May alignment values for IM1 and IM2, a single change of IM1 yaw of 4050urad, or a single change on IM2 yaw of 22500urad would bring the CW1 beam back to within 1mm of center. Both changes are significantly larger than the changes measured in SEI or IMs.
Same as FRS 8220.
Restarted IOC.
Not much eye-catching here except ETMx. ETMx has taken a step over +/-10um in the last few hours for PITCH & YAW today (9/6).
Here is the timeline of what happened this morning at EX (see attached minute trend plot, showing time span 03:00 - 10:00 PDT).
At 03:28 h1iopsusex lost track of its DAC channels, and went into the safe state of not driving any DAC outputs. At this point TMSX and ETMX are not being damped, but the ISI is still operational (red line jumps to 132 in plot). Over the next hour, TMSX slowly rang up and eventually hit the software watchdog limit of 110mV RMS. Ten minutes later the SWWD tripped h1iopseiex DACs (puple line drop to zero) stopping the ISI isolation, which then quietened the suspensions down over the next three hours. When the control room untripped the SWWD at 08:28 the sequence repeated itself. The problem was resolved by restarting the h1iopsusex model at 09:43.
The initial problem of the IOP model losing track of its DAC channels has been seen before, and is more likely on the end station SUS machines due to their increased ADC glitch rate (faster computers).
Bottom line is the software watchdog acted correctly, and in this case resolved the ring-up of TMSX. For O3, the hardware watchdog will be active at EX as a fall-back watchdog in case the SWWD becomes non-functional.
Sheila restarted the models on h1iopsusex to fix the problem.
The clean room curtains were let to free hang so as to improve particle counts during the installation then removal of the Surface Discharge Ionizer assembly at the end stations as part of the TMDS exercises. As found, they had been clamped aside and prevented from touching the ISCTs. Is this an issue for commissioning this week?
End X HEPI, ISI & TMS were tripped upon arrival. SWWD was tripped (see attached screenshot). Reset TMSX DACKILLIOP, then SEIETMX DACKILLIOP, then HEPI WD, then ISI WD. Guardian brought everything back. CDS overview is reporting red blocks for DAC and DK on H1IOPSUSEX (see attached screenshot). Have not figured out how to clear these.
Daniel, Keita, Sheila, Thomas, Hang
1,
Because the 118.3MHz and 9.1MHz&45.5MHz SBs' phase are not sync'ed perfectly, we need to use a double demodulation scheme to sense the AS72 signal, see T1700324. Previously, we offset the first demodulation frequency by 205Hz (demod at 72.8M + 205 Hz for the first demod). However, with this config we could not engage the PLL loop to stabalize the secondary demod freq.
Daniel pointed out the if we domod at 72.8M + 205, we would down convert both <45.5M, 118.3M> and <2x45.5M, 2x9.1M> to 205Hz, and the two signals could beat against each other since 118.3M SB's phase drifted relative to 9.1M. Therefore the PLL loop could not be locked.
To solve it, we instead demod'ed at exactly 72.8M for the first demod loop, but offset the 118.3M by 205Hz. After this modification we could have a stable PLL loop to derive the 72.8M Hz signal.
2,
We preformed some preliminary AS72 vs AS36 comparison. Under DRMI config (10 W input),the SRM pitch respose in cnt/rtHz were (also the first plot)
A_I | A_Q | B_I | B_Q | |
AS36 | 253 | 207 | 944 | 360 |
AS72 | 2.5 | 0.19 | 1.4 | 1.2 |
In order to see the signal, we had to have a very narrow bw of 0.01Hz. For reference, the noise level for AS72 is about ~0.1 cnt/rtHz.
Then in the NLN w/ full IFO, we did the measurement again (second plot)
A_I | A_Q | B_I | B_Q | |
AS36 | 318 | 77 | 786 | 223 |
AS72 | 1.6 | 0.39 | 1.1 | 0.7 |
The noise level for AS72 is still about 0.1 cnt/rtHz.
In addition we report the sum signal under the full IFO
A_I | A_Q | B_I | B_Q | |
AS36 | 25 000 | -4 300 | 33 000 | -14 000 |
AS72 | 169 | -3.3 | 211 | -1.8 |
We also tried to see the BS repose but could not see anything even if the line we drove dominated the BS rms motion...
Note that the 72 MHz signals is tiny because the modulation index for the 118 MHz is puny. See alog 37042. Since we are adding the new modulation to the EOM for the IMC, it is completely off-resonance. Obviously, we would need a dedicated EOM, if this installation should become permanent.
Kyle, Gerardo Today we leak tested the new 2.75 CFF, valved-in the RGA and NEG pump, dumped GV18's unpumped gate annulus volume into the adjacent (pumped) annulus volume and opened GV18. This completes WP #7139 and #7139. Attached is the pumpdown. Note: the controller for the Y2-8 ion pump is showing 5600V, 1.0 x 10-11 Torr and 0.0 microamps pump current - hmmm. I STOPPED then STARTED the HV but get same reading. Neither the "Torr" nor the "current" are as expected. This might be related to the controller setup parameters. Otherwise, the pump isn't actually pumping! I'll consult Gerardo tomorrow.
Another ion pump cable issue?
What does X2-8 read?
Yes - the ion pump current could be at the limit of the controller's measurement circuit. Pressures on the two arms look to be the same now. I thought there was a factor of 10 difference yesterday but maybe I had the wrong glasses on. Kyle or Gerardo?
I checked the display of the controller for X2-8 this morning and found it displays the same as the Y2-8 controller. That's great and all and, obviously they are pumping, but I thought that we had observed leakage current in 300' HV cable that amounted to micro-amps. Also, as a general rule of thumb, you figure 1 micro-amp of pump current for a 100 l/s ion pump @ 1 x 10-9 torr. As such, we should be seeing 5 - 10 micro-amps of pump current in addition to any leakage current.
I suggest turning off one or both ion pumps and looking for a response on the vacuum gauge over a period of a day or more. Hopefully this would confirm that they are pumping. As to leakage current - maybe things have dried out significantly over the summer and therefore leakage has fallen? Need to get some of these signals into epics to enable trending.
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.