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

Button to boost confidence to 1.0 #1209

Merged
merged 1 commit into from
Mar 29, 2022
Merged

Button to boost confidence to 1.0 #1209

merged 1 commit into from
Mar 29, 2022

Conversation

subdavis
Copy link
Contributor

@subdavis subdavis commented Mar 29, 2022

fixes #1202

Screenshot from 2022-03-29 13-27-24

This is the easy/obvious solution I could add quickly to give the user something that worked. There may be a more ergonomic version that accepts the current top confidence as correct from the track list, but I didn't do that because there's no way to show the user feedback that this has done something, and adding visual feedback will require a bit more thought.

We'll need a way to display on a track list item where confidence == 1 or not, and then a button or hotkey or something to boost it to 1. This is related to #614.

I think this PR is a minimal fix that will give users something to provide feedback on.

@subdavis subdavis changed the title Button to boost confidence Button to boost confidence to 1.0 Mar 29, 2022
Copy link
Collaborator

@BryonLewis BryonLewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small (probably insignificant) question, but otherwise it seems to do what is needed and we know that in the future we may need some shortcuts to make this more useful.

{{ pair[1].toFixed(4) }}
</v-col>
<v-col
v-if="pair[1] !== 1 && !disabled"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wondering if this should be shown if the pair length > 1 or if the pair[1] !== 1. I know the idea of the confidencePairs means this should never be 1.0 while also having other pairs but if anyone reformatted their CSV to have a 1.0 pair and other pairs they wouldn't be able to use this quick tool to assign a true pair. It's a small thing and probably don't worry about it too much.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it depends on what you care about. If a pair already has a value of 1.0 then maybe it doesn't matter. Likewise, if there's only one pair, but it's 0.25, maybe someone would want to make it 1.0.

We can always change it later if someone has a preference.

@subdavis subdavis merged commit 3627d1f into main Mar 29, 2022
@subdavis subdavis deleted the boost-confidence branch March 29, 2022 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Option to confirm a classification as correct
2 participants