You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Verified in the network tab that historical requests were being issued with the correct bounds. Right now a bug in Yamcs prevents historical data from being returned.
Was able to add analog aggregate to the bargraph, and change bounds in fixed/local clock modes. No loss of data was observed. In local clock mode, bars updated correctly as new telemetry streamed in.
Summary
Changing time conductor in fixed or local clock mode does not update the graph with new data.
Expected vs Current Behavior
Bar Graph should be updated to show relevant data to the time conductor.
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: