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

Think about a step to understand where errors are made, maybe after squeeze #123

Open
SebChw opened this issue Oct 10, 2023 · 3 comments
Open
Assignees
Labels

Comments

@SebChw
Copy link
Owner

SebChw commented Oct 10, 2023

No description provided.

@kordc kordc added the v0.3 label Oct 11, 2023
@kordc
Copy link
Collaborator

kordc commented Nov 19, 2023

@SebChw could you elaborate more on this? I don't think I understand this issue

@SebChw
Copy link
Owner Author

SebChw commented Nov 19, 2023

Yes:

I imagine it like this we are still unhappy with our results and we are thinking on what causes bad results.

Do we always mess up between 2 classes? Are some particular examples harder?

@trebacz626 trebacz626 self-assigned this Nov 19, 2023
@trebacz626
Copy link
Collaborator

Shal we add this to mnist tutorail and craete confusion matrix and save examples with highest loss?

@kordc kordc added v0.4 and removed v0.3 labels Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants