recipe bioconductor-flowworkspace

Infrastructure for representing and interacting with gated and ungated cytometry data sets.

Homepage:

https://bioconductor.org/packages/3.20/bioc/html/flowWorkspace.html

License:

AGPL-3.0-only

Recipe:

/bioconductor-flowworkspace/meta.yaml

Links:

biotools: flowworkspace, doi: 10.1186/1471-2105-13-252

This package is designed to facilitate comparison of automated gating methods against manual gating done in flowJo. This package allows you to import basic flowJo workspaces into BioConductor and replicate the gating from flowJo using the flowCore functionality. Gating hierarchies, groups of samples, compensation, and transformation are performed so that the output matches the flowJo analysis.

package bioconductor-flowworkspace

(downloads) docker_bioconductor-flowworkspace

Versions:
4.22.1-04.18.0-14.18.0-04.14.0-04.12.0-04.10.0-14.10.0-04.6.0-24.6.0-1

4.22.1-04.18.0-14.18.0-04.14.0-04.12.0-04.10.0-14.10.0-04.6.0-24.6.0-14.6.0-04.4.0-04.2.0-24.2.0-14.2.0-04.0.1-03.34.0-03.32.0-13.30.2-03.30.1-03.28.2-03.26.2-03.24.4-0

Depends:
  • on bioconductor-biobase >=2.70.0,<2.71.0

  • on bioconductor-biobase >=2.70.0,<2.71.0a0

  • on bioconductor-biocgenerics >=0.56.0,<0.57.0

  • on bioconductor-biocgenerics >=0.56.0,<0.57.0a0

  • on bioconductor-cytolib >=2.22.0,<2.23.0

  • on bioconductor-cytolib >=2.22.0,<2.23.0a0

  • on bioconductor-delayedarray >=0.36.0,<0.37.0

  • on bioconductor-delayedarray >=0.36.0,<0.37.0a0

  • on bioconductor-flowcore >=2.22.0,<2.23.0

  • on bioconductor-flowcore >=2.22.1,<2.23.0a0

  • on bioconductor-graph >=1.88.0,<1.89.0

  • on bioconductor-graph >=1.88.1,<1.89.0a0

  • on bioconductor-ncdfflow >=2.56.0,<2.57.0

  • on bioconductor-ncdfflow >=2.56.0,<2.57.0a0

  • on bioconductor-rbgl >=1.86.0,<1.87.0

  • on bioconductor-rbgl >=1.86.0,<1.87.0a0

  • on bioconductor-rgraphviz >=2.54.0,<2.55.0

  • on bioconductor-rgraphviz >=2.54.0,<2.55.0a0

  • on bioconductor-rhdf5lib >=1.32.0,<1.33.0

  • on bioconductor-rhdf5lib >=1.32.0,<1.33.0a0

  • on bioconductor-rprotobuflib >=2.22.0,<2.23.0

  • on bioconductor-rprotobuflib >=2.22.0,<2.23.0a0

  • on bioconductor-s4vectors >=0.48.0,<0.49.0

  • on bioconductor-s4vectors >=0.48.0,<0.49.0a0

  • on libblas >=3.9.0,<4.0a0

  • on libgcc >=14

  • on liblapack >=3.9.0,<4.0a0

  • on liblzma >=5.8.2,<6.0a0

  • on libstdcxx >=14

  • on libzlib >=1.3.1,<2.0a0

  • on r-base >=4.5,<4.6.0a0

  • on r-bh >=1.62.0-1

  • on r-cpp11

  • on r-data.table

  • on r-dplyr

  • on r-ggplot2

  • on r-matrixstats

  • on r-scales >=1.3.0

  • on r-xml

Additional platforms:
linux-aarch64

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 bioconductor-flowworkspace

to add into an existing workspace instead, run:

pixi add bioconductor-flowworkspace

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 bioconductor-flowworkspace

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-flowworkspace

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/bioconductor-flowworkspace:<tag>

(see bioconductor-flowworkspace/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