Add guess, inferred components for calibration constants#342
Conversation
…, add toggle between the two for displaying
Added the two separate variables and a toggle to display one or the other (currently gives an error if trying to display the inferred calibration values)
|
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.
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.
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.
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
EZoni
added
ml
EZoni
changed the title
|
I flagged the PR as "[WIP]" because there may be some style issues to fix. For example, I see this on my browser: 
In general I think we should find a way to expand those panels, because there's a lot of unused empty space horizontally, overall on the whole page. |
|
The issue mentioned in #342 (comment) is fixed in #351. |
|
FYI, final look after the latest commits (slightly different than the one in the PR description): 
|
EZoni
changed the title
…#342) Co-authored-by: Edoardo Zoni <ezoni@lbl.gov>
2 participants
Add components to change the uncertainty in alpha and beta in the gui:
