STōk: structure tokenizer
Encoder-only protein structure tokenizer using SDPA attention with RoPE and a SwiGLU MLP, managed via Hydra. The classifier can be tied to a frozen VQ codebook for per-residue structure tokens.
install
pip install stok
smoke test
The following smoke test command will print the config, model parameter count, and run a tiny forward pass:
stok smoke-test
Config overrides can be used to run a smoke test using a different model architecture. This is useful for testing different architectures to ensure that the selected hyperparameters are compatible.
stok smoke-test model.encoder.d_model=512 model.encoder.n_heads=8 model.encoder.n_layers=6
codebook presets and custom files
By default the model uses the built-in codebook preset base, which corresponds to the codebook used in the Large GCP-VQVAE model. Config overrides can be used to change the codebook.
-
Use a different built-in preset (for example, the codebook use in the Lite GCP-VQVAE model variant:
stok smoke-test model.codebook.preset=lite
-
Use a custom codebook file (overrides preset):
stok smoke-test model.codebook.path=/abs/path/to/codebook.pt
If using a custom codebook file, it must be a PyTorch tensor saved in .pt format and of shape [C, d_code], where C is the codebook size and d_code is the codebook dimension. If d_code does not match the encoder model dimension, a linear projection will be automatically added to the classifier head.
Configuration fields:
model:
codebook:
preset: "base" # one of: "base", "lite" (default: base)
path: null # custom file path; when set, overrides preset
training
Single‑GPU (quick/dev):
stok train \
data.train=/abs/path/to/train.csv \
data.eval=/abs/path/to/eval.csv
Multi‑GPU with Accelerate (spawns one process per GPU):
accelerate launch -m stok.train \
data.train=/abs/path/to/train.csv \
data.eval=/abs/path/to/eval.csv
Notes:
- Verify your setup with:
accelerate env - If your default Accelerate config is not set to 8 processes, you can pass:
accelerate launch --num_processes 8 -m stok.train ...
- DataLoader workers are per process. Tune
data.num_workersto avoid oversubscription when using many GPUs.
Metadata
Release files for stok 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| stok-0.1.4.tar.gz | 6.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stok-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.1 MB
Release files / stok-0.1.4.tar.gz
| Download URL | stok-0.1.4.tar.gz |
|---|---|
| Size | 6.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec13b0dc4cade38f8d5adc33a95fb27da4a7e4adea5079d651afaa562261f1d3
|
|
BLAKE2b-256 checksum How to use checksums |
5be0ffcdcaf3d9a0b5d16ba01708113ac28aed3a2a49c3f2232a8e7f505008b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2025.
Transparency logRelease files / stok-0.1.4-py3-none-any.whl
| Download URL | stok-0.1.4-py3-none-any.whl |
|---|---|
| Size | 6.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
483f21244fe348f55350d12d4b62bbf58f0476753c913f8448669026d73f0408
|
|
BLAKE2b-256 checksum How to use checksums |
bb7468c499cb14598d7d982a7701e09226d1f40c47f3bddd9aced51eae993c60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2025.
Transparency log