-
Notifications
You must be signed in to change notification settings - Fork 4
Add guess, inferred components for calibration constants #342
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
Conversation
…, add toggle between the two for displaying
dashboard/calibration_manager.py
Outdated
| with html.Div( | ||
| style="display: flex; align-items: center; margin: 20px; justify-content: space-between;" | ||
| ): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remind me/us again on why we wrap everything within a with html.Div():? What does this accomplish specifically? Just trying to understand if it's necessary, optional, if it should be used elsewhere/everywhere where we set up other graphical components, etc. I'm sure I haven't used it consistently, or at all, so far, so I want to make sure I understand why it's here and what it does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can also search the answer online, I'm asking just in case you have the answer ready off the top of your head.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wrapped this in a div so that the alpha and beta sections are separate and they're flexboxes, but looking at it now I can just use a VRow to be more consistent with other parts of the code
|
The issue mentioned in #342 (comment) is fixed in #351. |



Add components to change the uncertainty in alpha and beta in the gui:
