recipe barcode_splitter

Split multiple fastq files by matching barcodes in one or more of the sequence files. Barcodes in the tab-delimited barcodes.txt file are matched against the beginning (or end) of the specified index read(s). By default, barcodes must match exactly, but --mistmatches can be set higher if desired. Compressed input is read (from all files) if the first input file name ends in .gz. Reading of compressed input can be forced with the gzipin option.

Homepage:

https://bitbucket.org/princeton_genomics/barcode_splitter

License:

GNU

Recipe:

/barcode_splitter/meta.yaml

Links:

doi: 10.5281/zenodo.2566616

package barcode_splitter

(downloads) docker_barcode_splitter

Versions:

0.18.6-00.18.5-00.18.4-0

Depends:
  • on python

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 barcode_splitter

to add into an existing workspace instead, run:

pixi add barcode_splitter

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 barcode_splitter

Alternatively, to install into a new environment, run:

conda create -n envname barcode_splitter

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

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