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

Histogram of prediction score does not correspond to the sliders #1211

Closed
dcfidalgo opened this issue Mar 1, 2022 · 1 comment · Fixed by #1261
Closed

Histogram of prediction score does not correspond to the sliders #1211

dcfidalgo opened this issue Mar 1, 2022 · 1 comment · Fixed by #1261
Labels
type: bug Indicates an unexpected problem or unintended behavior
Projects

Comments

@dcfidalgo
Copy link
Contributor

Describe the bug
In the web app for a text classification dataset, the histogram of the prediction score filter does not correspond to the sliders.
This is a bit confusing when trying to adjust the sliders.

To Reproduce
Do the first tutorial, try to use the slider to find predictions with low scores.

Expected behavior
The histogram should be aligned with the sliders.

Screenshots
Screenshot from 2022-03-01 11-47-14

In the screenshot, the x-axis of the histogram starts at 50%, but the sliders start at 0%

Environment (please complete the following information):

  • OS [e.g. iOS]: Ubuntu
  • Browser [e.g. chrome, safari]: Firefox
  • Rubrix Version [e.g. 0.10.0]: master
  • ElasticSearch Version [e.g. 7.10.2]: 7.10.2
  • Docker Image (optional) [e.g. rubrix:v0.10.0]:
@dcfidalgo dcfidalgo added the type: bug Indicates an unexpected problem or unintended behavior label Mar 1, 2022
@dcfidalgo dcfidalgo added this to Backlog in Release via automation Mar 1, 2022
@dcfidalgo dcfidalgo added the app label Mar 1, 2022
@dcfidalgo
Copy link
Contributor Author

@frascuchon @leiyre

@frascuchon frascuchon moved this from Backlog to Planified in Release Mar 2, 2022
frascuchon pushed a commit that referenced this issue Mar 15, 2022
frascuchon pushed a commit that referenced this issue Mar 15, 2022
frascuchon pushed a commit that referenced this issue Mar 15, 2022
@frascuchon frascuchon moved this from Planified to In progress in Release Mar 16, 2022
frascuchon pushed a commit that referenced this issue Mar 16, 2022
Release automation moved this from In progress to Ready to DEV QA Mar 16, 2022
frascuchon pushed a commit that referenced this issue Mar 16, 2022
Using the fixed range [0-1] for score filter visualization.

Closes #1211
@frascuchon frascuchon moved this from Ready to DEV QA to Ready to Release QA in Release Mar 25, 2022
frascuchon pushed a commit that referenced this issue Mar 25, 2022
Using the fixed range [0-1] for score filter visualization.

Closes #1211

(cherry picked from commit 093f78b)
frascuchon pushed a commit that referenced this issue Mar 25, 2022
Using the fixed range [0-1] for score filter visualization.

Closes #1211

(cherry picked from commit 093f78b)
@frascuchon frascuchon moved this from Ready to Release QA to Approved Release QA in Release Mar 28, 2022
frascuchon pushed a commit that referenced this issue Mar 28, 2022
Using the fixed range [0-1] for score filter visualization.

Closes #1211

(cherry picked from commit 093f78b)
frascuchon pushed a commit that referenced this issue Mar 28, 2022
Using the fixed range [0-1] for score filter visualization.

Closes #1211

(cherry picked from commit 093f78b)
frascuchon pushed a commit that referenced this issue Mar 30, 2022
Using the fixed range [0-1] for score filter visualization.

Closes #1211

(cherry picked from commit 093f78b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Indicates an unexpected problem or unintended behavior
Projects
No open projects
Release
Approved Release QA
Development

Successfully merging a pull request may close this issue.

1 participant