The measurements on H2 SUS FMY begun last night completed but with data gathered from a tripped watchdog state on FMY M1.  The script to collect the tfs calls upon a function to generate the time-series for the excitations.  This function also monitors the watchdog state of whatever system it is actuating upon.  When a watchdog is triggered, the script automatically resets the Epics channel "H2:SUS-FMY_M1_WD_RSET" to reset the watchdog state.  The attached image shows this script may have been a bit trigger-happy with the "*RSET" button during last night's measurements.  The "H2:SUS-FMY_M1_WDMON_CURRENTTRIG","H2:SUS-FMY_M1_WDMON_STATE", and "H2:SUS-FMY_M1_WDMON_FIRSTTRIG" values were all at either "0" or "1" during a "clean" period of nearly three hours.  The attached image is a dataviewer plot of the full data.  The "H2:SUS-FMY_M1_WD_RSET" channel was oscillating between "0" and "1" at least eleven times during this (supposedly) "clean" period.  This is very concerning as our watchdogs are not correctly displaying our watchdog levels.  Or this could be an issue with the function monitoring the wrong channel or channel value.  Investigations are ensuing, but this is highly suspicious and inexplainable as of now.