CLSify
Classification of Candidatus Liberibacter solanacearum following IPPC (International Plant Protection Convention) standard DP 21: Candidatus Liberibacter solanacearum.
Quick Facts
License: MIT
Programming Language Python
Input / Output - What it Does!
This program takes as the input Sanger sequences from the 16S, 16S-23S, and 50S primers from the IPPC standard DP21. It then aligns them to the GenBank reference sequences EU812559 and EU834131 (as specified in DP21). Based on the alignments and the document DP21, sequence identity is computed and haplotyping is performed, yielding:
sequence identity to EU822559 for identifying the species C. Liberibacter solanacearum, and
haplotyping of the read based on variation from the reference sequence.
Sample names can be inferred from the read names or from a separate mapping TSV file.
Quick Start
This is gonna be really quick!
Installation
We recommend using Bioconda.
First install Bioconda. Then:
# conda install -y clsifyAnd – tadaa – you’re ready to go!
Running
You can have one FASTA (or FASTQ) file with all of your reads or one file for each. If you have a single sequence per FASTA (or FASTQ) file then you can use the file name instead of the sequence name.
# clsify -o result.tsv INPUT.fasta
## OR
# clsify [--use-file-name] -o result.tsv INPUT1.fasta INPUT2.fasta [...]
## e.g.,
# clsify [--use-file-name] -o result.tsv INPUT*.fastaHistory
v0.1.1
Zapping gremlins in haplotype table.
Change formatting of README.
v0.1.0
Initial release.
Everything is new!
1 maintainer
Metadata
1 maintainer
Release files for clsify 0.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 | |
|---|---|---|---|---|
| clsify-0.1.1.tar.gz | 1.3 MB | Without provenance | Details |
Release files / clsify-0.1.1.tar.gz
| Download URL | clsify-0.1.1.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33d02e9d95e3bcc2480c27fa10f5a61c47049252a8787d8c98e95c8194e026e3
|
|
BLAKE2b-256 checksum How to use checksums |
7671a171dfd9de25a91091f73d09c303f0c3e274cf12037af764d53b87d34a51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.7
|
Security for clsify 0.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.
