recipe fastq-screen

FastQ Screen allows you to screen a library of sequences in FastQ format against a set of sequence databases so you can see if the composition of the library matches with what you expect.

Homepage:

https://www.bioinformatics.babraham.ac.uk/projects/fastq_screen

Developer docs:

https://github.com/StevenWingett/FastQ-Screen

License:

GPL3 / GPL-3.0-or-later

Recipe:

/fastq-screen/meta.yaml

package fastq-screen

(downloads) docker_fastq-screen

Versions:
0.16.0-00.15.3-00.15.2-00.14.0-20.14.0-10.14.0-00.13.0-10.13.0-00.11.3-1

0.16.0-00.15.3-00.15.2-00.14.0-20.14.0-10.14.0-00.13.0-10.13.0-00.11.3-10.11.3-00.11.1-10.11.1-00.5.2-10.5.2-0

Depends:
  • on bowtie

  • on bowtie2

  • on perl >=5.32.1,<6.0a0 *_perl5

  • on perl-gdgraph

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 fastq-screen

to add into an existing workspace instead, run:

pixi add fastq-screen

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 fastq-screen

Alternatively, to install into a new environment, run:

conda create -n envname fastq-screen

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/fastq-screen:<tag>

(see fastq-screen/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