Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Can we reduce memory consumption by storing segmentation labels as class indices, not one-hot? #338

Open
ant0nsc opened this issue Dec 10, 2020 · 0 comments
Open

Can we reduce memory consumption by storing segmentation labels as class indices, not one-hot? #338

ant0nsc opened this issue Dec 10, 2020 · 0 comments

Comments

@ant0nsc
Copy link
Contributor

ant0nsc commented Dec 10, 2020 •
edited by azure-boards bot
Loading

Discussion topic: We are consistently assuming that the segmentation classes are mutually exclusive, but we are not storing them in that way. Rather, we store much more memory intensive one-hot encodings. Can we save memory by not doing one-hot?
Clearly, we'd have to change our loss functions.

AB#3901
@ant0nsc ant0nsc added no changelog needed CHANGELOG.md does not need to be updated in this PR and removed no changelog needed CHANGELOG.md does not need to be updated in this PR labels Apr 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ant0nsc