This repository was archived by the owner on Nov 22, 2022. It is now read-only.
Fix featurizer & memory issues for char embeddings #220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This diff addresses a few issues for CharacterEmbeddings:
YodaFeaturizer
,YodaFeaturizerLocal
, andSimpleFeaturizer
did not create characters that can be used byCharFeatureField
- fix this.CharFeatureField
padded all tokens (in all sentences) to the max token length of each batch, which leads to OOMs (e.g. in hate speech there is a token of length 60k). Instead, add amax_word_length
flag in the feature (default to 20).min_freq
flag for characters (so every character appearing in training data would get an embedding ID). Add this flag.Differential Revision: D13662817