quicktour.RmdPort of the Quicktour vignette in 🤗 tokenizers website. Click here for the original version.
Let’s have a quick look at the 🤗 Tokenizers library features. The library provides an implementation of today’s most used tokenizers that is both easy to use and blazing fast.
It can be used to instantiate a pretrained tokenizer but we will start our quicktour by building one from scratch and see how we can train it.
To illustrate how fast the 🤗 Tokenizers library is, let’s train a new tokenizer on wikitext-103 (516M of text) in just a few seconds. First things first, you will need to download this dataset and unzip it with:
url <- "https://s3.amazonaws.com/research.metamind.io/wikitext/wikitext-103-raw-v1.zip"
fpath <- pins::pin(url)In this tour, we will build and train a Byte-Pair Encoding (BPE) tokenizer. For more information about the different type of tokenizers, check out this guide in the 🤗 Transformers documentation. Here, training the tokenizer means it will learn merge rules by:
The main API of the library is the class Tokenizer, here is how we instantiate one with a BPE model:
tok <- tokenizer$new(model = models_bpe$new(unk_token = "[UNK]"))To train our tokenizer on the wikitext files, we will need to instantiate a trainer, in this case a BpeTrainer:
trainer <- trainers_bpe$new(
special_tokens=c("[UNK]", "[CLS]", "[SEP]", "[PAD]", "[MASK]")
)We can set the training arguments like vocab_size or min_frequency (here left at their default values of 30,000 and 0) but the most important part is to give the special_tokens we plan to use later on (they are not used at all during training) so that they get inserted in the vocabulary.
The order in which you write the special tokens list matters: here “[UNK]” will get the ID 0, “[CLS]” will get the ID 1 and so forth.
We could train our tokenizer right now, but it wouldn’t be optimal. Without a pre-tokenizer that will split our inputs into words, we might get tokens that overlap several words: for instance we could get an "it is" token since those two words often appear next to each other. Using a pre-tokenizer will ensure no token is bigger than a word returned by the pre-tokenizer. Here we want to train a subword BPE tokenizer, and we will use the easiest pre-tokenizer possible by splitting on whitespace.
tok$pre_tokenizer <- pre_tokenizers_whitespace()Now, we can just call the train() method with any list of files we want to use:
tok$train(fpath, trainer)This should only take a few seconds to train our tokenizer on the full wikitext dataset! To save the tokenizer in one file that contains all its configuration and vocabulary, just use the save() method:
tok$save("tokenizer-wiki.json")and you can reload your tokenizer from that file with the from_file() class method:
tok <- tokenizer$from_file("tokenizer-wiki.json")Now that we have trained a tokenizer, we can use it on any text we want with the encode() method:
output <- tok$encode("Hello, y'all! How are you 😁 ?")This applied the full pipeline of the tokenizer on the text, returning an Encoding object. To learn more about this pipeline, and how to apply (or customize) parts of it, check out this page.
This Encoding object then has all the attributes you need for your deep learning model (or other). The tokens attribute contains the segmentation of your text in tokens:
output$tokens
#> [1] "Hello" "," "y" "'" "all" "!" "How" "are" "you"
#> [10] "[UNK]" "?"Similarly, the ids attribute will contain the index of each of those tokens in the tokenizer’s vocabulary:
output$ids
#> [1] 27253 16 93 11 5097 5 7961 5112 6218 0 35An important feature of the 🤗 Tokenizers library is that it comes with full alignment tracking, meaning you can always get the part of your original sentence that corresponds to a given token. Those are stored in the offsets attribute of our Encoding object. For instance, let’s assume we would want to find back what caused the "[UNK]" token to appear, which is the token at index 10 in the list, we can just ask for the offset at the index:
output$offsets[[10]]
#> [1] 26 27and those are the indices that correspond to the emoji in the original sentence:
substr("Hello, y'all! How are you 😁 ?", 26, 27)
#> [1] " \U0001f601"We might want our tokenizer to automatically add special tokens, like "[CLS]" or "[SEP]". To do this, we use a post-processor. TemplateProcessing is the most commonly used, you just have to specify a template for the processing of single sentences and pairs of sentences, along with the special tokens and their IDs.
When we built our tokenizer, we set "[CLS]" and "[SEP]" in positions 1 and 2 of our list of special tokens, so this should be their IDs. To double-check, we can use the token_to_id() method:
tok$token_to_id("[SEP]")
#> [1] 2Here is how we can set the post-processing to give us the traditional BERT inputs:
tok$post_processor <- post_processors_template_processing$new(
single="[CLS] $A [SEP]",
pair="[CLS] $A [SEP] $B:1 [SEP]:1",
special_tokens=list(
list("[CLS]", tok$token_to_id("[CLS]")),
list("[SEP]", tok$token_to_id("[SEP]"))
)
)Let’s go over this snippet of code in more details. First we specify the template for single sentences: those should have the form "[CLS] $A [SEP]" where $A represents our sentence.
Then, we specify the template for sentence pairs, which should have the form "[CLS] $A [SEP] $B [SEP]" where $A represents the first sentence and $B the second one. The :1 added in the template represent the type IDs we want for each part of our input: it defaults to 0 for everything (which is why we don’t have $A:0) and here we set it to 1 for the tokens of the second sentence and the last "[SEP]" token.
Lastly, we specify the special tokens we used and their IDs in our tokenizer’s vocabulary.
To check out this worked properly, let’s try to encode the same sentence as before:
tok$encode("Hello, y'all! How are you 😁 ?")$tokens
#> [1] "[CLS]" "Hello" "," "y" "'" "all" "!" "How" "are"
#> [10] "you" "[UNK]" "?" "[SEP]"To check the results on a pair of sentences, we just pass the two sentences to encode():
output <- tok$encode("Hello, y'all!", "How are you 😁 ?")
output$tokens
#> [1] "[CLS]" "Hello" "," "y" "'" "all" "!" "[SEP]" "How"
#> [10] "are" "you" "[UNK]" "?" "[SEP]"You can then check the type IDs attributed to each token is correct with
output$type_ids
#> [1] 0 0 0 0 0 0 0 0 1 1 1 1 1 1If you save your tokenizer with save(), the post-processor will be saved along.
To get the full speed of the 🤗 Tokenizers library, it’s best to process your texts by batches by using the encode_batch() method:
output <- tok$encode_batch(c("Hello, y'all!", "How are you 😁 ?"))The output is then a list of Encoding objects like the ones we saw before. You can process together as many texts as you like, as long as it fits in memory.
To process a batch of sentences pairs, pass two lists to the encode_batch() method: the list of sentences A and the list of sentences B:
output <- tok$encode_batch(
list(
c("Hello, y'all!", "How are you 😁 ?"),
c("Hello to you too!", "I'm fine, thank you!")
)
)When encoding multiple sentences, you can automatically pad the outputs to the longest sentence present by using enable_padding(), with the pad_token and its ID (which we can double-check the id for the padding token with token_to_id() like before):
tok$enable_padding(pad_id=3, pad_token="[PAD]")We can set the direction of the padding (defaults to the right) or a given length if we want to pad every sample to that specific number (here we leave it unset to pad to the size of the longest text).
output <- tok$encode_batch(c("Hello, y'all!", "How are you 😁 ?"))
output[[2]]$tokens
#> [1] "[CLS]" "How" "are" "you" "[UNK]" "?" "[SEP]" "[PAD]"In this case, the attention mask generated by the tokenizer takes the padding into account:
output[[2]]$attention_mask
#> [1] 1 1 1 1 1 1 1 0