[](https://zenodo.org/badge/latestdoi/71775920)
# KrATER (K-mer Analysis Tool Easy to Run)
Requirements
- Python libraries:
Matplotlib Numpy Scipy
RouToolPa (https://github.com/mahajrod/RouToolPa)
Jellyfish 2
Installation
- Fast way
install jellyfish 2.x.x from http://www.genome.umd.edu/jellyfish.html
sudo pip install routoolpa krater
or
pip install –user routoolpa krater
- Install requirements
install jellyfish 2.x.x from http://www.genome.umd.edu/jellyfish.html
- install python libraries(not necessary if you going to install KrATER via pip)
run following command for global installation
sudo pip install matplotlib numpy scipy
or following command for local installation if you don’t have root permissions
pip install –user matplotlib numpy scipy
- install RouToolPa
- From pip with root permission:
sudo pip install routoolpa
- From pip without root permissions:
pip install –user routoolpa
- Get RouToolPa
git clone https://github.com/mahajrod/routoolpa
Add following strings to ~/.profile and ~/.bashrc (create files if absent). Don’t forget to replace <ROUTOOLPA_DIR> with actual path
PYTHONPATH=${PYTHONPATH}:<ROUTOOLPA_DIR> PATH=${PATH}:<ROUTOOLPA_DIR> export PYTHONPATH export PATH
- Run in terminal
source ~/.profile
- Install KrATER
Use variant 3 to install newest version of KrATER Variant 1: install using pip (old version)
run following command for global installation
sudo pip install krater
run following commands for local installation
pip install –user krater
Then add ~/.local/bin in your PATH variable
cat “PATH=${PATH}:~/.local/bin/” >> ~/.profile cat “PATH=${PATH}:~/.local/bin/” >> ~/.bashrc
Load updated PATH variable
source ~/.profile
Variant 2: install from source code with root permissions
git clone https://github.com/mahajrod/krater cd krater python setup.py build sudo python setup.py install
Variant 3: install from source code without root permissions
- Get KRATER
git clone https://github.com/mahajrod/krater
Add following strings to ~/.profile and ~/.bashrc (create files if absent). Don’t forget to replace <KRATER_DIR> with actual path
PYTHONPATH=${PYTHONPATH}:<KRATER_DIR> PATH=${PATH}:<KRATER_DIR> export PYTHONPATH export PATH
- Run in terminal
source ~/.profile
RUN
If input file/files is/are fastq:
- Typical usage:
draw_kmer_distribution_from_fastq.py -m 23 -t ${THREAD_NUMBER} -b -s 30G -e png -o ${OUTPUT_PREFIX} -i {COMMA_SEPARATED_LIST_OF_FASTQ_FILES} -w ${MINIMUM_COVERAGE_LIMIT_FOR_NON_LOG_PICTURE} -g ${MAXIMUM_COVERAGE_LIMIT_FOR_NON_LOG_PICTURE}
Parameter description:
If input file is jellyfish database
- Typical usage:
draw_kmer_distribution_from_jellyfish_database.py -i ${JELLYFISH_DATABASE} -o ${OUTPUT_PREFIX} -w ${MINIMUM_COVERAGE_LIMIT_FOR_NON_LOG_PICTURE} -g ${MAXIMUM_COVERAGE_LIMIT_FOR_NON_LOG_PICTURE} -e png
If input file is histogram file produced by Jellyfish:
- Typical usage
draw_kmer_distribution_from_histo.py -i ${JELLYFISH_HISTO_FILE} -o ${OUTPUT_PREFIX} -w ${MINIMUM_COVERAGE_LIMIT_FOR_NON_LOG_PICTURE} -g ${MAXIMUM_COVERAGE_LIMIT_FOR_NON_LOG_PICTURE} -e png
Parameter_description:
Metadata
Release files for KrATER 2.5
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 |
|---|---|---|---|---|
| KrATER-2.5.tar.gz | 11.9 kB | Without provenance | Details for KrATER-2.5.tar.gz |
Release files / KrATER-2.5.tar.gz
| Download URL | KrATER-2.5.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13941ce3e819df215d2b39490cb2cbcbf116c172ca01c63e70fab6c3fb803828
|
|
BLAKE2b-256 checksum How to use checksums |
3e6fbe76d0cc0f0d498c6aec6761f5ab2e43644ab7560ed6bafe145bc8363eec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.9 tqdm/4.63.1 importlib-metadata/4.8.3 keyring/23.4.1 rfc3986/1.5.0 colorama/0.4.4 CPython/3.6.9
|
Security for KrATER 2.5
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.