Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
When using an activation function of "Softmax2d" for many callbacks and losses, no argmax is applied
See original GitHub issue(I will compile a list and hopefully open a PR if needed)
Describe the bug This behavior is present in a plethora of catalyst’s callbacks and losses. It’s consistent, but it’s definitely confusing for many new users.
To Reproduce Steps to reproduce the behavior: Use these functions/classes: Callbacks
MeterMetricsCallback- I’m not sure if this can support meters with softmax? Need to double check
Criterion // Dependents
Expected behavior
Should ideally apply argmax when activation='Softmax2d'
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Scitator Ahhhh sorry, I’ve been prioritizing work lately. I’ll hopefully get to this by the end of next week. I think the PR should just be a warning for the next version and then the actual changes on the version after that.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.