Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Dataset health check renaming & acceptance threshold #214

Open
pcaversaccio opened this issue Jul 2, 2022 · 3 comments
Open

Dataset health check renaming & acceptance threshold #214

pcaversaccio opened this issue Jul 2, 2022 · 3 comments
Assignees
Labels
ai tools 🤖 Issues related to AI tools feature 💥 New feature or request frontend 🖥 Issues related to front-end

Comments

@pcaversaccio
Copy link
Member

User Feedback: It's not clear, for a non-technical person, what to do with the Dataset Health Check results (SNR). At the very least, indicated what a high or low SNR value means. I also would avoid the word "health" but perhaps something like "quality" as the SNR measure is an indicator of the level of noise to actual signal, and hence leads to it's "quality" changing rather than "health" IMO. Maybe also add a threshold above/below which the quality is typically acceptable/unacceptable.

@giaoNguyen70 what are your thoughts on this feedback?

@pcaversaccio pcaversaccio added feature 💥 New feature or request frontend 🖥 Issues related to front-end ai tools 🤖 Issues related to AI tools labels Jul 2, 2022
@AI-Daita
Copy link

AI-Daita commented Jul 4, 2022

Agree for rename: "quality" is better than "health"
Also agree for adding the quartiles (for ex.) for data interpretation (such as, acceptable or outlier).

@locpnh1995
Copy link
Collaborator

@pcaversaccio , Have you have final solution for this issue yet ?

@pcaversaccio
Copy link
Member Author

Ignore this one for that release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ai tools 🤖 Issues related to AI tools feature 💥 New feature or request frontend 🖥 Issues related to front-end
Projects
None yet
Development

No branches or pull requests

3 participants