recipe chipmunk

Fast Java motif discovery tool for ChIP-Seq, HT-SELEX, DNase footprints, and related sequence data.

Homepage:

https://autosome.org/ChIPMunk/

License:

WTFPL AND Apache-2.0 AND LGPL

Recipe:

/chipmunk/meta.yaml

Links:

biotools: chipmunk, doi: 10.1093/bioinformatics/btq488, doi: 10.1142/S0219720013400040

ChIPMunk is a DNA/RNA motif discovery tool distributed as a compiled Java JAR. This package installs command-line wrappers for ChIPMunk, diChIPMunk, and ChIPHorde.

package chipmunk#

(downloads) docker_chipmunk

Versions:

8-0

Depends:
  • on openjdk >=8

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 chipmunk

to add into an existing workspace instead, run:

pixi add chipmunk

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 chipmunk

Alternatively, to install into a new environment, run:

conda create -n envname chipmunk

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/chipmunk:<tag>

(see chipmunk/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

.. Create all the necessary plots for each package by loading all the correct specs and data. Important points on the place and implementation of this script block: 1. It is here, and not in a separate HTML file, as it needs to have the `package.name` rendered in for each package. 2. All packages are handled in one `window.onload` function, as multiple instances of this throughout a (rendered) HTML just overwrite each other.