findltr
Command-line tool for de novo identification of LTR retrotransposons.
Requirements
Basic Local Alignment Search Tool (BLAST):
$ sudo apt-get install ncbi-blast+
Installations
Example install, using VirtualEnv:
# install/use python virtual environment virtualenv ~/virtenv_scratch --no-site-packages # activate the virtual environment source ~/virtenv_scratch/bin/activate # upgrade pip in the new virtenv pip install -U pip setuptools # install this package in DEVELOPMENT mode python setup.py develop # or simply install # python setup.py install
Options
The list of available options:
General
- --input
Input *.fasta or *.fa file
- --output
Output *.gff file
Search parameters
Option |
Description |
Default |
|---|---|---|
–algorithm |
Algorithm, [kmp|salcp|original] |
original |
–pattern_len |
Length of pattern |
20 |
–min_distance |
Minimal distance between LTRs |
1000 |
–max_distance |
Maximal distance between LTRs |
20000 |
–min_ltr_len |
Minimal length of LTRs |
100 |
–max_ltr_len |
Maximal length of LTRs |
1000 |
Other
- --verbose
Include more details
- --debug
Turn on debugging output, do not catch exceptions
See findltr --help for complete list of available options.
Metadata
Release files for findltr 0.0.2
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 |
|---|---|---|---|---|
| findltr-0.0.2.tar.gz | 7.2 kB | Without provenance | Details for findltr-0.0.2.tar.gz |
Release files / findltr-0.0.2.tar.gz
| Download URL | findltr-0.0.2.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6f84d2fe35f9de0afcbf421044c1630cfea4fb55d105b2907590f924be6fea7
|
|
BLAKE2b-256 checksum How to use checksums |
5b45b999d59695b46c56d31f858fd1e0c18a88c2f2dbcf783685e6a75ab41605
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for findltr 0.0.2
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.