Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bar Graph does not update when time conductor value changes #5456

Closed
1 of 7 tasks
shefalijoshi opened this issue Jul 7, 2022 · 3 comments
Closed
1 of 7 tasks

Bar Graph does not update when time conductor value changes #5456

shefalijoshi opened this issue Jul 7, 2022 · 3 comments

Comments

@shefalijoshi
Copy link
Contributor

shefalijoshi commented Jul 7, 2022

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

  1. Drag the analog aggregate to a bar graph
  2. Expect that some bars are displayed (this is currently not happening)
  3. Change time conductor start/end
  4. Expect that some bars are displayed with new data.

Environment

  • Open MCT Version: release/2.0.5
  • Deployment Type: VIPER testathon
  • OS: all
  • Browser: all

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?
  • Does this have an impact on Performance?

Additional Information

@akhenry
Copy link
Contributor

akhenry commented Jul 12, 2022

Note that yamcs/yamcs#685 will make it difficult to verify this with real data.

@akhenry
Copy link
Contributor

akhenry commented Jul 12, 2022

Verified fixed

  • Switched to fixed mode
  • Changed time conductor bounds
  • 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.

@ozyx
Copy link
Contributor

ozyx commented Jul 12, 2022

Verified 7/12/22

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.

@unlikelyzero unlikelyzero added this to the Sprint:2.0.7 milestone Jul 17, 2022
@unlikelyzero unlikelyzero added the needs:e2e Needs an e2e test label Jul 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants