Introduction
ALLEGRO is a synthetic biology tool leveraging linear programming to design the smallest possible gRNA library to fulfill user-specified constraints.
- Design a Cas gRNA library for thousands of species simultaneously
- Flexible library design using an ensemble of options such as tracks, multiplicity, pre- and post-clustering, guide cutting efficacy prediction, and more
- Extremely fast and computationally efficient
- Written in Python, Cython, and C++
Overview of the ALLEGRO workflow. Step (1) Given the gene sequence or the genome of hundreds to thousands of input species, ALLEGRO extracts Cas target sequences. Step (2) ALLEGRO formulates and solves an (integer) linear program including millions of variables. Step (3) The optimal solution of the linear program determines the guide library with minimal size that covers all targets.
Documentation
You may find the documentation for ALLEGRO at its GitHub Wiki.
Support
If you run into any issues or have suggestions for ALLEGRO, please report them on our GitHub Issues tracker. It's the fastest way to get support and helps us improve ALLEGRO for everyone.
About
ALLEGRO has been developed and is maintained by Amirsadra Mohseni, and Stefano Lonardi at the University of California, Riverside.
1 maintainer
Release files for allegro-bio 1.0.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 | |
|---|---|---|---|
| allegro_bio-1.0.1.tar.gz | 57.2 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| allegro_bio-1.0.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| allegro_bio-1.0.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| allegro_bio-1.0.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
Total release size: 18.3 MB
Release files / allegro_bio-1.0.1.tar.gz
| Download URL | allegro_bio-1.0.1.tar.gz |
|---|---|
| Size | 57.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03444a1a79649baeda5d881dcef2c1ca3eb76f6efa6eda7737233b27ddb10ed2
|
|
BLAKE2b-256 checksum How to use checksums |
d255e89f79055d578d66b1b1b3bddc224e229e3bd233f22bfe08c81b8a556393
|
| 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 Apr 4, 2026.
Transparency logRelease files / allegro_bio-1.0.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | allegro_bio-1.0.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
3e143c4eaf6ddace34d6af8a1ef0139822fad5ed73faac5a10de4881a0a35a9b
|
|
BLAKE2b-256 checksum How to use checksums |
10573fcf96e8562e8235566d9bf03e23325e1a73a510a2cf4edc12e1c8f9f5f3
|
| 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 Apr 4, 2026.
Transparency logRelease files / allegro_bio-1.0.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | allegro_bio-1.0.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
f1309345189836a564ecea4dd21135be365591c87eec8dc35fdd5b2f479d87f3
|
|
BLAKE2b-256 checksum How to use checksums |
6ffeae37260f68033daf07b24e06c7c67d426f2217a1346cfb2597f9c9fede28
|
| 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 Apr 4, 2026.
Transparency logRelease files / allegro_bio-1.0.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | allegro_bio-1.0.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
791a8285a467a6820d0a9ee5215f21226609691e651523dbae13b5114f83c522
|
|
BLAKE2b-256 checksum How to use checksums |
b87c40a49839fbc92551539762087494e8e7f00c6a7193f0b723bd9db6127b3e
|
| 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 Apr 4, 2026.
Transparency log
