LAPA
Alternative polyadenylation detection from diverse data sources such as 3'-seq, long-read and short-reads.
Installation
pip install lapa
Poly(A) site calling from long-read RNA-seq or 3'-seq
lapa --alignment {rep1.bam},{rep2.bam},{rep3.bam} \
--fasta {fasta} \
--annotation {gtf} \
--chrom_sizes {chrom_sizes} \
--output_dir {output}
Argument details (doc):
$ lapa --help
Usage: lapa [OPTIONS]
CLI interface for lapa polyA cluster calling.
Options:
--alignment TEXT Single or multiple bam file paths are
separated with a comma.Alternatively, CSV
file with columns of sample, dataset, path
where the sample columns contains the name
of the sample, the dataset is the group of
samples replicates of each other, and path
is the path of bam file. [required]
--fasta TEXT Genome reference (GENCODE or ENSEMBL fasta)
[required]
--annotation TEXT Standart genome annotation (GENCODE or
ENSEMBL gtf). GENCODE gtf file do not
contains annotation for `five_prime_utr` and
`three_prime_utr` so need to be corrected
with `gencode_utr_fix` (see https://github.c
om/MuhammedHasan/gencode_utr_fix.git).
[required]
--chrom_sizes TEXT Chrom sizes files (can be generated with
`faidx fasta -i chromsizes > chrom_sizes`)
[required]
--output_dir TEXT Output directory of LAPA. See
lapa.readthedocs.io/en/latest/output.html)
for the details of the directory structure
and file format. [required]
...
Recommend setting is including all the samples with thier biosample/experimental replicates (tissue, cell line):
samples.csv
sample,dataset,path
ENCFF772LYG,myoblast,ENCFF772LYG.bam
ENCFF421MIL,myoblast,ENCFF421MIL.bam
ENCFF699KOR,myotube,ENCFF699KOR.bam
ENCFF731HHB,myotube,ENCFF731HHB.bam
then LAPA takes samples_config.csv as input:
lapa --alignment samples.csv \
--fasta {fasta} \
--annotation {gtf} \
--chrom_sizes {chrom_sizes} \
--output_dir {output}
...
TSS calling from long-read RNA-seq
lapa_tss --alignment samples.csv \
--fasta {fasta} \
--annotation {gtf} \
--chrom_sizes {chrom_sizes} \
--output_dir {output}
Argument details (doc):
$ lapa_tss --help
Usage: lapa_tss [OPTIONS]
CLI interface for lapa tss cluster calling.
Options:
--alignment TEXT Single or multiple bam file paths are
separated with a comma.Alternatively, CSV
file with columns of sample, dataset, path
where the sample columns contains the name
of the sample, the dataset is the group of
samples replicates of each other, and path
is the path of bam file. [required]
--fasta TEXT Genome reference (GENCODE or ENSEMBL fasta)
[required]
--annotation TEXT Standart genome annotation (GENCODE or
ENSEMBL gtf). GENCODE gtf file do not
contains annotation for `five_prime_utr` and
`three_prime_utr` so need to be corrected
with `gencode_utr_fix` (see https://github.c
om/MuhammedHasan/gencode_utr_fix.git)
[required]
--chrom_sizes TEXT Chrom sizes files (can be generated
with)`faidx fasta -i chromsizes >
chrom_sizes`) [required]
--output_dir TEXT Output directory of LAPA. See
lapa.readthedocs.io/en/latest/output.html)
for the details of the directory structure
and file format. [required]
Documentation
See the following documentation links for other features, parameters of LAPA, python api and statistical testing:
Readthedocs: https://lapa.readthedocs.io/en/latest/index.html
API reference: https://lapa.readthedocs.io/en/latest/autoapi/index.html
Colab tutorials (analysis of myoblast myotube cell differentiation): https://colab.research.google.com/drive/1QzMxCRjCk3i5_MuHzjozSRWMaJgdEdSI?usp=sharing
Cite
If you are using LAPA on academic studies cite the following paper:
@article{celik2022analysis,
title={Analysis of alternative polyadenylation from long-read or short-read RNA-seq with LAPA},
author={Celik, Muhammed Hasan and Mortazavi, Ali},
journal={bioRxiv},
year={2022},
publisher={Cold Spring Harbor Laboratory}
}
Metadata
Release files for lapa 0.0.5
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 |
|---|---|---|---|---|
| lapa-0.0.5.tar.gz | 29.6 kB | Without provenance | Details for lapa-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lapa-0.0.5-py3-none-any.whl | Python 3 | none | any | Details for lapa-0.0.5-py3-none-any.whl |
Total release size: 65.8 kB
Release files / lapa-0.0.5.tar.gz
| Download URL | lapa-0.0.5.tar.gz |
|---|---|
| Size | 29.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3240405cbdd0e68c344676bc780e62368359024726f0ef2c04ef487d49793669
|
|
BLAKE2b-256 checksum How to use checksums |
64cce9059f9e9108f5a9a22e08164e29be3a937bab6c7636a8c2e51bf5b85ceb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.7
|
Release files / lapa-0.0.5-py3-none-any.whl
| Download URL | lapa-0.0.5-py3-none-any.whl |
|---|---|
| Size | 36.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2d6378d8318ce1dd442d27072cda849a3cfec991062edb7d221a6e6031586c0
|
|
BLAKE2b-256 checksum How to use checksums |
5a165e29b4ebbadd96dad3de71e12ab64bcf7dc0a5b825a34bc2676ec224ee8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.7
|
Security for lapa 0.0.5
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.