Four burst signals have been injected into H1 since the new inverse actuation filter was installed Sunday evening (Timeline of CAL-CS Calibration Filter Updates), with different waveforms:
GPS 1126270500  -  White noise burst, frequency 125 Hz, bandwidth 150 Hz
GPS 1126280500  -  White noise burst, frequency 300 Hz, bandwidth 350 Hz
GPS 1126300500  -  Sine-gaussian, frequency 20.82 Hz, Q=7.32
GPS 1126310500  -  Sine-gaussian, frequency 413.0 Hz, Q=85.1

The low-frequency, low-Q sine-gaussian offers the clearest check of the calibration amplitude and phase among these signals.  (It would be better to use detchar injections, i.e. a set of sine-gaussians at a range of frequencies, as was done during ER7, but we have not performed any detchar injections during ER8 yet.)  I used a matlab script (attached) to plot the intended strain waveform (the file produced by Chris P. and read by tinj to inject the signal) and the H1:GDS-CALIB_STRAIN channel from the hoft frames in the archive at Caltech.  Both have been bandpass filtered bidirectionally with 'filtfilt' around the frequency of interest.  I also did a crude matched filter, stepping the intended strain waveform by integer samples and considering both upright and inverted overlaps with the data.  As you can see from the plot, the signal that came through in the H1:GDS-CALIB_STRAIN channel is consistent with being *inverted* relative to the intended strain signal.  That was also the case in ER7, but we thought the recent calibration work and a careful look at sign conventions would have resolved that.

Is there any possibility that the GDS calibration process running on Monday, producting H1:GDS-CALIB_STRAIN, had not yet been updated with the final resolution of sign convention?