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

[Plots] Zooming out and in can cause the plot to display incorrectly #7926

Open
3 of 7 tasks
jvigliotta opened this issue Nov 12, 2024 · 0 comments · May be fixed by #7939
Open
3 of 7 tasks

[Plots] Zooming out and in can cause the plot to display incorrectly #7926

jvigliotta opened this issue Nov 12, 2024 · 0 comments · May be fixed by #7939

Comments

@jvigliotta
Copy link
Contributor

jvigliotta commented Nov 12, 2024

Summary

Occasionally, plots may be stuck in a state that represents a zoomed out level than the current zoom level for telemetry binning. This occurs after zooming in from large time ranges over several subsequent zoom ins. Once a plot has entered this zoomed-out-binning, it may not be removed from this state. Resizing the window or opening a large view of the plot does not fix it. Opening the plot in a new tab does fix it after synchronizing the time conductor, but is obviously not ideal behavior. The end result is that instead of the natural flow of telemetry, vertical lines representing the bins of the zoomed out plot are plotted instead of the better telemetry.

Expected vs Current Behavior

Zooming in and out should display the telemetry in the best way possible.

Steps to Reproduce

  1. Load a plot somewhat zoomed out to force it to use minmax.
  2. Zoom into an area of the plot. Note: The bug may appear at this point, but it's inconsistent.

Environment

  • Open MCT Version:
  • Deployment Type:
  • OS:
  • Browser:

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

Good State:
plot-good-state

Bad State:
plot-bad-state

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants