While trying to phase AS_B 90MHz signals (hooked up to AS_B_FR45), we noticed that the phase to the signal changes dramatically with the amopunt of power on the quadrant. Attached is a time series of the DC power (Blue. 0 is on top, more power goes negative), as well as I and Q phase. On this plot we first maximized the light on Seg1, then phased all signal into I, then noticed that the phasing changes with power on the segment, then reduced the power into the DRMI in 4 steps. As you can see the phasing dramatically changes with the power on the diode...
Here are the 36 signals at the same time. As the power drops by roughly a factor of 2, the signals also drop by roughly a factor of 2, without any apparent change in the phase.
This confusion was due to dark offsets - the for some reasone changed significantly.
J. Kissel, K. Izumi Kiwamu and I have spent the day tuning measurements, and finally gathering all transfer functions that use the IFO to determine the overall scale factor of all stages of the ETMY actuator. To refresh your memory, that's using PCAL, ALS DIFF VCO / PLL, and Free Swining Michelson techniques. We tried following the prescription that Joe, Kiwamu and I had agreed upon (see T1500383), but we ran into a few flaws in our plan, and diverted accordingingly. However, I think we have everything we need to make estimates of the actuation strength of ETMY with these three methods, as has been done prior to ER7 (see LHO aLOG 18767). As with other measurements this week, analysis and results are to come, but we want to at least aLOG where the measurements live, and the details / gotchas of today's exercise so that we remember them in the future. Details ------------ The list of measurements (and how they differ from T1500383): PCAL: optic [m] RXPD [ct] PCALY [m] IFO DARM [ct] ETMY L3 LV LPON EXC [ct] IFO DARM [ct] --------------- = ---------- x ------------- x ------------------------- x ------------------------ x --------------- iStage EXC [ct] PCALY [m] IFO DARM [ct] ETMY L3 LV LP ON EXC [ct] IFO DARM [ct] iStage EXC [ct] (1) (2) (X) (X) (Y) Measurement (1) we obtain, a priori, from the PCAL team. This is determined by their estimation of the power on the test mass (see, e.g. LHO aLOG 20459, and more completely in T1500252). Measurement (2) is a PCAL to DARM transfer function (DARM_IN1 / RX_PD) using the pre-calibrationed (from (1)) RX_PD channel as the reference. Measurements (X) and (Y) are lettered not numbered, because these same transfer functions are used for all three measurement techniques. However, these (Y) (and (X)) transfer functions are drives from the L3 / L2 / L1 TEST L filter banks at each stage, such that the exciations downstream of all LOCK and DRIVEALIGN heirarchy filter banks. Therefore we're only measuring the actuation strength of each stage (without the confusion of the hierarchical control filters). The response channel is DARM_IN1. Note that (X) is repeated twice in the PCAL method because we get an absolute [m / ct] calibration for the ETMY L3 EXC, which is then propogated to the PUM/L2 and UIM/L1 stages as well, which we do by using the ratio of (X) and (Y). Measurements (2), (X), and (Y) are gathered with the IFO fully locked using all of ETMY in its lowest noise state. ALS DIFF: What we had planned to do, as shown in T1500383, was the following: optic [m] f_green [Hz] L_arm [m] DIFF PLL [ct] ETMY HV L3 EXC IFO DARM [ct] ---------- = A_VCO x ------------- x ------------ x ------------------- x (1 + G_DIFF) x -------------- x --------------- iStage EXC DIFF_PLL [ct] f_green [Hz] ETMY L3 HV EXC [ct] IFO DARM [ct] iStage EXC [ct] (3) (4) (5) (6) (7) (Y) However, we ended up doing a few of the measurements differently today, for two reasons: (a) For (5), we had previously used ETMX L2 (see LHO aLOG 18711). We had used ETMX L2 because it was an out-of-loop excitation; ALS DIFF uses EX L3 and EX L1 to lock green, but it does not use the EX L2 stage. However, we were sad about the 1/f^4 roll-off of the L2 actuator -- it provided little coherence above the relatively noise ALS DIFF noise. Instead of using ETMX L2 EXC, one immediately suggest using ETMX L3 with the high-voltage driver, but we were worried about confusion with the loop hierarchy, so we though to go with ETMY L3 in its high voltage configuration -- that way we could similarly treat it as an out-of-loop excitation, we wouldn't have to worry about being confused by the hierarchy of the ETMX control, and we'd get the extra f^2 of actuation strength. HOWEVER we didn't think of this ahead of then, but it was implicitly assumed that we could lock the full IFO on ETMY with the driver in its HV stage in order to transfer the ALS DIFF absolute calibration of the ETMY L3 HV configuration to the ETMY L3 LVLN, LP ON configuration. We've *not* developed developed a stable configuration with the Full IFO locked with ETMY L3 HV, and even if we had it, we've not demonstrated that we can switch between HV and LV LP ON while the interferometer is locked. We figure commissioning such a thing was a huge adventure that we did not want to undertake. (b) It turns out, with a little bit of ingenuity (a.k.a. Izumi-sensei wisdom), we can use the entire ETMX drive as a whole (i.e. the super-actuator of L3 and L1) in concert with the DIFF PLL CTRL signal that we've already calibrated to obtain the equivalent of (3) and (4). Take the ALS DIFF loop as follows, where excite just down stream of the DARM bank, such that you're still using the SUS in whatever hierarchy is predefined (we used the L3 LOCK bank): +------+ +------+ -----| ETMX |----| DIFF |-------> DIFF_PLL_CTRL | +------+ +------+ | | | IN2 <-| | | +------+ | + ----< -1 |---| DARM |------- ^ +------+ | L3 LOCK EXC It so follows that L3 LOCK IN2 1 ----------- = ---------- L3 LOCK EXC 1 + G_DIFF which is true with any excitation at any point around the loop, just like is done "normally" done with a DARM IN2 / DARM EXC TF. Further, DIFF_PLL_CTRL 1 ------------- = ---------- x ETMX x DIFF L3 LOCK EXC 1 + G_DIFF one can immediately see that the absolute calibration of the super-actuator ETMX falls out of ratio of these two transfer functions, assuming you have the absolute calibration of DIFF such that you can divide it out (i.e. the [Hz/ct] and z:p = 40:1.6 Hz pair of the VCO, i.e. measurements (3) and (4), which we do, a priori). What's great, is that since you're using the same excitation, as long as you store both of these channels in the template, you can directly measure and export the transfer function ratio that you really want, DIFF_PLL_CTRL ------------- = ETMX x DIFF L3 LOCK IN2 and thus you've reduced two measurments, formerly (5) and (6) into one. So today's version of the ALS DIFF Equation is optic [m] f_green [Hz] L_arm [m] DIFF PLL [ct] ETMX L3 LOCK EXC [ct] IFO DARM [ct] ---------- = A_VCO x ------------- x ------------ x ------------------- x --------------------- x --------------- iStage EXC DIFF_PLL [ct] f_green [Hz] EX L3 LOCK IN2 [ct] IFO DARM [ct] iStage EXC [ct] (3) (4) (5) (Z) (Y) Measurement (3) is obtained by measuring the open loop gain of the ALS DIFF PLL independently, while locked to an independent frequency reference, instead of the beat-note from the DIFF PD, i.e. LHO aLOG 20850, LHO aLOG 20542, etc. Measurement (4) is obtained by using the ALS DIFF PLL in the same way as (3), but sweeping the lock frequency of the frequency reference, i.e. LHO aLOG 20603. Measurement (5) is as described above, driving EX L3 LOCK EXC while the IFO is only ALS DIFF locked, but measuring the transfer function EX L3 LOCK IN2 and DIFF_PLL_CTRL Measurement (Z) is performed with the IFO in full low noise lock (locked on ETMY in its low-noise state). Note that the nominal lowest noise state is to have the ETMX driver turned OFF. With the driver ON (so you can take this measurement) the ESD DAC noise destroys the low frequency performance, so you have to drive pretty dang hard to get good coherence. Measurement (Y) are as described above. Free Swinging Michelson Similarly to the ALS DIFF method, we planned (in T1500383) to propogate the Michelson absolute calibration down the Y-arm, instead of the X-arm like we had done previously (see LHO aLOG 18718), by driving ETMY using the high-voltage driver. For the same reasons as DIFF, propogating that absolute calibration to the LVLN LP ON configuration in full-lock would have been hard-to-impossible. As such, we performed measurements in exactly the same way we had done before, propogating down the X ARM, and relying on (Z) from the ALS DIFF technique, optic [m] MICH [m] AS_Q [ct] ITMX L2 EXC [ct] SARM [ct] ETMX L3 LOCK EXC [ct] IFO DARM [ct] ----------- = ----------- x (1 + G_MICH) x ---------------- x ---------------- x --------------------- x --------------------- x -------------- iStage EXC AS_Q [ct] ITMX L2 EXC [ct] SARM [ct] ETMX L3 LOCK EXC [ct] IFO DARM [ct] iStage EXC [ct] (6) (7) (8) (9) (10) (Z) (Y) Measurement (6) is the "free-swinging" part of the free-swinging Michelson, where we fit the AS_Q and AS_DC signals to an ellipse to obtain the optical gain of the Michelson. Measurement (7) is the open loop gain of the Michelson, taken with MICH locked using the BS, such that we can back out the loop suppression from the ITM excitation. Measurement (8) is the ITM excitation, taken in the same MICH lock stretch as (2). Note that we made sure to put the ITM L2 stage in its highest range state (state 2) to get the best SNR. Measurement (9) and (10) are taken with the XARM locked on red. The only difference this time is that we drove from the LOCK bank, again treating ETMX as a super-actuator, not caring about the individual strength of the test mass stage. One last thing regarding all of these measurements. We had set a goal to get coherence out to 200 [Hz], but Kiwamu found on Monday that ALS DIFF measurement (5) was difficult to get --------------------- The data / templates for the IFO measurements we took / tuned today have been committed to the CalSVN in the following locations: (2) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-26/ 2015-08-26_H1SUSETMY_PCALYtoDARM_FullLock.xml (5) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/ALSDIFF/2015-08-26 2015-08-26_ALSDiff_ETMX_L3_HVHN.xml (6) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-26/ 2015-08-26_H1MICH_freeswingingdata.xml (7) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-26/ 2015-08-26_MICH_OLGTF.xml (8) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-26/ 2015-08-26_H1SUSITMY_L2_State2_MICH.xml (9) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-26/ 2015-08-26_H1SUSITMX_L2_State2_XARM.xml (10) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FreeSwingMich/2015-08-26/ 2015-08-26_H1SUSETMX_L3_HVHN_XARM.xml (X) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-26/ 2015-08-26_H1SUSETMY_L3toDARM_LVLN_LPON_FullLock.xml (Y) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-26/ 2015-08-26_H1SUSETMY_L1toDARM_FullLock.xml 2015-08-26_H1SUSETMY_L2toDARM_FullLock.xml (Z) /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Measurements/FullIFOActuatorTFs/2015-08-26/ 2015-08-26_H1SUSETMX_toDARM_FullLock.xml For the record, even though T1500383 defines an order to take these measurements to minimize time to take these 11 measurements, we deviated from the plan so that we could spend time tuning up the TFs that we needed. As such, we took the ALS DIFF measurement (5) first, then brought the full IFO up, then took (2), (X), and (Y). Sadly, we lost lock from what likely was the consequences of two successive small earthquakes (5.2 and 4.9 in the mid-atlantic ridge). As such, we didn't get (Z) until we re-locked the IFO about an hour later. Once we got (Z), we intentionally broke the lock again to get (6) through (10). Because the IFO *may* have had a different optical gain between the first lock stretch where we got all of the Y arm measurements, and the other lock stretch when we got (Z) which is used to propogate the absolute calibrations from the FSM and ALS DIFF methods, there *may* be a systematic discrepancy between those two methods and the PCAL method, but we'll just have to wait for the analysis to find out. And we'll compare against another measurement suite that will be taken on this coming Friday.
Quiet shift. Calibration and commissioning all evening. UTC (Pacific) 23:05 (16:05) Daniel S. to CER 23:15 (16:15) Daniel S. back 23:44 (16:44) Sheila clearing CDS diagnostic overflow counters, adding code to guardian to do so at each lock loss 00:50 (17:50) Kiwamu taking the IFO down 03:27 (20:27) Kiwamu asked me to lock the IFO, it did so by itself 03:50 (20:50) Jenne and I add a stage of whitening to the OMC DCPD 05:03 (22:03) Sheila taking the IFO down and then to LOCK_DRMI_1F
See attached.
the new ubuntu frame writer we started this afternoon filled its local disk system with commissioning plus science frames in six hours. I have reconfigured it to only write science frames, deleted the old frames and restarted it. It will now take 18hours to fill its disk. So for the new DAQ medm, only the science frame comparison with fw0 is now valid.
As per Jeff's request.
Since the last L2/L3 crossover measurement, we have moved the 200 Hz digital pole in DARM to 1 kHz. This changes the shape of the crossover slightly above 50 Hz.


I have created a DTT template that makes it easier to decide when it's okay to turn on more OMC DCPD whitening.
Evan wrote an alog some time ago about the new OMC DCPD whitening on/off guardian states (alog 20578), and Cheryl and Evan made some notes on when it's okay to go to these new states (alog 20787).
As of right now, the guardian will automatically turn on one stage of whitening, but we get better high frequency noise performance if we add a second stage. However, if some mode (eg. a violin mode) is rung up, then we can't add the second stage of whitening without being in danger of saturating the ADC. So. The new DTT template should help decide when it's okay to add the second stage.
The template is /ligo/home/ops/Templates/dtt/DCPD_saturation_check.xml (screenshot below). The template should be run after we have arrived at NOMINAL_LOW_NOISE for the main lock sequence. If the dashed RMS lines are below the green horizontal line, it's okay to add the second stage of whitening.
To engage the second stage of DCPD whitening:
Open the full list of guardian states for the OMC_LOCK guardian, and select "ADD_WHITENING". It will take a minute or two, and automatically return to the nominal "READY_FOR_HANDOFF" state.
could you explain the math & logic a little bit more?
I would have thought that an RMS of 3000 cts is as high as we want to go. Increasing the RMS by a factor of 10 would make it so that its always saturating = not OK. Or isn't this IN1 channel the real ADC input?
Yes, 3000 ct rms = 8500 ct pkpk = too many counts to add a second stage of whitening.
We run with about 10 mA dc on each DCPD, which shows up as 13000 ct or so of dc on the IN1 channels. That means we have something like 19000 ct of headroom before the ADCs saturate on the high side (+32 kct). Assuming the ac fuzz is symmetric about the mean, saturation will certainly occur if the ac is greater than 38000 ct pkpk with two stages of whtening, or 3800 ct pkpk with one stage of whitening.
That's why the criterion I've been using for turning on a second stage of whtening is to look at the IN1 channels and verify that the ac is less than 3000 ct pkpk, or 1000 ct rms when there is only one stage of whitening on. If we find the DCPDs saturating too often with two stages, we should be even more restrictive.
Added a gain change for ASAIR_B_RF18, ASAIR_B_RF90, ASAIR_B_LF and ASAIR_A_LF when the AS port beam diverted closes (it has 10% residual through beam).
# Set the ASAIR PD gains for BDIV open
ezca['LSC-ASAIR_B_RF18_I_GAIN'] = 18
ezca['LSC-ASAIR_B_RF18_Q_GAIN'] = 18
ezca['LSC-ASAIR_B_RF90_I_GAIN'] = 18
ezca['LSC-ASAIR_B_RF90_Q_GAIN'] = 18
ezca['LSC-ASAIR_A_LF_GAIN'] = 11
ezca['LSC-ASAIR_B_LF_GAIN'] = 11
Curiously, the DC gains scale differently than the RF channels...
More Whitening Filter changes to reduce the pole frequency and thus high frequency distortion (LHO alog 20393).
CAL-CS_DARM_DELTAL_RESIDUAL: zpk ([1 1],[500,500],1)
changed to zpk ([0.1 0.1],[100,100],1)
CAL-DARM_ERR zpk ([10 10],[100,1000],1)
changed to zpk ([1 1],[200,200],1)
CAL-DARM_CTRL : zpk ([5 5],[500,500],1)
changed to zpk ([1 1],[200,200],1)
Attached plot shows the signal with old filter and the new filter for comparison.
- Set the nominal ODC threshold values for all SUS, LSC, ASC, TCS and OMC during the morning lock. - Updated SDF with those settings. - Note that TCS got disconnected yesterday, so ODC_MASTER settings related to TCS are not SDF'ed yet. - Updated all ODC screens to show all relevant bits. - Added the intent bit button to the ODC master screen (it is also available on the Guardian screen). With that almost all indicator are green in full lock. The exceptions are: - ADC saturation: - Unfortunately many models have an ADC channel that by design saturates, i.e. the CDS bit delivered to ODC for those models is always lo. - On top of that some models (like e.g. ASC) report a saturation, even though n channel seems to be saturation. Dave Barker has noticed that before... - DAC saturation: TCS currently reports a DAC saturation - not sure why. - LSC and ASC report a incorrect parity bit (that's an ODC internal issue)
To show the calibration group how to analyze duotone, I looked at the IOP channel for the duotone input of the first LSC ADC card (the same card that is used for OMC DCPD).
Nothing is automated yet (that's for Sudarshan), I just used dtt to access 64kHz IOP channel, took 2 sec of time series, exported it to text, and used matlab to analyze.
According to my script the delay is 7.3us (i.e. the duotone second boundary is 7.3us behind the digital world second boundary).
The medm screen for each IOP has a simpler duotone timing monitor and it is reporting 5us delay instead of 7 (see attached). I don't know where that descrepancy comes from. I know that the number the medm screen is reporting comes from a simple zero-crossing calculation at around the second boundary, but even when you look at the zero-crossing, it looks more like 7us than 5 (second attachment).
Tomorrow we'll do the loopback duotone test for pcal and ETM SUS.
Evan Stefan Daniel
The second EOM driver was installed in the CER using the 9MHz control and readback channels. The first attached plot shows the DAQ readback signals. Both drivers show the similar noise levels for the in-loop and out-of-loop sensors. They are also coherent with each other as well as ASC-AS_C! The in-loop noise is clearly below which would indicate that the signal is suppressed to the sensor noise. The measured out-of-loop noise level is also a factor of 4 higher than the setup in the shop.
The second plot shows the same traces but this time the ifr is feeding the EOM driver in the CER. As expected its out-of-loop noise level is now consistent with measurements in the shop and no longer coherent with the unit in the PSL.
We were starting to suspect that we are looking at down-converted out-of-band noise...
Using a network analyzer, we took the following measurements:
The first four of these are shown in the attached plot [the OCXO has been multiplied by 5 in frequency for the sake of comparison]. The message is that the 45.5 MHz in the IFO distribution system has huge, broad wings out to 2 MHz away from the carrier. These are not seen on the IFR, the harmonic generator on the bench, or the 9.1 MHz in the distribution system.
Although the EOM driver still works to suppress some of the RFAM below 50 kHz, the broad wings still contribute significantly to the rms; most of it is accumulated above 200 kHz offset from the carrier. This is shown in the second attachment.
I looked again at some rf spectra in the CER.
These peaks appear on every output of the harmonic generator, even when it is not driving any distribution amplifiers (just a network analyzer).
These peaks also appear even when the harmonic generator is driven by +12 dBm of 9.1 MHz from an IFR (not from the OCXO + distribution amplifier).
This suggests we should focus on the harmonic generator or its power supply.
Although the error reporting is not detailed enough yet on the production server to provide the channel name and value that caused an error upon attempting to insert it into the MySQL database, it is on the test system. The following channels and values caused errors on the test system: Jul 11 16:59:40 H1:OMC-READOUT_ERR_GAIN: -nan Aug 4 07:54:43 H1:SYS-MOTION_C_PICO_F_MOTOR_1_NAME: 'xF3x01' Aug 8 12:25:47 H1:OMC-READOUT_ERR_GAIN: -nan
This is nice, it gives us a sense of how often the calculations for the handoff to DC readout fail. Answer: about once a month.
We should have the OMC guardian check that the calculated value for OMC_READOUT_ERR gain is sensible before writing it to the epics channel.
Maybe more than that. There have been times when the test server has not been running and so did not catch the error when the production server stopped. I think maybe twice while I was on vacation Aug. 8 - 20.
After some email communication with Keith Thorne and Elli, I've added limits at 32,500 to the channels L1:TCS-ITMX_CO2_CHILLER_OUT_GAIN_OUT and its y-arm sibling. This has also been done at LLO.
These channels have a static output on them, and are used to set the chiller temperature for the TCS CO2 lasers. The value is not changed, and will not be at all affected by the limit being put in place.
Patrick, Sheila, Jenne, Eric For the first part of the test, we injected our fiducial CBC waveform (same one used in ER7) and tried raising the LIMIT value on the hardware injection block in order to address saturation problems observed in ER7. During ER7, the LIMIT was 200. We raised it to 400. The first injection did not go through: 1124601535 1 1.000000 cbctest_1117582888_ intent bit off, injection canceled Patrick, Sheila, and Jenne tried to turn on the intent bit, but there was some sort of problem, which will be alog'ged separately. As a temporary work-around, we turned off the tinj intent-bit check and injected again: 1124602724 1 1.000000 cbctest_1117582888_ successful Patrick determined that the injection produced a maximum |amplitude| of 15 counts coming out of the injection block, which seemed to indicate that the original LIMIT value of 200 was sufficient. However, an alarm went off to indicate that there was saturation at ETMY. Thus, the saturation problem cannot be solved by tinkering with the INJ block in MEDM. Rather, the problem is occurring downstream on the ETM actuators. We request that Jeff K, Adam M, et al. look into options for avoiding saturation at the ETMs. Next we tried a blind injection using the new blind injection code. The blind injection code does not log injections in EPICS so they are not automatically picked up in the segment database. 1124603111 1 1.000000 cbctest_1117582888_ successful The blind injection was clearly visible. The ETM saturation warning went off again. The injection was logged correctly in the blind injection blindinj_H1.log: current time = 1124603049... Attempting: awgstream H1:CAL-INJ_BLIND_EXC 16384 /ligo/home/eric.thrane/O1/Hardw areInjection/Details/Inspiral/H1/cbctest_1117582888_H1.out 1 1124603111 Injection successful. All of these injections were carried out with scale factor = 1; (that's the 1.000000). The injection file, described in a comment below, is a 1.4 on 1.4 BNS, optimal orientation, at D=45 Mpc. It is the same waveform used in previous ER tests.
It looks like the injection actually does hit the 400 count limit (plot 1). It saturates right at the end when the injection chirps up to high frequency. There's some kind of ringing as well (plot 2). From the spectrogram (plot 3) and the zoom (plot 4) this looks like a feature at just above 300 Hz. I thought it might be a notch for the PCal line, but that's 331.9 Hz. So someone will have to check the inverse actuation filter and see what's happening at that frequency. It's possible to see the overflow from the first injection in the ETMY L3 MASTER channel (plot 5). It happens at -131072 counts, and the injection is trying to push it past -200000. The blind injection caused an overflow as well, but since this channel is only recorded at 2048 Hz, it looks like it falls short of overflow (plot 6). There's a faster readback whose name escapes me at the moment. Unless the blind injection is made a factor of about 10 smaller, or rolled off at high frequency, it will be trivial to detect it by looking at the drive to the ETM.
FYI, the injected waveform was fiducial waveform from ER7: https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=16125 It's a 1.4-1.4 BNS at 45 Mpc, optimal orientation.
There are a couple of things to watch out for when performing CBC hardware injections, based on iLIGO experience:
For the ER7 injection we used an SEOBNRv2 waveform that has a ringdown at the end, hoping that this turn off would not trigger an impulse. However, for BNS masses, the turn off and ringdown is pretty sharp. I've asked Chris check that there are no "whooper" effects with the SEOBNRv2 waveform, but we haven't had chance to do this yet. For a SpinTaylorT4 waveform (the other waveform CBC wants to inject), there will definitely be a step, so this needs to be checked and rolled off carefully.
One other comment on the test: what scaling in awgstream did you use? That waveform looks monstously loud (eyeball SNR > 20). That's much louder than would be useful for a blind injections, but good for helping us find whooper effects.
Duncan, the scale factor is 1.
Just for completeness, because I didn't see it posted, here's an Omega scan of the injections in h(t). The first is the non-blind injection, the second is the blind injection. I think the glitch ten seconds after the blind injection is unrelated. I thought it might be a filter turning off or being reset, but it's not on a GPS second (it's at 1124603210.28). It does cause an overflow of the ETMY ESD DAC.
I verified that the blind injection was correctly recorded in the raw frame file.