PairPlex: large-scale natively paired antibody sequencing
PairPlex uses combinatorial barcoding (inspired by UDA-seq) to perform cost-effective sequencing of large numbers of natively paired antibodies by massively overloading 10x Genomics reactions.
Installation
PairPlex can be installed with pip:
pip install pairplex
Alternatively, you can install from source (which may not be entirely stable, so use at your own risk):
git clone https://github.com/brineylab/pairplex
cd pairplex
pip install .
Installation can be quickly confirmed by checking the version:
pairplex version
If the current version is displayed, installation was successful.
Usage
CLI
pairplex run /path/to/sequencing_data /path/to/output_directory
Sequencing data can be provided as a single FASTA/Q file or a directory containing one or more FASTA/Q files (optionally gzip compressed). If a directory is provided, all files in the directory will be processed (recursively).
Providing the merge_paired_reads option will instruct PairPlex to merge paired-end sequencing reads with fastp prior to processing, so the output of Illumina's bcl2fastq or Element's bases2fastq can be used directly as input:
pairplex run --merge_paired_reads /path/to/paired_reads /path/to/output_directory
By default, we assume Illumina-style naming conventions for paired-end read files. For paired FASTQ files produced by Element's bases2fastq, the platform option should be set to element.
pairplex run --merge_paired_reads --platform element /path/to/paired_reads /path/to/output_directory
[!NOTE] If the sequencing data is already merged (or wasn't paired-end to begin with), the
platformoption is not used, since the file naming conventions are only needed to match file pairs for read merging.
The complete list of CLI options can be displayed by running:
pairplex run --help
API
import pairplex
pairplex.run(
sequences="/path/to/sequencing_data",
output_directory="/path/to/output_directory",
merge_paired_reads=True,
)
Citation
If you are using Pairplex or the dataset generated of paired antibody sequences, please cite:
Metadata
Release files for pairplex 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pairplex-0.3.0.tar.gz | 17.8 MB | With provenance | Details for pairplex-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pairplex-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for pairplex-0.3.0-py3-none-any.whl |
Total release size: 35.6 MB
Release files / pairplex-0.3.0.tar.gz
| Download URL | pairplex-0.3.0.tar.gz |
|---|---|
| Size | 17.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b0063bd806ac67c3b777f977ebdb9bf6e8792ca15522cd1c683559903c2e6aa
|
|
BLAKE2b-256 checksum How to use checksums |
17ff4cf150f91681ed8d80524da0784c2c955938d89ce66468f01f1f05c9c825
|
| 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 22, 2025.
Transparency logRelease files / pairplex-0.3.0-py3-none-any.whl
| Download URL | pairplex-0.3.0-py3-none-any.whl |
|---|---|
| Size | 17.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6bba41f34390f24f109c7dd3de9528f9d6cfeb3dda0a254e3b454c86adf323ea
|
|
BLAKE2b-256 checksum How to use checksums |
39914057148f102e390510e16ec23d51f68e1d162a31c6a56e13b6edb244c362
|
| 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 22, 2025.
Transparency logSecurity for pairplex 0.3.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pairplex-0.3.0.tar.gz
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 22, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.