Add BertForSequenceClassification with Native and WASM Examples #2857
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n examples (native + wasm)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces the
BertForSequenceClassificationmodel. It includes two examples to demonstrate its functionality:ModernBert.Additionally, the following type adjustments have been made to align with common conventions observed in Hugging Face models:
label2id: Updated to use astringkey and an unsigned integer value, reflecting common Hugging Face model configurations.id2label: Modified inDebertaV2to use a string key and a string value, consistent with Hugging Face model configurationsNote: The WASM example depends on methods not yet available in the main branch of the upstream
tokenizersrepository.It is compatible with changes proposed in huggingface/tokenizers#1758