Brian, Fabrice and I have found that there is an odd discrepancy between the value of the watchdog recorded by the framebuilder and the value recorded by EPICS. The EPICS value reads 4, while the framebuilder value reads 0. These should be reading the same value, since they are both a part of the same filter module (H2:ISI-ITMY_ST1_WDMON_STATE). 

In the attached plot, you can see the discrepancy in the top two charts (all full data). The top left is the DQ channel, which says the watchdog is 0 (??), while the top right is the EPICS channel, which says the watchdog is at 4 (fully tripped). The watchdog C code has no '0' state, so it's odd that this value would be recorded at all when the model is running.

We show that the model is running by showing the GPS time as recorded from the model in the bottom right. The value for the GPS time drops to 0 when the model is killed (1014668665) and comes back when the model is started again (1014668677). 

We also get full data from CPS H1 at the bottom left when the model is restarted. The data from 1014668665-677 in this channel is not 'real' - it is reflections of previous data at 1 second intervals. This can be casually observed by the apparent aliasing effect from 1014668655-70 in what look like dark diagonal stripes. We can see the CPS signal grow when the model starts.