seqme is a modular and extendable python library containing model-agnostic metrics for evaluating biological sequence designs. It enables benchmarking and comparison of generative models for small molecules, DNA, RNA, peptides, and proteins.
Key features:
- Metrics: A collection of sequence-, embedding-, and property-based metrics for evaluating generative models designs.
- Models: Out-of-the-box, pre-trained property and embedding models for small molecules, DNA, RNA, peptides, and proteins.
- Visualizations: Functionality to display metric results from single-shot and iterative optimization methods as tables and plots.
Is a metric or model missing? seqme's modular metric and third-party model interfaces make adding your own easy.
Installation
You need to have Python 3.10 or newer installed on your system. To install the base package do:
$ pip install seqme
To install sequence-specific models as well, include the appropriate extras specifiers. Check the individual model docs for installation instructions.
Quick start
Install seqme and the protein language model, ESM-2.
$ pip install "seqme[esm2]"
Run in a Jupyter notebook:
import seqme as sm
sequences = {
"Random": ["MKQW", "RKSPL"],
"UniProt": ["KKWQ", "RKSPL", "RASD"],
"HydrAMP": ["MMRK", "RKSPL", "RRLSK", "RRLSK"],
}
cache = sm.Cache(
models={"esm2": sm.models.ESM2(
model_name="facebook/esm2_t6_8M_UR50D", batch_size=256, device="cpu")
}
)
metrics = [
sm.metrics.Uniqueness(),
sm.metrics.Novelty(reference=sequences["UniProt"]),
sm.metrics.FBD(reference=sequences["Random"], embedder=cache.model("esm2")),
]
df = sm.evaluate(sequences, metrics)
sm.show(df) # Note: Will only display the table in a notebook.
Check out the docs for in-depth tutorials and examples.
Citation
If you use seqme in your research, consider citing our publication:
@article{mollerlarsen2025seqme,
title={seqme: a Python library for evaluating biological sequence design},
author={Rasmus Møller-Larsen and Adam Izdebski and Jan Olszewski and Pankhil Gawade and Michal Kmicikiewicz and Wojciech Zarzecki and Ewa Szczurek},
year={2025},
eprint={2511.04239},
archivePrefix={arXiv},
primaryClass={cs.LG},
url={https://arxiv.org/abs/2511.04239},
}
Metadata
Release files for seqme 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| seqme-0.5.1.tar.gz | 65.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seqme-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 142.3 kB
Release files / seqme-0.5.1.tar.gz
| Download URL | seqme-0.5.1.tar.gz |
|---|---|
| Size | 65.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ead48950221d1ca0931c593acbd8a2138778f33c76819b58846388472a83c7d
|
|
BLAKE2b-256 checksum How to use checksums |
ab4a1448cd14b7426039c82175207d36b3d1bac9de6e031b2eee7ddd5a14de5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 22, 2026.
Transparency logRelease files / seqme-0.5.1-py3-none-any.whl
| Download URL | seqme-0.5.1-py3-none-any.whl |
|---|---|
| Size | 76.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cb66430ace2df57e57e29ea1462d50de932aed3c0f9d908919979d2b2b0cd7b6
|
|
BLAKE2b-256 checksum How to use checksums |
276c8f1eb32efed56af3e94ef0cb82c93f7bdfecdf9b0e08ddda40dcf49079dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 22, 2026.
Transparency log