SRUFinder
Detect and subtype Single Repeat Units, mini-arrays, and CRISPR arrays by repeat matching with a comprehensive repeat sequence database
Table of contents
Quick start
conda create -n srufinder -c conda-forge -c bioconda -c russel88 srufinder
conda activate srufinder
srufinder my.fasta my_output
Installation
SRUFinder can be installed either through conda or pip.
It is advised to use conda, since this installs SRUFinder and all dependencies, and downloads with database in one go.
Conda
Use miniconda or anaconda to install.
Create the environment with SRUFinder and all dependencies and database
conda create -n srufinder -c conda-forge -c bioconda -c russel88 srufinder
pip
If you have the dependencies (Python >= 3.8, Prodigal >= 2.6) in your PATH you can install with pip
Install srufinder python module
python -m pip install srufinder
Upgrade srufinder python module to the latest version
python -m pip install srufinder --upgrade
When installing with pip, you need to download the database manually:
# Download
svn checkout https://github.com/Russel88/SRUFinder/trunk/data
# Tell SRUFinder where the data is:
# either by setting an environment variable (has to done for each terminal session, or added to .bashrc):
export SRUFINDER_DB="/path/to/data/"
# or by using the --db argument each time you run SRUFinder:
srufinder input.fa output --db /path/to/data/
SRUFinder - How to
SRUFinder takes as input a nucleotide fasta, and produces outputs with SRU predictions
Activate environment
conda activate srufinder
Run with a nucleotide fasta as input
srufinder genome.fa my_output
For metagenome assemblies and short contigs/plasmids/phages, change the prodigal mode
The default prodigal mode expects the input to be a single draft or complete genome
srufinder assembly.fa my_output --prodigal meta
Check the different options
srufinder -h
Metadata
Release files for srufinder 0.2.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 | Actions |
|---|---|---|---|---|
| srufinder-0.2.1.tar.gz | 11.9 kB | Without provenance | Details for srufinder-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| srufinder-0.2.1-py3.9.egg | Legacy Egg format | - | - | Details for srufinder-0.2.1-py3.9.egg |
Total release size: 37.6 kB
Release files / srufinder-0.2.1.tar.gz
| Download URL | srufinder-0.2.1.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
520155c7a5789cedd714597956baf4a03c4cd5c5f290070c2fdb95bb0ca9ff20
|
|
BLAKE2b-256 checksum How to use checksums |
32b1a7596be5386ae32f288def50acea724bd3dab9eb6f73aadd37b093cca202
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/0.0.0 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Release files / srufinder-0.2.1-py3.9.egg
| Download URL | srufinder-0.2.1-py3.9.egg |
|---|---|
| Size | 25.7 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
633a5d4edfcda810539e0b00ef3bd0fb3664fe0f61f1f287c6fce9459d9f38e7
|
|
BLAKE2b-256 checksum How to use checksums |
c6f510c3bd1284cb3afe4e8e3ed635d3ff3bb9dda6ab3058c2d59d2e893d6166
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/0.0.0 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Security for srufinder 0.2.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.