Lapels remaps reads aligned to the in silico genome back to the reference coordinate and annotates variants.
- Two files are taken as input:
a MOD file that is used to generate the in silico genome and
a BAM file that contains the in silico genome alignments.
Lapels will generate a new BAM file with corrected read positions, adjusted cigar strings, and annotated tags of variants (eg. SNPs, Insertions, and Deletions).
Metadata
Release files for lapels 1.1.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 | Provenance | Actions |
|---|---|---|---|---|
| lapels-1.1.1.tar.gz | 22.3 kB | Without provenance | Details for lapels-1.1.1.tar.gz |
Release files / lapels-1.1.1.tar.gz
| Download URL | lapels-1.1.1.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37da9ac43887dfc45503ccf9f4135bb8992e89f6d32a204fe8c8e0ee57b7aa7d
|
|
BLAKE2b-256 checksum How to use checksums |
4d7743f12a0b79429f4b31d9041a1c8b9744c0f5b6da557fec68d36a7312c047
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lapels 1.1.1
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.