Last week HAM6's vacuum gauges were upgraded from the original pirani-coldcathode pair to the new Beckhoff Infinicon BPG-402. The new gauge has two channels (MOD1 and MOD2) which both record the vacuum over the full range of atmospheric (760 Torr) down to 1.e-09 Torr
I have renamed the archived Cold-Cathode minute trend files to match the new MOD1 name. In other words, if you ask for minute trend data prior to 8/10 for channel H0:VAC-LX_Y0_PT110_MOD1_PRESS_TORR you will be given data for the CC channel H0:VAC-LX_Y0_PT110B_PRESS_TORR. Note the archvied Pirani data is not accessible from NDS. I will write code to obtain data directly from the raw minute trend files if this is needed.
I will make the same changes for the other gauges which have been upgraded (PT170 and PT180)
Peter, Dave:
we modified h1pslfss under WP6100 to fix two bugs:
temperature channel inputs to DINCO for OOL and Ambient were swapped in the model
DINCO DAC outputs drive chans 08-11 and not 12-15
model was restarted, no DAQ restart was required.
Kyle, Chandra Valved in IP and valved out TP. Pressure fell from 1.1e-6 Torr to 9e-7 Torr when IP was valved in and now is slowly rising with TP valved out (currently at 1.2e-6 Torr). After IP reaches thermal equilibrium we expect pressure to fall again. After that is observed we will shut down turbo + scroll (hopefully this afternoon). Note: verified the MPC controller was ON and programmed for 500 L/s pump prior to valving back in. Read -5700 V. Now reads -5000 V with load.
LLO site was generally unaffected by the major flooding in Livingston and Baton Rouge area.
However, access to the site was difficult and hazardous so the site was closed Friday thru Wednesday.
Many staff had their homes inundated with river flood water.
All staff and visitors were either directly or indirectly affected by this event and many are still helping with the clean up and the recovery efforts underway.
The site is now fully open and has returned to regular operation.
Thanks to all of the LIGO family who have reached out to help those in need.
Note: The monthly Science Saturday event scheduled for tomorrow (08/20/2016) has been canceled.
Manual temp control via multiple variacs -> 10% decrease every few hours
SEI - progress made to miigate tripping of HAM6 ISI when fast shutter is activated
SUS - no report
CDS - hopeful to close out gust meter work today; PEM AA chassis repaired; TCS AA chassis repaired. Both AA chassis suffered buffer chip damage most likely due to 'hot-swapping'.
CDS SW - continuing worl to address Frame Writer instability issues. Also, formulate a plan for '02
PSL - water leak is repaired. Optics have been wiped. Further inspection of collateral water issues will be performed. Power up of LASER hopeful for this afternoon. TCSY is back up and fully functional at full power. No hard evidence of BS OpLev glitching noted. If said glitchiness persists there will be a plan to swap out the laser.
VAC - will transition HAM6 to ION pump. RGA bakeout work between HAMs 4 and 5 will continue into tomorrow. Length of time most likely will depend on commissioners being able to return to their tasks.
FAC - Bubba will inish eyewash station inspections. DI skid will be re-plumbed'
Attached is a plot of the cooling water flow rate for the 4 laser heads after replacement of the
burst hose (over head 3) and replacement of the head 4 flow sensor. Also attached is a 30-day
trend plot of the same signals. The large jump in flow rates about 6 days into the plot coincides
with replacement of the water manifold located under the table.
At this stage it is too early to tell if replacing the head 4 flow sensor fixes the problem
with the all over the place signal seen in the 30-day trend plot.
Evan G., Jeff K. Summary: We measured the transfer functions of the OMC DCPD anti-aliasing (AA) module paths of ch13-16 for chassis S1102788. We measure this because the filter board was modified for these channels (LHO aLOG 28010). This is similar to the measurement Kiwamu made in LHO aLOG 21123. The OMC DCPD AA channels are 13 and 14 for DCPD A and B, respectively. The OMC PI AA channels are 15 and 16. We find that the notch behaviour of channel 13 matches what Kiwamu found in LHO aLOG 21123, but the notch of channel 14 is distorted (broken?). Channels 15 and 16 do not have the same notch behaviour (as to be expected for the PI paths, matching LHO aLOG 28085). These differences--compared to the calibration model reference AA filter--are below 1% in magnitude and less than 1 degree in phase below 7 kHz. While the calibration group is unaffected by the broken channel 14, noise from 65 kHz will be aliased down into the detection band. We should consider fixing this. Details: The setup for the measurements is shown in the first attachment, and the reference measurement (to remove the gain of the single ended to differential box) is shown in attachment 2. Each transfer function measurement is normalized by the reference measurement transfer function. Data is saved in /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/OMCAAChassis Analysis script is saved as /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/OMCAAChassis/process_aachassis_data_20160818.m Plots are shown in the third attachment. Of particular note is to compare the new measurements to the AA filter model. Channel 14 (OMC DCPD B) now has a different behaviour near the notch. The difference is below 1% in magnitude and 1 degree in phase below 7 kHz, and does not force a revision in the calibration model reference AA filter.
J. Kissel, D. Sigg, R. McCarthy We haven't really quantified what sort of super-Nyquist frequency junk lies around this notch that might cause aliased noise in the detection band. Thus we don't really know whether this abnormal notch is "good enough," -- but we also don't know so for any functional/normally behaving notches either (e.g. the CAL model reference or DCPD A / CH13's response). The best I've seen is Carl's study with an SR785, seen in LHO aLOG 28611, but the frequency axis of his plot leaves one with desire. In either case, we think it prudent to just fix the notch, so as to not leave this hanging chad lying around, in case the abnormal response is indicative of a component failure (gradual or otherwise). For bookkeeping purposed, I've opened FRS Ticket 6071. We think it sufficient to wait until next Tuesday to fix it; no emergency here.
I have updated the Beckhoff SDF system to the latest channel lists. I'll automate this process soon, here is the process I followed (using ecatc1plc1 as an example)
It is assumed that the /opt/rtcds/userapps/release/ecat area is up to date with its req files (which may be in DOS format)
First get the latest autoBurt.req into the ECAT target area:
cd /opt/rtcds/lho/h1/target/h1ecatc1/h1ecatc1plc1epics
cp autoBurt.req archive/autoBurt.req.18aug2016
cp /opt/rtcds/userapps/release/ecat/h1ecatc1/H1ECATC1_PLC1.req autoBurt.req
dos2unix autoBurt.req
Now get this autoBurt into the Beckhoff-SDF target area and use it to generate the new monitor.req file
cd /opt/rtcds/lho/h1/target/h1sysecatc1plc1sdf/h1sysecatc1plc1sdfepics
cp autoBurt.req archive/autoBurt.req.18aug2016
cp ../../h1ecatc1/h1ecatc1plc1epics/autoBurt.req .
cd burt
cp monitor.req archive/monitor.req.18aug2016
grep "^H" ../autoBurt.req | sort > monitor.req
Now restart the SDF target on h1build (as user controls)
h1sysecatc1plc1sdfstartup
If channels have been added, open the SDF MEDM screen and view the 'CHANS NOT INIT' table. Press the global 'MON' button (which selects all channels to ACCEPT and MON) and 'CONFIRM'. Now all new channels are being monitored, commissioners can decide if any should be taken out of this list.
Finally check the snap file changes into SVN.
This week I installed the ISS Outer Loop chassis into H1-PSL-R1, and hooked most of its cables up. The two AA cables for PDs 5-8 are not hooked up to an AA Chassis yet, and will be hooked up once the original servo is removed from the AA Chassis (The intention is to re-use one of the original ISS Outer loop servo's cables.) With the PSL down, I was unable to do any system testing. I have not disconnected any cables from the original servo, so it is still fully functional. I made an medm screen in UserApps/psl/h1/medm/H1PSL_ISS_OL.adl All of the new servo's functionality seems to be working. The TCS system had a bad channel that I traced back to the AA Chassis, S1301168. It turns out that 2 of the input buffers (U2 on channels 11 and 12) were bad. I replaced them, and now everything works fine. In the e-traveller, it seems that these chips have been replaced once before in February, 2015. We should keep an eye on them.
The broken hose was replaced. An attached picture shows the burst end of the hose and the fitting that
goes over that end. The two other attached pictures shows the hose, end on.
The turbine flow sensor for head 4 was replaced. Whilst there was no problem with this sensor per
se, its output was somewhat noisier than the three other sensors. Replacing it now seemed like a prudent
thing to do. A visual inspection of the flow sensor showed what might be a small build up of material
around the turbine. If true that would in part explain the noisy signal from this sensor.
The bulge in the crystal chiller return leg hose section in the chiller room was removed.
The resonator optics of the high power oscillator were inspected for dust and water marks. The 4f
lenses for heads 3 and 4 were drag wiped. The lens in front of the reverse direction power monitoring
photodiode was drag wiped clean. The fibre bundle ends are being given more time to dry out.
JeffB / Peter
G. Mendell, S. Karki, D. Tuyenbayev
Attached are plots showing the calibration factors (kappa_tst, kappa_pu, kappa_A, kappa_C and f_c) for ER9 generated from Spectral Line Monitor (SLM) data, analyzed using Matlab code from Sudarshan Karki and EPICS values from Darkhan Tuyenbayev.
The plots show the calibration factors from
1152010820 == Jul 08 2016 11:00:03 UTC
to
1152097220 == Jul 09 2016 11:00:03 UTC
For example, note the behavior of kappa_C and f_c after 18 hrs in the bottom row of the first attached plot.
A full set of plots can be found by going here,
https://ldas-jobs.ligo-wa.caltech.edu/~gmendell/pcalmon_with_plots/daily-pcalmonNavigation.html
and clicking on July 9 2016 in the calendar in the left frame, and then any of the links to the plots in the middle frame. (To compare with O1, click on Dec. 26, 2015 and then on the links to the plots.)
Technical Notes:
1. The SLM tool is in the calibration svn here,
aligocalibration/trunk/Projects/PhotonCalibrator/scripts/SLMTool
and analyzed line amplitudes and phases for the channels and frequencies given in this configuration:
set channelFrequencyList {H1_R,H1:SUS-ETMY_LKIN_P_LO_DQ,35.9aup;H1_R,H1:CAL-CS_LINE_SUM_DQ,37.3aup;
H1_R,H1:CAL-PCALY_EXC_SUM_DQ,36.7aup,331.9aup,1083.7aup;
H1_R,H1:CAL-PCALX_EXC_SUM_DQ,3001.3aup;H1_R,H1:CAL-DARM_ERR_WHITEN_OUT_DBL_DQ,35.9aup,36.7aup,37.3aup,331.9aup,1083.7aup,3001.3aup;
H1_R,H1:CAL-DARM_CTRL_WHITEN_OUT_DBL_DQ,35.9aup,36.7aup,37.3aup,331.9aup,1083.7aup,3001.3aup;
H1_R,H1:CAL-PCALY_TX_PD_OUT_DQ,36.7aup,331.9aup,1083.7aup;H1_R,H1:CAL-PCALY_RX_PD_OUT_DQ,36.7aup,331.9aup,1083.7aup;
H1_R,H1:CAL-PCALX_TX_PD_OUT_DQ,3001.3aup;H1_R,H1:CAL-PCALX_RX_PD_OUT_DQ,3001.3aup;
H1_R,H1:CAL-DELTAL_EXTERNAL_DQ,35.9aup,36.7aup,37.3aup,331.9aup,1083.7aup,3001.3aup;
H1_HOFT_C00,H1:GDS-CALIB_STRAIN,35.9aup,36.7aup,37.3aup,331.9aup,1083.7aup,3001.3aup}
with these replacements:
35.9 -> 35.3 Hz
H1:SUS-ETMY_LKIN_P_LO_DQ -> H1:SUS-ETMY_L3_CAL_LINE_OUT_DQ
2. EPIC values from Darkhan Tuyenbayev were used, found in the calibration svn here:
aligocalibration/trunk/Runs/PreER9/H1/Scripts/CAL_EPICS/D20160810_H1_CAL_EPICS_VALUES.m
See: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=29104
3. The Matlab code from Sudarshan Karki is in this tarball in the calibration svn,
aligocalibration/trunk/Projects/PhotonCalibrator/scripts/SLMTool/slm_matlab_analysis_code_for_compiling_ER9.tar
The Matlab code was changed from that used during O1, with these changes,
i. D20150929H1_CAL_EPICS_VALUES.m was replace with D20160810_H1_CAL_EPICS_VALUES.m. (And EP. was added to the front
of each EP value to make this into a struct; D20160810_H1_CAL_EPICS_VALUES is run by testSLMData_analysis.m.)
ii. In loadSLMData.m, 35.9 was changed to 35.3 Hz, and dewhitening.darm_err and dewhitening.darm_ctrl were changed to
unity gain filters by setting z = 2*pi*[1,1]; p = 2*pi*[1,1]. This is becuase the H1:CAL-DARM_ERR_WHITEN_OUT_DBL_DQ and
H1:CAL-DARM_CTRL_WHITEN_OUT_DBL_DQ do not need dewhitening, compared to the single precision version of these for O1.
4. This email from Shivaraj pointed out the need to use 35.3 Hz in place of 35.9 Hz.
-------- Original Message --------
Subject: [calibration] ESD line during ER9
Date: Thu, 4 Aug 2016 14:48:30 -0500
From: shivaraj ...
"Hi,
During the call I mentioned that one has to use 35.3 Hz line in channel
H1:SUS-ETMY_L3_CAL_LINE (same as O1) as opposed to 35.9 Hz we used
during O1.
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28164
In the above a-log entry it was mentioned that 35.9 Hz was run from a
different channel
(H1:SUS-ETMY_LKIN_P_OSC) and hence changing the channel should work. But
I don't see the
35.9 Hz line in CAL-DELTA_EXTERANL,
https://ldas-jobs.ligo.caltech.edu/~shivaraj/calibration/sus_lines_ER9.png
which is why I had switch the line frequency not the channel.
Cheers
shivaraj"
5. Previous alogs:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=27981
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=28164
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=29104
This morning I restarted h1psliss with the revised re-use of the ISS-ADC channels for the new ISS PD5-8 fast and slow signals. This required a DAQ restart. We took this opportunity to revise the H1EDCU_DUST.ini file and added Jonathan's new daqd diagnostics EPICS channels to H1EDCU_DAQ.ini.
Reconnected flow meter to exhaust of CP4 for measurements toward CP3 manual overfill work-around. Installation caused a quick spike in exhaust pressure >3psi. (signal name includes CP3 since the device will eventually migrate to CP3 exhaust - CP4 is temporarily being used to collect data to simulate CP3)
Ch 6: H0:VAC-MY_CP3_FL201_DISCHARGE_FLOW_SLPM Ch 7: H0:VAC-MY_CP3_FL201_DISCHARGE_FLOW_MA
Executive summary:In regard to narrow lines, the (nearly) full O1 H1 data set is little changed from what was reported for the first week's data: a pervasive 16-Hz comb persists throughout the CW search band (below 2000 Hz), accompanied by a much weaker and more sporadic 8-Hz comb; there remain several distinct 1-Hz and nearly-1-Hz combs below 140 Hz, along with other sporadic combs. The 1459.5 hours of 30-minute FScan SFTs used here span from September 18 to the morning of January 3. The improved statistics make weaker and finer structures more visible than in the 1st week's data. As a result, many new singlet lines have been tagged, and it has become apparent that some previously marked singlets actually belong to newly spotted comb structures. The improved statistics also make it more apparent that the originally spotted combs span a broader bandwidth than marked before Details: Using 1459.5 hours of FScan-generated, Hann-windowed, 30-minute SFTs, I have gone through the first 2000 Hz of the DARM displacement spectrum (CW search band) to identify lines that could contaminate CW searches. This study is very similar to prior studies of ER7 data, ER8 data and the first week of O1 data, but for completeness, I will repeat below some earlier findings. Some sample displacement amplitude spectra are attached directly below, but more extensive sets of spectra are attached in a zipped file. As usual, the spectra look worse than they really are because single-bin lines (0.5 mHz wide) appear disproportionately wide in the graphics A flat-file line list is attached with the same alphabetic coding as in the figures. Findings:
In week 1 Keith identified a comb-on-comb (labeled K, see attached plot), fine spacing 0.08842 Hz, which shows up sporadically at around 77, 154, and 231 Hz. We found it in a large group of channels, centered at the INPUTOPTICS/SUS-BS/SUS-ITM (see full attached list). It remains clearly visible (especially at 77 Hz) in those channels until week 5 of O1, during which it disappears from all of them in all three regions (see attached example). Therefore, it seems likely that its presence in the full O1 data is an artifact from the first four weeks.
I recently re-analyzed this data while testing a comb-finding algorithm, and in the process found a new comb which accounts for several peaks marked as singlets in Keith's original post. This comb has a 2.040388 Hz spacing, with visible harmonics from 9th (18.3635 Hz) to 38th (77.5347 Hz). The code I used, and its docs, can be found on gitlab (requires login).
here is a minute trend log plot of HAM6 vacuum from 7/34 to present. Note the Y range from 1.0e-07 to 1000. The gap in the middle is when HAM6 was opened and the Cold Cathode gauge was turned off (reporting 0.0 which does not plot on a log scale).