- recipe coprarna
Target prediction for prokaryotic trans-acting small RNAs
- Homepage:
- License:
MIT
- Recipe:
- package coprarna¶
- Versions:
2.1.4-0,2.1.3-9,2.1.3-8,2.1.3-7,2.1.3-6,2.1.3-5,2.1.3-4,2.1.3-3,2.1.3-2,2.1.4-0,2.1.3-9,2.1.3-8,2.1.3-7,2.1.3-6,2.1.3-5,2.1.3-4,2.1.3-3,2.1.3-2,2.1.3-1,2.1.3-0,2.1.2-0,2.1.1-0,2.1.0-0- Depends:
on blast-legacy
on bzip2
on clustalo
on coreutils
on domclust
on embassy-phylip
on emboss
on gawk
on grep
on intarna
>2.2,<3on mafft
on perl
<6on perl-bio-eutilities
on perl-bioperl
on perl-getopt-long
on perl-list-moreutils
on perl-parallel-forkmanager
on phantomjs
on python
on r-base
<4on r-pheatmap
on r-robustrankaggreg
on r-seqinr
on sed
on suds-jurko
- Additional platforms:
Installation¶
You need a conda-compatible package manager (currently either pixi, conda, or micromamba) and the Bioconda channel already activated (see Usage). Below, we show how to install with either pixi or conda (for micromamba and mamba, commands are essentially the same as with conda).
Pixi¶
With pixi installed and the Bioconda channel set up (see Usage), to install globally, run:
pixi global install coprarna
to add into an existing workspace instead, run:
pixi add coprarna
In the latter case, make sure to first add bioconda and conda-forge to the channels considered by the workspace:
pixi workspace channel add conda-forge
pixi workspace channel add bioconda
Conda¶
With conda installed and the Bioconda channel set up (see Usage), to install into an existing and activated environment, run:
conda install coprarna
Alternatively, to install into a new environment, run:
conda create -n envname coprarna
with envname being the name of the desired environment.
Container¶
Alternatively, every Bioconda package is available as a container image for usage with your preferred container runtime. For e.g. docker, run:
docker pull quay.io/biocontainers/coprarna:<tag>
(see coprarna/tags for valid values for <tag>).
Integrated deployment¶
Finally, note that many scientific workflow management systems directly integrate both conda and container based software deployment. Thus, workflow steps can be often directly annotated to use the package, leading to automatic deployment by the respective workflow management system, thereby improving reproducibility and transparency. Check the documentation of your workflow management system to find out about the integration.
Download stats¶
Link to this page¶
Render an 
badge with the following MarkDown:
[](http://bioconda.github.io/recipes/coprarna/README.html)
