File size: 2,252 Bytes
b513e94
 
 
 
 
 
 
 
6b41f39
b513e94
 
a4221ee
 
8508c38
 
a4221ee
 
 
 
4f00213
 
a4221ee
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
---
license: mit
language:
- en
tags:
- tokeniser
pretty_name: tokeniser on val, test set of Slim Pajama
size_categories:
- 1B<n<10B
---

# Tokenizer

**Imp Links: [PyPI Main Library (tokeniser-py)](https://pypi.org/project/tokeniser-py/) | [PyPI Lite Library (tokeniser-py-lite)](https://pypi.org/project/tokeniser-py-lite/) | [Main Library GitHub (tokeniser-py)](https://github.com/Tasmay-Tibrewal/tokeniser-py) | [Lite Library GitHub (tokeniser-py-lite)](https://github.com/Tasmay-Tibrewal/tokeniser-py-lite) | [Demo (HF Spaces)](https://huggingface.co/spaces/Tasmay-Tib/Tokeniser-py) | [Complete repo (chunked) - GitHub](https://github.com/Tasmay-Tibrewal/Tokeniser) | [Imp Files Github](https://github.com/Tasmay-Tibrewal/Tokeniser-imp)**

This is a tokeniser created on a custom-written algorithm on a huge vocabulary of `~1B` tokens. These tokens are given in the files (such that they are `<2GB` each, making them trackable by Git LFS). The text corpus is from the `SlimPajama` dataset by cerebras and consists of the whole text and validation corpus.
The final tokeniser is available in two versions (`0.5B` version - Val. data only and `1B` version - Val data + Test data, created using the same algo).
The files includes the token counts, the text corpus used, individual lines/paras from SlimPajama as a list JSON, ordered tokeniser with token ids (in order of their counts), unordered tokeniser  with token ids.

The tokeniser contains 131,072 tokens. 

## To do:
- Write custom code for the final tokenisation part (to break text into tokens)
- Create a python library for using the tokeniser
- Put the files on GitHub for a general overview
- Release the experimentation notebook and the tokenisation code (as part of the library)
- Make a writeup to explain the algo used

`Note: algo used is no industry standard algo like Byte Pair encoding, infact i have not studied BPE yet, i wanted to create a tokeniser from scratch first without any idea of what is currently used, and then compare the two, so a lot of what i implement may have similarities to that in industry but may not provide some performance improvement`

I am storing it on HF, not on GITHUB, because of storage issues, and due to easy availability for the AI community.