-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Support Bar Graphs in Open MCT #4177
Comments
Testing instructions:
|
Looks awesome, nice work! Couple issues I found:
|
Testathon 9/20/2021.
|
Testathon 9-20-21: some problems identified
Should we reopen this for needed fixes? |
Think this is @charlesh88's fault, will look into. |
Testathon 9-28-21: Bar Graph Should look like Overlay Plot The series element needs to show the object type icon (line 30 in BarGraphOptions.vue) @shefalijoshi could you add please? For reference, see markup in SeriesForm.vue lines 11 - 20. |
Just pushed a fix for the hidden 0 line issue to #4270 |
@scottbell Please take a look at #4177 (comment) |
Ok, I think I've got the bar graph inspector squared away now: |
@nikhilmandlik @jvigliotta I'm having some problems replicating the issue in Thanks for the help! |
@scottbell When the bar styles are being saved to the domain object via Interestingly, there is also the following (but with an empty name): I suspect we need to convert the ${this.key} to a string when we call mutate |
@scottbell for @nikhilmandlik 's issue, I see the following console error: |
Verified fixed |
Is your feature request related to a problem? Please describe.
Bar Graphs should display bars with range variable names on the X-axis and values on the Y-axis.
Describe the solution you'd like
Bar Graphs should accept aggregate telemetry.
Metadata should be provided that determines which attributes of the telemetry to use for which axisThis will come later as there is yamcs work to do and nobody to do it right now.Additional context
Add any other context or screenshots about the feature request here.
See the following issues that make up this feature:
Resolves #4100
Resolves #4101
Resolves #4178
Resolves #4102
Resolves #4191
Resolves #4192
Resolves #4212
Resolves #4217
The text was updated successfully, but these errors were encountered: