PepLocus
Map mass-spectrometry peptides directly to eukaryotic genome assemblies, including splice-junction peptides. PepLocus searches all six reading frames, always treats I/L as equivalent, and can use GTF/GFF annotations or RNA-seq BAM evidence.
Install
Requires Python 3.9 or newer. Linux and macOS are recommended.
python -m pip install "git+https://github.com/qussai96/PepLocus.git"
Once published on PyPI:
python -m pip install peplocus
Dependencies are installed automatically; no external aligner is needed.
Run
Map a peptide list to an assembly:
peplocus -a assembly.fa -p peptides.tsv --out results
Add annotation and/or RNA-seq evidence to find splice-junction placements:
peplocus -a assembly.fa -p peptides.tsv -g models.gtf -b rnaseq.bam --out results_spliced
-g accepts GTF or GFF. Either -g or -b can be used alone. A BAM index is not required.
Optional one-edit rescue searches peptides with no exact match for one amino-acid substitution, insertion or deletion:
peplocus -a assembly.fa -p peptides.tsv -g models.gtf --rescue-one-edit --out results_rescue
The default is 8 workers (--threads). Rescue uses a minimum query length of 9 aa; short candidates can be highly ambiguous. Use --min-rescue-length 12 for a more conservative search. --discover-junctions optionally searches for bounded canonical single-intron matches without supplied evidence.
Peptides can be a plain list, FASTA, CSV or TSV; FragPipe's Peptide Sequence column is recognised automatically. Assembly FASTA may be plain or gzip-compressed. Use a fresh output directory for each run.
peplocus -h
Results
| File | Contents |
|---|---|
all_mappings.bed |
Exact and I/L-equivalent placements |
tryptic_mappings.bed |
Placements with compatible tryptic or possible protein-terminal contexts |
mappings.tsv |
Coordinates, sequences, evidence, cleavage contexts and mapping counts |
peptides.tsv |
Per-peptide exact and rescue counts and status |
unmapped.tsv |
Peptides with no exact match, including labeled rescue candidates |
summary.json |
Parameters, counts, timings and search limits |
BED files use standard BED12 coordinates, with peptide names in biological N-to-C orientation on both strands. Rescue candidates are kept separately in rescue/, with their own all/tryptic BED files and detailed TSV. A reusable junctions.tsv is also saved when splice evidence is supplied.
Contiguous matching is exhaustive for the chosen translation table. Splice mapping depends on available junctions and search limits. Placements show sequence compatibility; one-edit candidates are not confirmed variants, and tryptic compatibility alone does not establish biological origin.
Metadata
Release files for peplocus 0.5.6
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 |
|---|---|---|---|---|
| peplocus-0.5.6.tar.gz | 32.7 kB | Without provenance | Details for peplocus-0.5.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| peplocus-0.5.6-py3-none-any.whl | Python 3 | none | any | Details for peplocus-0.5.6-py3-none-any.whl |
Total release size: 70.6 kB
Release files / peplocus-0.5.6.tar.gz
| Download URL | peplocus-0.5.6.tar.gz |
|---|---|
| Size | 32.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
277da7a0f0bf0fc646944f3c3c7bfc0385e23e23f8be64354a120d159c826e5c
|
|
BLAKE2b-256 checksum How to use checksums |
5d483fc8c2fabaaf1a25bf924dc4a10750c4d48492df9d9e27eda16c06f82102
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.18
|
Release files / peplocus-0.5.6-py3-none-any.whl
| Download URL | peplocus-0.5.6-py3-none-any.whl |
|---|---|
| Size | 37.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b7c46c9e75da7e268ac0d2958ff5027bae1d995e172a7be1399fa2ef51022f8
|
|
BLAKE2b-256 checksum How to use checksums |
319d0508c85cec6abf093ad3dd609998deec4cd21416654efa2a7f67ef3009c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.18
|
Security for peplocus 0.5.6
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.