The PhyloToAST project is a collection of python code and scripts that modify the QIIME [1] pipeline by adding/changing several steps including: support for cluster-computing, multiple primer support (eliminate primer bias) [2], enhanced support for species-specific analysis, and additional visualization tools.
Installation
To install PhyloToAST from PyPI:
$ pip install phylotoastFrom source:
$ python setup.py installDocumentation
Full documentation for the scripts and code is available at docs.phylotoast.org (hosted by Read the Docs)
Requirements
The list of required modules will vary depending on which executable scripts and/or parts of the API you may use. For this reason there are no required dependencies that will be automatically installed along with PhyloToAST. Each executable script will check that the required libraries are installed and will print a message if any are not found.
If you would like to install everything up front, the following is a complete list of libraries that are used in PhyloToAST:
matplotlib >= 1.5.0
biopython >= 1.60
biom-format >= 2.1.5
h5py (for parsing BIOM v2.x format files)
Source
The PhyloToAST source is hosted on github.
Citing
Dabdoub, S. M. et al. PhyloToAST: Bioinformatics tools for species-level analysis and visualization of complex microbial datasets. Sci. Rep. 6, 29123; doi: 10.1038/srep29123 (2016).
Publications using PhyloToAST
Tsigarida and Dabdoub et al., The Influence of Smoking on the Peri-Implant Microbiome. Journal of Dental Research, 2015; doi: 10.1177/0022034515590581
Mason et al., The subgingival microbiome of clinically healthy current and never smokers. The ISME Journal, 2014; doi:10.1038/ismej.2014.114
Dabdoub et al., Patient-specific Analysis of Periodontal and Peri-implant Microbiomes. Journal of Dental Research, 2013; doi: 10.1177/0022034513504950
References
[1] J Gregory Caporaso, et al., QIIME allows analysis of high-throughput community sequencing data. Nature Methods, 2010; doi:10.1038/nmeth.f.303
[2] Kumar PS, et al., Target Region Selection Is a Critical Determinant of Community Fingerprints Generated by 16S Pyrosequencing. PLoS ONE (2011) 6(6): e20956. doi:10.1371/journal.pone.0020956
1 maintainer
Metadata
1 maintainer
Release files for phylotoast 1.3.0
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 | |
|---|---|---|---|---|
| phylotoast-1.3.0.tar.gz | 245.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| phylotoast-1.3.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 509.5 kB
Release files / phylotoast-1.3.0.tar.gz
| Download URL | phylotoast-1.3.0.tar.gz |
|---|---|
| Size | 245.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
384f3ccccdc1610896c42cff50a13218903b7a8fab41ad0778c5288d5136cfa8
|
|
BLAKE2b-256 checksum How to use checksums |
06a2399ddd95b5a328057d097de58247d2dcda86d84aef5fa9f068c25b027348
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / phylotoast-1.3.0-py2.py3-none-any.whl
| Download URL | phylotoast-1.3.0-py2.py3-none-any.whl |
|---|---|
| Size | 264.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
ca09d4c6d7d89485c851b3a872cac9a16f5f26de02bc46ed7703779fd6376ac8
|
|
BLAKE2b-256 checksum How to use checksums |
73e0e9bbc5c45622e07731590da5beed583aba70941824980421a58bb2a5ea74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for phylotoast 1.3.0
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.
