BT-FLOR: Build Transcripts From LOng Reads
Full documentation
https://bt-flor.readthedocs.io
The software build transcripts from long reads.
The software get bam file as input and output gtf file with all alternative spliced transcripts and exons that declared by average of mapping positions of close reads.
The gtf also contain the counts of read in each transcript.
Optinally user can supply known gtf file. In this case the gtf also contains the percent of overlap between the known gtf to the closest transcript and exon that found by the BT-FLOR.
License
BT-FLOR is licensed under GNU General Public License version 3. License needed for commercial use.
2 maintainers
Metadata
2 maintainers
Release files for bbcu.bt-flor 1.0.26
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 |
|---|---|---|---|---|
| bbcu.bt-flor-1.0.26.tar.gz | 22.0 kB | Without provenance | Details for bbcu.bt-flor-1.0.26.tar.gz |
Release files / bbcu.bt-flor-1.0.26.tar.gz
| Download URL | bbcu.bt-flor-1.0.26.tar.gz |
|---|---|
| Size | 22.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1f04969280a992c03145cf5a6df0ff7c92b94cf994912f3d448825d527d22a2
|
|
BLAKE2b-256 checksum How to use checksums |
08baa386802bccf56d6d2d982bb81a80fb3f52de1f3a06acd5f6d00bb9552a24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.11
|
Security for bbcu.bt-flor 1.0.26
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.
