B. Weaver, J. Oberling
After this morning's PSL trip there was a 0.5W increase in IMC-PWR_IN, observed ~15 minutes after reaching NOMINAL_LOW_NOISE. We started digging in the Guardian code and rediscoverd that the ISS diffracted power gets adjusted by a software PID loop located in the IMC_LOCK guardian; this adjustment is done via changing the ISS 2nd loop reference signal. At the start of a lock stretch this PID loop is necessary to keep the ISS diffracted power around the predetermined nominal value of 8%. However today we witnessed that when the diffracted power trended towards the upper threshold (set in the IMC_LOCK guardian code) of 10%, the IMC_LOCK turned on the PID loop, thus increasing the measured IMC-PWR_IN by ~0.5W.
Looking back 16 days we discovered 2 more cases of the IMC_LOCK guardian turning on the ISS PID loop during a NOMINAL_LOW_NOISE (and observing) lock stretch. Attached is the 16 day trend and the 2 examples. The 2nd example was 30 hours into last week's 46 hour lock stretch. Also note, in the 16 day trend, the continued power discrepancy from lock to lock.
Looking at the 16 day trend, by eye it seems the ISS diffracted power is hugging the upper threshold of 10% more often then not, hovering around 9%. This might be normal acceptable behavior, however we were surprised to see that a PID loop was increasing power in the middle of an observing lock. Will follow up with commissioners.
What do the in- and out-of-loop signals for the outer loop look like during these events? (I.e., SUM14 and SUM58.)
B. Weaver, J. Kissel, Not sure what Evan wants with the "SUM14" and "SUM58" channels, so I found what channels are stored in the frames for the ISS, and used my vague knowledge of how the ISS SECOND LOOP works, and chose H1:PSL-ISS_SECONDLOOP_SUM14_REL_OUT_DQ H1:PSL-ISS_SECONDLOOP_SUM58_REL_OUT_DQ and reproduced Betsy's plots with trends of those channels in addition to the original channels. I'll leave it to Evan to interpret the results, 'cause we don't know how. Let us know if you need anything different, Evan (or on a different scale, or whatever).
Fil came to let me know that the alarm at Hanford site is going off. They called earlier that there will be an alert system testing between 12:30-13:30.
I switched to Observing a bit at 19:49 after Praxxair hadn't moved for a really long time. I went back to comissioning then the truck took off from Mid Y at 19:51. And back to Observing when it went back to Rt. 10.
The PSL AOM diffracted power was dropping but now stable within desired range (8%). Peter went to turn on the laser Watchdog.
Downloaded Dunca's M.'s new ODC overview screens. They are now linked to the sitemap. The old one are still available. cds/h1/medm/SITEMAP.adl is in the svn - revision 11744 For what it's worth - I also noticed that some ODC settings for IM's and HTTS's are not up to date.
PSL tripped.
Sitting in the control room I heard something about a lock loss. I looked at the monitor that displays various cavity transmissions and noticed that the laser had tripped. I went into the diode room. The Beckhoff computer indicated that the laser switched off due to the power watchdog being kicked. The power watchdog performed as it should. However we should make it routine to reset the power watchdog every maintenance day. Something we have mentioned but perhaps were not as diligent about it as we should be. All the PSL related servos were up by the time I returned to the control room. Attached is a plot of the laser power since the last time (I believe) the watchdog was reset back on Sept. 1st.
Locked again at NOMINAL_LOW_NOISE. RF45 MODE reduced to 22.2 dB after it was reset to 23.2 by Guardian after the lockloss. Currently not Observing due to Praxxair (a really big truck) on site.
When the laser was restarted the main screen indicated that the laser power was 34.7 W. Instead of turning on the watchdog there and then I decided to wait and let the power stabilise out before setting the dog loose. Turned on the watchdog at ~13:05 UTC, the power indicated on the screen was 34.1 W.
re Int Issue 1127, WP 5521.
Have modified the WHAM5 Top Level Model to terminate the output of the ADC and ground the input of the Coil Driver Corner2 Voltage monitors.
This will eliminate the false Rogue Excitation WD Trips of which this platform has been suffering. BTL identified the cause finding the bad monitor output.
This is temporary until we swap out the driver and look for a cause in the monitor circuit.
On Tuesday 29 Sept, the model will be installed and the FE restarted after taking the platform down to safe or offline.
After restart, the SDF will have to be repointed to the OBSERVE.snap
Attached is an image of the modified model area: the two don't look like the others.
Modified model commited to svn rev 11742.
The glitch rate hasn't been doing very well in the past hour (since I relocked the ifo) so I dropped the intent bit and reduced the modulation index (17:37 UTC) by 1 dB. The H1:LSC-MOD_RF45_AM_RFSET value is now 22.2 instead of 23.2. I went back to observing with this configuration and see if it helps with the glitch rate. So far the DMT Omega has been looking much cleaner in the past 10 minutes.
Lockloss after 60 hours locking at NOMINAL LOW NOISE (beat the old record of 46 hours from three days ago). There's a 5.4M earthquake in Argentina at a depth of 198.5km happened right around the time. Terramon suggested this earthquake shouldn't drop us out of lock but LLO has also dropped lock at the same time. USGS reported no bigger earthquake.
Back to Observing 16:27 UTC.
TITLE: 09/28 [DAY Shift]: 15:00-23:00 UTC (08:00-16:00 PDT), all times posted in UTC
STATE Of H1: Observing at ~64Mpc. The ifo has been locked for 58 HOURS!
OUTGOING OPERATOR: TJ
QUICK SUMMARY: Nominal seismic activity in earthquake band. Rising in seismic activity in anthropogenic band. RF45 behaving okay. Wind below 5 mph. No broadband loud glitches in the past half an hour.
TITLE: 09/28 [Owl Shift]: 07:00-15:00 UTC (00:00-08:00 PDT), all times posted in UTC
STATE Of H1: Observing, ~70 MPc
SHIFT SUMMARY: Really quiet first half, then the RF45 Noise would intermittently appear. I would have to adjust H1:LSC-MOD_RF45_AM_RFSET down to fix it. Definitely seems to be getting worse.
INCOMING OPERATOR: Nutsinee
LOG:
The RF Noise isn't quite as bad this time, for the past 10min or so it will breifly get noisy, relax for min, then get noisy againa and saturate ETMY.
LLO is down right now so I will take that opportunity to try and fine tune the RF45Set again.
Observing
H1:LSC-MOD_RF45_AM_RFSET == 21.2
The Coherence below 2Hz in H1:LSC-DARM_IN1_DQ is almost 0 with the RFSET this low, and AS90 is at about 400.
The RF Noise is back again, I will try to tweak H1:LSC-MOD_RF45_AM_RFSET again.
Back to Observing.
Tried to find a good balance of adjusting the RF Set value to bring the noise down, and keeping AS90 up. Ended up with:
Back to just above 70Mpc.
Executive summary:
A matlab file (37 MB) containing the averaged inverse-noise-weighted spectrum from the first week can be found here: https://ldas-jobs.ligo.caltech.edu/~keithr/spectra/O1/H1_O1_week1_0-2000_Hz.mat Because of the way multiple epochs are handled, the matlab variable structure is non-obvious. Here is how to plot the full spectrum after loading the file: semilogy(freqcommon,amppsdwt{1,1})
Keith has found: "There is a sporadic comb-on-comb with 0.088425-Hz fine spacing that appears with limited spans in three places near harmonics of 77, 154 and 231 Hz (ambiguity in precise fundamental frequency)" Using the coherence tool, we have seen coherence between h(t) and a number of auxiliary channels that shows this comb around 77 Hz. Seems to be around the input optics, in channels: H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ H1_SUS-ITMY_L1_WIT_L_DQ H1:SUS-BS_M1_DAMP_L_IN1_DQ H1_SUS-ITMY_L1_WIT_P_DQ H1:SUS-BS_M1_DAMP_T_IN1_DQ H1_SUS-ITMY_L1_WIT_Y_DQ H1:SUS-BS_M1_DAMP_V_IN1_DQ H1_SUS-ITMY_L2_WIT_L_DQ H1:SUS-BS_M1_DAMP_Y_IN1_DQ H1_SUS-ITMY_L2_WIT_Y_DQ See the attached figures. Nelson, Soren Schlassa, Nathaniel Strauss, Michael Coughlin, Eric Coughlin, Pat Meyers
The structure at 76.4Hz Nelson listed some channels for above shows up in at least 50 other channels. Greatest coherence is consistently at 76.766 Hz, second greatest is (mostly) consistently at 76.854Hz. Spacing between the two combs is about 0.0013Hz. The epicenter seems to be the INPUTOPTICS/the SUS-BS and SUS-ITM* channels, like Nelson said (see below for fuller list). The plots above are pretty typical, but I have plots for all channels listed and can post any more that are useful. Most or all channels showing the comb with max coherence greater than 0.1 are listed below. Max coherences over 0.2 are marked below as strong, and max coherences under 0.15 as weak. Those marked strongest are around 0.22. I haven't included anything of max coherence <0.1 but I'm sure there are many. H1:ASC-AS_A_RF36_I_PIT_OUT_DQ (weak) H1:ASC-AS_A_RF36_I_YAW_OUT_DQ H1:ASC-AS_A_RF36_Q_PIT_OUT_DQ H1:ASC-AS_A_RF36_Q_YAW_OUT_DQ (weak) H1:ASC-AS_B_RF36_I_YAW_OUT_DQ H1:ASC-AS_B_RF36_Q_YAW_OUT_DQ (strong) H1:ISI-BS_ST2_BLND_RZ_GS13_CUR_IN1_DQ (strong) H1:ISI-BS_ST2_BLND_Z_GS13_CUR_IN1_DQ (strong) H1:ISI-HAM2_BLND_GS13RZ_IN1_DQ H1:ISI-HAM2_BLND_GS13Z_IN1_DQ H1:ISI-HAM3_BLND_GS13Z_IN1_DQ (strong) H1:ISI-HAM5_BLND_GS13RZ_IN1_DQ H1:ISI-HAM5_BLND_GS13Z_IN1_DQ H1:ISI-HAM6_BLND_GS13RZ_IN1_DQ H1:ISI-ITMX_ST2_BLND_RX_GS13_CUR_IN1_DQ (weak) H1:ISI-ITMX_ST2_BLND_Z_GS13_CUR_IN1_DQ (strong) H1:ISI-ITMY_ST1_BLND_RZ_T240_CUR_IN1_DQ (weak) H1:ISI-ITMY_ST1_BLND_Y_T240_CUR_IN1_DQ (weak) H1:ISI-ITMY_ST2_BLND_RZ_GS13_CUR_IN1_DQ (strong) H1:ISI-ITMY_ST2_BLND_Z_GS13_CUR_IN1_DQ (strong) H1:LSC-PRCL_IN1_DQ H1:PEM-CS_LOWFMIC_LVEA_VERTEX_DQ (strong) H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ (strongest) H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ (strong) H1:SUS-BS_M1_DAMP_L_IN1_DQ (strongest) H1:SUS-BS_M1_DAMP_T_IN1_DQ (strong) H1:SUS-BS_M1_DAMP_V_IN1_DQ (strong) H1:SUS-BS_M1_DAMP_Y_IN1_DQ (strong) H1:SUS-ITMX_M0_DAMP_R_IN1_DQ (strong) H1:SUS-ITMX_M0_DAMP_V_IN1_DQ (strong) H1:SUS-ITMY_L1_WIT_L_DQ (strong) H1:SUS-ITMY_L1_WIT_P_DQ (strong) H1:SUS-ITMY_L1_WIT_Y_DQ (strong) H1:SUS-ITMY_L2_WIT_L_DQ (strong) H1:SUS-ITMY_L2_WIT_P_DQ (strong) H1:SUS-ITMY_L2_WIT_Y_DQ (strong) H1:SUS-MC1_M3_WIT_L_DQ H1:SUS-MC1_M3_WIT_P_DQ (weak) H1:SUS-MC2_M1_DAMP_L_IN1_DQ H1:SUS-MC2_M1_DAMP_T_IN1_DQ H1:SUS-MC2_M1_DAMP_Y_IN1_DQ H1:SUS-PR2_M1_DAMP_P_IN1_DQ H1:SUS-PR2_M1_DAMP_R_IN1_DQ H1:SUS-PR2_M1_DAMP_V_IN1_DQ H1:SUS-PR2_M3_WIT_L_DQ H1:SUS-PR2_M3_WIT_P_DQ (weak) H1:SUS-PR2_M3_WIT_Y_DQ (weak) H1:SUS-PR3_M1_DAMP_P_IN1_DQ H1:SUS-PR3_M1_DAMP_V_IN1_DQ H1:SUS-PRM_M1_DAMP_L_IN1_DQ (strongest) H1:SUS-PRM_M1_DAMP_T_IN1_DQ H1:SUS-PRM_M1_DAMP_Y_IN1_DQ (strong)
The 99.9989Hz comb Keith found (designated H) appears in 109 channels (list is attached). Coherence is uniformly greatest at the ~500Hz harmonic, with many channels approaching .7 and greater, drops off sharply at the ~600Hz and ~700Hz, and is invisible after 700. (See spreadsheet titled "comb_H_sigcohs_wk1.xslx" for a list of cohering channels by line, with coherence value.) At all harmonics except the ~300Hz, the structure manifests in the signal and the coherences as two lines .001Hz apart, but if I recall correctly .001Hz is the resolution of the frequency series, so it's safer to say that this is a bulge with .001Hz < width < .002Hz. At ~300Hz, almost all the cohering channels with data in that range show a bulge of width about 0.5Hz (see attached "disjoint_plots" for a comparison of typical channels by harmonic). This bulge, and the fact that it appears in all the same channels associated with the rest of the comb, makes me think that the fundamental may be the bulge at ~300Hz and not the line at 99.9989Hz. An interesting feature of the bulge is that in many cases, it has a prominent upward or downward spike at 299.96Hz, which is just the place the line would be if it were there (see "bulge_w_spike.jpg"). More to come re: changes in week 4 data, patterns in cohering channels, and the spike.
We tested a set of waveforms to see if they would saturation the ETMY ESD. Test the 15Hz waveform Previously we have tested a waveform that began at 30Hz, see aLog 21838. It was requested we try it from 15Hz instead of 30Hz. Here are the commands I ran for testing the 15Hz waveform: ezcawrite H1:CAL-INJ_TINJ_TYPE 1 awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 0.1 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 0.25 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 0.5 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/coherenttest1from15hz_1126257408.out 1.0 -d -d >> log3.txt The start times of the injections from the log file (log3.txt): SIStrOpen: Waveform starts at GPS=1127276638, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127276799, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127277026, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127277293, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127277517, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127277840, epoch=0, sample=0 I did not notice any ESD saturations. John's waveforms John V. has also provided 10 waveforms that I tested, see aLog 21964. Cautiously testing the first waveform Here are the command I entered as I slowly scaled up the first waveform's amplitude: awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.2 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.5 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.75 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 0.85 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 1.0 -d -d >> log3.txt The start times for these injections: SIStrOpen: Waveform starts at GPS=1127278105, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127278209, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127278748, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127279093, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127279520, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127279644, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127280123, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127280433, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127281232, epoch=0, sample=0 The injection that began at 1127280433 was near an ETMY alert from the robot voice. The ETMY alert happened a bit after the injection happened. SO I waited, I repeated the same injection, and there was no alert. I did one of these injections with a padding of 10 minutes so if the search groups are going to followup one of these injections in more detail this would be a good choice: awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior0_1126259455.out 1.0 -d -d >> log3.txt # gave this guy a bit of time The start time of this injection is: SIStrOpen: Waveform starts at GPS=1127281956, epoch=0, sample=0 Testing the other nine waveforms Then I tested the remaining 9 waveforms by beginning with a scale factor of 0.3333 and incrementing to 1.0. I did these with little spacing between the injections so I do not think this set is worth the analysis groups following up. However, I think the injections with scale factor 1.0 should be looked at for ESD saturation (I believe Andy has a script for that): awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior1_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior1_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior1_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior2_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior2_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior2_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior3_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior3_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior3_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior4_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior4_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior4_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior5_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior5_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior5_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior6_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior6_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior6_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior7_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior7_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior7_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior8_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior8_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior8_1126259455.out 1.0 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior9_1126259455.out 0.3333 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior9_1126259455.out 0.6666 -d -d >> log3.txt awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 ../H1/posterior9_1126259455.out 1.0 -d -d >> log3.txt The start times of these injections: SIStrOpen: Waveform starts at GPS=1127282013, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282066, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282120, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282173, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282226, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282278, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282326, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282377, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282422, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282476, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282517, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282577, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282631, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282681, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282727, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282770, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282819, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127282964, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283007, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283048, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283089, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283160, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283204, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283245, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283292, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283338, epoch=0, sample=0 SIStrOpen: Waveform starts at GPS=1127283440, epoch=0, sample=0 As I did these injections I had the SUS-ETMY_L3_ESDOUTF_LL_OUT channel open in dataviewer. I did not see any injection go above the 90000 counts. The highest was posterior0*.out which was near 80000 counts.
I am going to follow up the injections I passed to Chris. Assuming the "start time" is the time at the 1st sample of the injection file (and not the 1st non-zero sample) the end times of the increasing amplitude posterior0 injections should be around
The only ETMY overflows during the injection periods were: 1127278436.8 1127280154.9 (also overflowed ETMY L2 and OMC DCPD) 1127282847.5 None were related to the injections.