This repository has been archived by the owner on Nov 22, 2022. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Warn about order of label_vocab for binary classification (#1435)
Summary: Pull Request resolved: #1435 As Junteng reports: > For example, if you have two possible labels in your training data, namely, "0" and "1". If you specify label_vocab as ["0", "1"], then "0" gets map to 0, and "1" gets map to 1. On the other hand, if you specify label_vocab as ["1", "0"], then "0" gets map to 1, and "1" gets map to 0. > Although this is not important for multi-class classification with negative log-likelihood loss, whether a label gets mapped to 0 or 1 matters in CosineEmbeddingLoss Reviewed By: m3rlin45 Differential Revision: D22641684 fbshipit-source-id: f74c83ed3320286d394546cb6394fd34e7e65f04
- Loading branch information