:orphan:  .. only available via index, not via toctree

.. title:: Package Recipe 'bioconductor-flowspecs'
.. highlight: bash

bioconductor-flowspecs
======================

.. conda:recipe:: bioconductor-flowspecs
   :replaces_section_title:
   :noindex:

   Tools for processing of high\-dimensional cytometry data

   :homepage: https://bioconductor.org/packages/3.22/bioc/html/flowSpecs.html
   :license: MIT + file LICENSE
   :recipe: /`bioconductor-flowspecs <https://github.com/bioconda/bioconda-recipes/tree/master/recipes/bioconductor-flowspecs>`_/`meta.yaml <https://github.com/bioconda/bioconda-recipes/tree/master/recipes/bioconductor-flowspecs/meta.yaml>`_

   This package is intended to fill the role of conventional cytometry pre\-processing software\, for spectral decomposition\, transformation\, visualization and cleanup\, and to aid further downstream analyses\, such as with DepecheR\, by enabling transformation of flowFrames and flowSets to dataframes. Functions for flowCore\-compliant automatic 1D\-gating\/filtering are in the pipe line. The package name has been chosen both as it will deal with spectral cytometry and as it will hopefully give the user a nice pair of spectacles through which to view their data.


.. conda:package:: bioconductor-flowspecs

   |downloads_bioconductor-flowspecs| |docker_bioconductor-flowspecs|

   :versions:
      
      
      .. raw:: html

         <details><summary><span class="truncated-version-list"><code>1.24.0-0</code>,  <code>1.20.0-0</code>,  <code>1.16.0-0</code>,  <code>1.14.0-0</code>,  <code>1.12.0-0</code>,  <code>1.8.0-0</code>,  <code>1.6.0-0</code>,  <code>1.4.0-1</code>,  <code>1.4.0-0</code>,  </span></summary>
      

      ``1.24.0-0``,  ``1.20.0-0``,  ``1.16.0-0``,  ``1.14.0-0``,  ``1.12.0-0``,  ``1.8.0-0``,  ``1.6.0-0``,  ``1.4.0-1``,  ``1.4.0-0``,  ``1.2.0-0``,  ``1.0.0-0``

      
      .. raw:: html

         </details>
      

   
   :depends on bioconductor-biobase: ``>=2.70.0,<2.71.0``
   :depends on bioconductor-biocgenerics: ``>=0.56.0,<0.57.0``
   :depends on bioconductor-biocparallel: ``>=1.44.0,<1.45.0``
   :depends on bioconductor-flowcore: ``>=2.22.0,<2.23.0``
   :depends on r-base: ``>=4.5,<4.6.0a0``
   :depends on r-ggplot2: ``>=3.1.0``
   :depends on r-reshape2: ``>=1.4.3``
   :depends on r-zoo: ``>=1.8.6``

   :additional platforms:
      

Installation
------------

You need a conda-compatible package manager
(currently either `pixi <https://pixi.sh>`__, `conda <https://docs.conda.io/projects/conda>`__, or `micromamba <https://mamba.readthedocs.io>`__)
and the Bioconda channel already activated (see :ref:`bioconda_setup`).
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 :ref:`bioconda_setup`),
to install globally, run::

    pixi global install bioconductor-flowspecs

to add into an existing workspace instead, run::

    pixi add bioconductor-flowspecs

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 :ref:`bioconda_setup`), to install into an existing and activated environment, run::

    conda install bioconductor-flowspecs

Alternatively, to install into a new environment, run::

    conda create -n envname bioconductor-flowspecs

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-flowspecs:<tag>

(see `bioconductor-flowspecs/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.

.. _conda: https://conda.io
.. _pixi: https://pixi.sh
.. |downloads_bioconductor-flowspecs| image:: https://img.shields.io/conda/dn/bioconda/bioconductor-flowspecs.svg?style=flat
   :target: https://anaconda.org/bioconda/bioconductor-flowspecs
   :alt:   (downloads)
.. |docker_bioconductor-flowspecs| image:: https://quay.io/repository/biocontainers/bioconductor-flowspecs/status
   :target: https://quay.io/repository/biocontainers/bioconductor-flowspecs
.. _`bioconductor-flowspecs/tags`: https://quay.io/repository/biocontainers/bioconductor-flowspecs?tab=tags


.. raw:: html

    <script>
        var package = "bioconductor-flowspecs";
        var versions = ["1.24.0","1.20.0","1.16.0","1.14.0","1.12.0"];
    </script>






Download stats
-----------------

.. raw:: html
    :file: ../../templates/package_dashboard.html

Link to this page
-----------------

Render an |install-with-bioconda| badge with the following MarkDown::

   [![install with bioconda](https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat)](http://bioconda.github.io/recipes/bioconductor-flowspecs/README.html)

.. |install-with-bioconda| image:: https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat
   :target: http://bioconda.github.io/recipes/bioconductor-flowspecs/README.html