I was trying to use the fast ODC channels (e.g. H1:SUS-ETMY_ODC_CHANNEL_OUT_DQ) to track down ETMY saturation causes, but ran into a number of bugs in our data access tools that made it impossible:

1) dataviewer can play the trend data of integer ODC channels, but not the full data.

2) both dtt (diaggui) and lockloss (pydv) can't access integer ODC channels

3) using NDS2, the ODC channel is down-sampled to 256 Hz, making it useless for my purpose.
(why do we do that? That channel compresses either way, and takes the same amount of disk space)

4) dtt (diaggui) can access that channel, but only with the "now" setting, and

  IT RETURNS DATA WITH A TIME STAMP IN THE FUTURE!!!!

(The attached plot has a UTC clock in the terminal, and dtt's repored time stamp...)


sigh... I give up for today.