Closed RCarvalhoNASA closed 7 years ago
The update rate is based on the new hidden time conductor which ticks at 60hz.
The clock that has been configured is actually based on last ~30 minutes local time, which doesn't match the timestamps of the telemetry we are playing back, so the plot shows nothing.
Configuration issues with new APIs and WARP that we'll have to address.
The clock that has been configured is actually based on last ~30 minutes local time, which doesn't match the timestamps of the telemetry we are playing back, so the plot shows nothing.
Oh, LOL. That actually makes total sense. Also explains why nothing in tables. Gosssssssh.
We need a LAD or some other server-side clock source in WARP, ideally both.
This is based on the WARP deploy using an invalid clock and timeconductor setting, closing this and tracking as: https://developer.nasa.gov/ResourceProspector/warp/issues/286
Testathon 2017/4/20 The X axis values in the plots are continually updating in realtime, showing every millisecond. Wouldn't it make more sense for them to update just as new data comes in, or at least at a lower frequency?