O1 days 18-21
model restarts logged for Thu 08/Oct/2015
2015_10_08 09:29 h1nds1
2015_10_08 12:37 h1asc
2015_10_08 12:47 h1broadcast0
2015_10_08 12:47 h1dc0
2015_10_08 12:47 h1nds0
2015_10_08 12:47 h1nds1
2015_10_08 12:47 h1tw0
2015_10_08 12:47 h1tw1
One unexpected restart of nds1. ASC restart for new model code, with associated DAQ restart.
model restarts logged for Wed 07/Oct/2015
No Restarts Reported.
model restarts logged for Tue 06/Oct/2015
No Restarts Reported
model restarts logged for Mon 05/Oct/2015
Many unexpected restarts of h1tw0 due to raid issues. No other restarts. Due to large size, full report in attached file.
HAM4 and HAM5 have had strong glitches for the past several weeks (sorry if I missed this being reported already, I didn't turn it up in a search, we found these by accident). They are sometimes completely not there, but sometimes happening as fast as twice per second! Attached are a slew of plots taken roughly every two days for H1:ISI-HAM4_BLND_GS13RZ_IN1_DQ (but I also see the same in H1:ISI-HAM5_BLND_GS13RZ_IN1_DQ).
We don't have a good lead on these, but wanted to report. They look an awful lot like what we have seen before when the HWS camera was on, see e.g., 18531. I noticed a note in the log on August 25 "15:54 Elli – Going to Hartman table at HAM4", and I also noticed that the glitches started showing up after a long hiaitus around August 27th. However, if I have my sign correct (0=off) for the camera switch channels, then the HWS cameras in the central station are currently off in O1 running.
Assuming it's not HWS, we should probably check ISI actuators for DAC glitches or overflows.
I can confirm that the corner station HWS cameras are all turned off. So 0=off is correct. And If I'm reading the spectrograms correctly the glitch rate seems to change from day to day. HWS camera doesn't do that.
Title: 10/9 Owl Shift 7:00-15:00 UTC (0:00-8:00 PST). All times in UTC.
State of H1: Observing
Shift Summary: Locked for the entire shift in Observing. Wind and seismic calm. Several ETMy saturations, none of which correspond to any RF45 glitching (since there was none that I saw).
Incoming operator: TJ
Activity log: None to speak of. Very quiet night.
Locked in Observing Mode for the duration of the shift so far. A few ETMy saturations, but none of them seemed to coincide with any RF45 glitching, as that has been stable.
TITLE: "10/08 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PDT), all times posted in UTC"
STATE Of H1: Observing at ~80 Mpc for the past 6 hours
SUPPORT: Jenne, Sheila
SHIFT SUMMARY: Few problems when we began to acquire lock. Smooth ride afterward. Wind speed dropped below 10 mph. No big earthquake. Only one ETMY saturation since we acquired lock. RF45 wan't acting up when the verbal alarm went off.
INCOMING OPERATOR: Travis
ACTIVITY LOG:
23:41 LLO delayed observing for another hour. We take sometimes to do some commissioning work.
0:44 Robert to LVEA to turn off stuff. No injection.
00:38 Locked at NOMINAL LOW NOISE
00:55 Cleared off ASCIMC excitation. Switched to Observing.
05:05 GRB Alert
The new rooftop camera is amazing. I can actually see things at night!
We set all quadrant gains of IMC WFSA to [1 1 1 1] from [1, 0.25, 1, 4]. (WFSB was already all 1.)
We also disabled IMCWFS error offsets in servo filters.
After this, we steered IM2 to bring the beam position on IM4 trans back (at first we tried IM3, but it would make the OSEM output to become larger, and they're already close to saturation).
IFO locked after this without any problem.
We haven't done any jitter coupling optimization and I don't know if Robert had time to do it.
The first and the second attachment show the current and the old settings, respectively.
In the first one, yellow boxes show what we changed. Red box show what we changed but are somehow reverted (automatically?).
This is just an observation related to entry 22482 where I was investigating the relation between ISS and IMC.
After Keita and Cheryl set the IMC WFS gains back to 1, it seems to have shifted the pointing to the ISS array a little bit. See the attached trend.
The QPD signals at the ISS array have moved by 0.1 or so both in PIT and YAW when the WFS gain was changed to 1. Both PIT and YAW moved towards the center of the QPD although SUM seems to have decreased at the same time. I am not sure what exactly was going on. We may need to optimize the pico-motors to minimize the jitter-coupling to the ISS array.
Only one ETMY saturation in 4 hours. Wind speed decreasing together with seismic.
TITLE: 10/8 [EVE Shift]: 23:00-07:00UTC (16:00-00:00 PDT), all times posted in UTC"
STATE Of H1: Observing at ~79 Mpc.
OUTGOING OPERATOR: Ed
QUICK SUMMARY: Sorry been busy. We spent about 1.5 hours at the begining of this shift trying to acquire lock. Had one lockloss and few other minor issues (ISS 2nd loop freaked out, had to find IR by hand). We locked again at NOMINAL LOW NOISE 00:38 UTC but since LLO wasn't Observing we took some time to do extra comissioning. The ifo state switched to Observing at 00:55 UTC. ~15 mph wind, EQ band seismic activity raised accordningly.
After today's Commissioning Day activities, we had quite a few SDF differences to clear out.
For the ASC, we accepted several things that will be regularly used for the A2L measurements. These are all channels of the ASC-ADS_ sub-subsystem. The things we accepted will have no effect on the interferometer, since during observation we don't use this system at all. We accepted things like the frequencies of the A2L measurements, the ramp times, and the matrix elements. Note that the "CLKGAIN", which is the acutal oscillator amplitude, is still set to zero in SDF, so if any excitation is happening, it'll be flagged in SDF.
I also accepted the new IM2 Pit and Yaw offset values, which were set after Keita and Cheryl did their IMC work today. (Since the IMC pointing moved slightly after their WFS work, they compensated by moving IM2 a bit). Keita and I also accepted several diffs from the ASCIMC model, that were changed as a result of their WFS work today.
Today I was able to remeasure the frequency noise coupling into DARM. I am not finished analyzing the data, but as a preview I am attaching the TF of the IMC VCO to the DCPD sum above 1 kHz. The coupling appears to go like 1/f, or perhaps slightly faster. A 1/f coupling would be consistent with what was found previously (a flat coupling from REFL9I power to DCPD photocurrent).
I was not able to get coherence between my CARM excitation and the IMC VCO below 1 kHz.
Attachment shows TF of demodulated REFL9 volts to DCPD sum (in milliamps). Compared to the previous measurement, the high-frequency portion is a factor of 3 higher. Additionally, we do not clearly see a transition to 1/f2 behavior around 250 Hz, as was seen in the last measurement. One might plausibly claim that the new measurement shows a knee around 100 Hz.
At 50 Hz, this TF predicts a frequency noise coupling that is a factor of 4 or so lower than the previous measurement.
Additionally, during the measurement I noticed that the nonlinear coupling into DARM was quite significant from 40 to 100 Hz; we could see broad wings around the excitation frequency.
TITLE: Oct 8 DAY Shift 15:00-23:00UTC (08:00-04:00 PDT), all times posted in UTC
STATE Of H1: Commissioning
LOCK DURATION:~4hours (this shift)
SUPPORT: All commissioners
INCOMING OPERATOR: Nutsinee
Activity log:
15:00 IFO taken to commissioning for today’s activities
15:01 Evan out to LVEA to get some cables
15:03 Jeremy called from LLO to confirm the beginning of joint commissioning activities
15:04 Lights switched on in the LVEA
15:08 Patrick doing CONLOG testing
15:11 Evan performing WP#5543
15:31 Noticed that the DARM spectra FOM had stopped. Will wait to restart after Evan is done taking measurements. NDS1 seems to have died. No CDS techs on site. E-mail sent.
16:25 Dave called about the NDS1 server. He’s taking a look
16:30 Premier Flooring on site.
16:31 D Barker re-started NDS1 server
17:11 IFO handed over to Robert Schofield for PEM injections
18:10 Robert handed IFO back over to Evan
18:12 Richard out to the roof for Camera install work
19:06 Ellie and TJ to CER to plug in wireless router
19:11 Ellie and TJ are back
19:15 IFO unlocked by Ellie for her measurements. WP#5548
19:30 Ellie out to ISCT6
19:35 ASC restart
20:18 Bubba and John into the LVEA by the Yarm
20:33 Bubba and John out of LVEA
21:05 Ellie out of the LVEA
21:10 John into LVEA for a tour
22:15 begin initial alignment
22:29 RF45 cable was changed for a shorter one. Keita needs a free-swinging Michelson to do a phase measurement before we proceed with locking.
Shift Summary: Commisioning Day
Attached are pitch/yaw spectra for the currently active SUS optical levers (ITMx/y, ETMx/y, PR3, SR3, BS), taken during a quiet lock stretch from yesterday @ 15:00 UTC (08:00 PDT). Based on these spectra, everything looks healthy. As an additional check (especially considering Sheila's report of BS oplev glitching here), I looked at the oplev SUM spectrograms posted on the DetChar summary pages. Looking at these (both the normal ASD spectrogram and the normalised ASD spectrogram) it can be seen that the BS (here) and ETMx (here) oplev lasers are showing signs of glitching (the broadband lines indicate this). After talking with Sheila, since BS oplev damping is only used in DRMI lock acquisition and then turned off, there is no rush to replace the BS oplev laser. We might save a little time in DRMI acquisition, but it so far is not a detriment to IFO operation (this is good as I cannot guarantee the spare laser I currently have will perform any better; I'm still waiting on a shipment of repaired lasers from the manufacturer that will alleviate this). ETMx oplev damping is not used at all, so also no rush to replace. The current SUS oplev laser replacment priority list is thus:
The peak at 78 Hz seems to have come from a different noise coupling than the bilinear coupling of ISI motion. Yesterday we noticed that the beam diverter at EX has been open since June. When we closed this the excess noise in the TMS QPDs disappeared, as well as the 78 Hz peak in DARM. alog 22286
In the course of investigating the 78 Hz peak, we saw a bilinear coupling from ETMX ISI to DARM (where there is only a linear coupling from ETMY), which we had thought could be related to the niose in DARM although we could see immediately that the motion seen by the GS13s was not enough to explain any noise in DARM. alogs 22107 and 22159 21767
In the course of investigating this we learned a few things:
Here I've attached a few plots from my last two measurements, which I made just before noticing the beam diverter was open and then repeated last night with the beam diverter closed for completeness. The results are the same with the beam diverter open and closed, which makes sense since we now that TMS motion is not involved in this noise coupling.
The first plot is a ratio of DARM noise to GS13 motion in nm. You can compare this to the B&K measurements that Betsy compiled alog 22169. It seems that the shape of this coupling is very similar to the quad cage resonances, so scattered light off of some part of the cage seems like a plausible mechanism.
The second plot shows a projection of this noise into DARM, which is a factor 20 below DARM around 70 Hz.
Today we replaced the roof camera with a new network camera. It is best viewed from the monitor where the Access system is. This monitor now has two computers connected to it. One the access computer and the other the Roof camera computer. you can easily switch between the two with the buttons on the monitor. The camera is accessed view a web browser. Designed for Windows explorer but we have Mozilla working on this machine. I will post the IP address on the monitor. Standard controls password accesses the camera and you control pan/tilt and zoom with the mouse and the controls on the left side of the screen. I will be adding go to points like a view of the gate that with a simple click the camera will adjust to. This is proving somewhat difficult as we do not have all of the plugins installed. If you have to re-open the screen accept the certificate and continue. If the video seems quite small on the left side select a different video stream then return to 1 and the screen will resized. This is a new camera so try it out and we can make some changes and possibly get a joy stick if people want.
Commissioners asked me to add the Beckhoff controlled Servo Board outputs (FASTEXCEN & COMEXCEN) to DIAG_MAIN until the SDF Beckhoff is up. Code and example notification attached.
The attached plot shows the history of the controls signal over the past 24 hours. There was a step down about 12h ago in the control signals followed by a return to the old value about 6h ago.Some of the glitches were also seen in the 45MHz unit set up in the CER (shown in the 9MHz channel).
(Fil Keita Daniel)
Replaced the delay line extension in the RF45 EOM cable run and reterminated the cable towards the EOM. Tapping at the connectors and wiggling the cable still results in glitches. But, so does wiggling neighboring cables. At this point it isn't clear, if we are chasing a red herring. Needs to be monitored.
I checked the RF phase and it did by 1.8(0.1) deg from before. Should be OK.
Free swing MICH, measured TF H1:LSC-ASAIR_A_RF45_Q_ERR_DQ/H1:LSC-ASAIR_A_RF45_Q_ERR_DQ with BW=0.1875Hz and took the data in [0.125, 0.75] band. Phase is pretty much 0 degrees, the important thing is the amplitude.
Amplitude(Q/I) = 5.18(0.04) (mean and sigma).
Therefore the demod phase is atan(amplitude(Q/I)) = 79 .07(0.08) deg.
| phase | |
| Aug. 10 (alog 20392) | 76.4(6) |
| Sept. 29 (alog 22061) | 77.3(0.03) |
| Today | 79.1(0.08) |
Summary: We had single-IFO time so I tested the new inverse actuation filter for PCALX. WP5530 Sudarshan and I believe we tracked down the factor of 2 and sign error from the initial PCALX test, see aLog 22160. We wanted to do this test to confirm that. CBC injections: The waveform file is: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/H1/coherenttest1from15hz_1126257408.out The XML parameter file is: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/h1l1coherenttest1from15hz_1126257408.xml.gz I did three CBC injections. The start times of the injections were: 1128303091.000000000, 1128303224.000000000, and 1128303391.000000000. The command line to do the injections is: ezcawrite H1:CAL-INJ_TINJ_TYPE 1 awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 coherenttest1from15hz_1126257408.out 1.0 -d -d >> 20151006_log_pcal.out awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 coherenttest1from15hz_1126257408.out 1.0 -d -d >> 20151006_log_pcal.out awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 coherenttest1from15hz_1126257408.out 1.0 -d -d >> 20151006_log_pcal.out I have attached the log. I had to change the file extension to be posted to the aLog. DetChar injection: I injected Jordan's waveform file: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/detchar/detchar_03Oct2015_PCAL.txt The start time of the injection is: 1128303531.000000000 The command line to do the injections is: awgstream H1:CAL-PCALX_SWEPT_SINE_EXC 16384 detchar_03Oct2015_PCAL.txt 1.0 -d -d >> 20151006_log_pcal_detchar.out I have attached the log. I had to change the file extension to be posted to the aLog.
Chris Buchanan and Thomas Abbott,
Quick follow-up with omega scans. It looks like most of the power is seen in GDS-CALIB_STRAIN about eight seconds after each listed injection time, consistently for each of these three injections. Doesn't look like there are omicron triggers for these times yet, but omega scans for GDS-CALIB_STRAIN are attached.
Full omega scans generated here:
https://ldas-jobs.ligo.caltech.edu/~christopher.buchanan/Omega/Oct07_PCALX_Inj1/
https://ldas-jobs.ligo.caltech.edu/~christopher.buchanan/Omega/Oct07_PCALX_Inj2/
https://ldas-jobs.ligo.caltech.edu/~christopher.buchanan/Omega/Oct07_PCALX_Inj3/
For complete documentation of the detchar safety injections:
The injections are 12 sine-gaussians, evenly spaced from 30hz to 430hz, 3 seconds apart with a Q of 6. There are three sets with increasing SNR of 25, 50, 100 (intended). However, the SNR is limited by the PCAL acuation range at higher frequencies.
To generate the waveforms I used the script written by Peter Shawhan / Andy located here: https://daqsvn.ligo-la.caltech.edu/websvn/filedetails.php?repname=injection&path=%2Fhwinj%2FDetails%2Fdetchar%2FGenerateSGSequencePCAL.m
I tuned the injections to stay within the PCAL actuation limits referenced in Peter Fritschel's document https://dcc.ligo.org/LIGO-
The intended time (seconds from start time of injections), freqency, snr, and amplitude (in units of strain) for all injections are pasted below:
__time__ __freq__ __SNR__ __AMP__
0.50 30.0 25.0 5.14e-21
3.50 38.2 25.0 4.96e-21
6.50 48.7 25.0 2.15e-21
9.50 62.0 25.0 2.07e-21
12.50 79.0 25.0 1.75e-21
15.50 100.6 25.0 1.78e-21
18.50 128.2 25.0 1.92e-21
21.50 163.3 25.0 2.06e-21
24.50 208.0 25.0 2.39e-21
27.50 265.0 10.0 1.11e-21
30.50 337.6 5.0 8.39e-22
33.50 430.0 5.0 8.51e-22
36.50 30.0 50.0 1.03e-20
39.50 38.2 50.0 9.92e-21
42.50 48.7 50.0 4.31e-21
45.50 62.0 50.0 4.14e-21
48.50 79.0 50.0 3.51e-21
51.50 100.6 50.0 3.55e-21
54.50 128.2 50.0 3.85e-21
57.50 163.3 50.0 4.12e-21
60.50 208.0 50.0 4.77e-21
63.50 265.0 20.0 2.21e-21
66.50 337.6 10.0 1.68e-21
69.50 430.0 10.0 1.7e-21
72.50 30.0 100.0 2.06e-20
75.50 38.2 100.0 1.98e-20
78.50 48.7 100.0 8.62e-21
81.50 62.0 100.0 8.27e-21
84.50 79.0 100.0 7.01e-21
87.50 100.6 100.0 7.1e-21
90.50 128.2 100.0 7.69e-21
93.50 163.3 100.0 8.24e-21
96.50 208.0 100.0 9.54e-21
99.50 265.0 40.0 4.43e-21
102.50 337.6 20.0 3.36e-21
105.50 430.0 20.0 3.4e-21
Here are the SNR of the CBC injections using the daily BBH matching filtering settings: end time SNR chi-squared newSNR 1128303098.986 20.35 32.86 19.86 1128303231.985 22.62 32.73 22.10 1128303398.985 23.25 21.05 23.25 Expected SNR is 18.4. Though a recovered SNR of 20 (about 10% percent difference from 18.4) is comparable to some of the SNR measurements when doing injections with CALCS in aLog 21890. Note this is the same waveform injected here except in aLog 21890 it starts from 30Hz. In both cases the matched filtering starts at 30Hz. The last two have a bit higher SNR though.
I edited Peter S.'s matlab script to check the sign of these PCAL CBC injections. Looks like the have the correct sign. See attached plots. To run code on LHO cluster: eval '/ligotools/bin/use_ligotools' matlab -nosplash -nodisplay -r "checksign; exit" Also in hindsight I should have done a couple CALCS CBC injections just to compare the SNR at the time with the PCAL injections.
gwdetchar-overflow -i H1 -f H1_R -O segments -o overflow --deep 1128303500 1128303651 124
It returns an empty table, so no overflows.
A time-domain check of the recovered strain waveforms is here: https://wiki.ligo.org/Main/HWInjO1CheckSGs. I found that the sign is correct, the amplitude matches within a few percent at most frequencies, and the phases are generally consistent with having a frequency-independent time delay of 3 or 4 samples (about 0.2 ms). Details are on that wiki page.
Thomas Abbot, Chris Buchanan, Chris Biwer
I've taken Thomas/Chris' table of recovered omicron triggers for the PCAL detchar injection and calculated the ratio of expected/recovered SNR and added some comments:
Recovered time time since frequency recovered expected recovered/expected comments
1128303531 (s) (Hz) SNR SNR SNR
1128303531.5156 0.515599966 42.56 34.07 25 1.3628
1128303534.5078 3.5078001022 61.90 39.41 25 1.5764
1128303537.5039 6.5039000511 64.60 28.29 25 1.1316
1128303540.5039 9.5039000511 79.79 23.89 25 0.9556
1128303543.5039 12.5039000511 1978.42 21.38 25 0.8552 suspicious, the frequency is very high
1128303546.502 15.5020000935 144.05 26.24 25 1.0496
1128303549.502 18.5020000935 185.68 26.38 25 1.0552
1128303552.502 21.5020000935 229.34 26.29 25 1.0516
1128303555.501 24.5009999275 918.23 27.34 25 1.0936
1128303558.501 27.5009999275 315.97 11.05 10 1.105
1128303564.5005 33.5004999638 451.89 6.76 5 1.352
1128303567.5156 36.515599966 50.12 68.53 50 1.3706
1128303570.5078 39.5078001022 61.90 78.23 50 1.5646
1128303573.5039 42.5039000511 76.45 52.04 50 1.0408
1128303576.5039 45.5039000511 91.09 48.42 50 0.9684
1128303579.5039 48.5039000511 116.63 47.73 50 0.9546
1128303582.502 51.5020000935 144.05 52.59 50 1.0518
1128303585.502 54.5020000935 177.91 52.3 50 1.046
1128303588.502 57.5020000935 261.81 54.8 50 1.096
1128303591.501 60.5009999275 323.36 55.64 50 1.1128
1128303594.501 63.5009999275 414.01 19.67 20 0.9835
1128303597.501 66.5009999275 390.25 9.55 10 0.955
1128303600.5005 69.5004999638 481.99 9.34 10 0.934
1128303603.5156 72.515599966 48.35 136.81 100 1.3681
1128303606.5078 75.5078001022 71.56 156.91 100 1.5691
1128303609.5039 78.5039000511 76.45 102.72 100 1.0272
1128303612.5039 81.5039000511 138.03 102.85 100 1.0285
1128303615.5039 84.5039000511 134.83 95.52 100 0.9552
1128303618.502 87.5020000935 1283.14 104.17 100 1.0417 frequency seems a bit high
1128303621.502 90.5020000935 211.97 107.18 100 1.0718
1128303624.502 93.5020000935 261.81 104.53 100 1.0453
1128303627.501 96.5009999275 323.36 109.66 100 1.0966
1128303630.501 99.5009999275 414.01 42.15 40 1.05375
1128303633.5005 102.5004999638 959.39 19.11 20 0.9555 this last injection had some kind of glitch on it
In most cases looks like the ratio is within 0.1 of 1. On a quick glance I see 10 injections that were not within this range.
The low-voltage electro-static driver (D1500016) includes monitors of the output quadrant drive signals that are sent to ADCs for sampling/monitoring (in a SUS IO chassis). The monitors look at the drive voltage after the normal inputs, test inputs, and parametric instability correction inputs are summed together. Each monitor path has a 1:4 voltage divider to fit the full driver range into the ADC input range.
Looking at these monitor channels for ETMY from a recent lock stretch shows several problems with these monitors as useful readbacks for the electro-static drive signals. In the attached plot, the two traces are:
There are several problems:
Followup work to do: i) check the behavior of the same channels on L1 for comparison; ii) test the behavior of the monitor channels with a spare unit on the bench, in the presence of a signal
It's analog. We need a usable whitening for this. (Daniel, Keita)
The noise floor is not a digital artefact, the analog gain seems to be too small to see anything useful at 100Hz. Even if we move 42Hz LPF up to 1k, we would still need a useful whitening, e.g. two stages of ISC style whitening.
In the first attachment top, red, blue and green are the same ETMY LL ESD low voltage monitor at different points, i.e. red is the test point in SUSAUX (2k), blue is DQ of the same (256), and green is in the IOP model (64k) before the signal comes into SUSAUX.
Also shown is the digital output test point (pink and cyan, pink taken at the same time as red) projected onto the LV monitor by removing the whitening and putting 40Hz LPF and adjusting the DC scaling. No wonder we're not seeing anything useful at 100Hz.
RMS of IOP channel is basically 1 count down to 8Hz or so, and this means that the noise floor is just ADC noise. RMS of this same signal goes only up to 180 or so counts at 1Hz. Changing 42Hz LPF with 1k is not enough for frequency lower than maybe 400Hz or so.
Boosting the analog gain by a factor of 100 or so, the RMS at low frequency would become uncomfortably large.
The second attachment shows what happens when there are two stages of ISC whitening (z=[1;1] p=[10;10]) plus 1kHz LPF instead of 42Hz, without changing DC gain.
The RMS between 1 and 10 Hz becomes 2000 counts-ish, RMS for f>10 becomes 100 counts-ish, and the monitor noise floor would be at least a factor of 10 larger than the noise floor for f<1k.
In the future, when our sensitivity increases by a factor of 3+ or something for f>100Hz and our drive drops by the safe factor, we might have to think about more whitening or more whitening gain. By that time, we might also be able to more aggressively cut down the low frequency part (f<5Hz) of the drive on ESD. According to Evan ESD-PUM crossover is about 20Hz (alog 19859) so it sounds doable.
[update 0:40 UTC] The third attachment shows the DQ channel (red), test point (blue) and IOP channel (green, which is almost completely masked by blue) measured at the same time up to 116Hz. They're the same except decimation filters.