:orphan: .. only available via index, not via toctree .. title:: Package Recipe 'rsem' .. highlight: bash rsem ==== .. conda:recipe:: rsem :replaces_section_title: :noindex: RSEM is a software package for estimating gene and isoform expression levels from RNA\-Seq data. :homepage: https://deweylab.github.io/RSEM :developer docs: https://github.com/deweylab/RSEM :license: GPL3 / GPL-3.0-or-later :recipe: /`rsem `_/`meta.yaml `_ :links: doi: :doi:`10.1186/1471-2105-12-323`, biotools: :biotools:`rsem` \"RSEM is a software package for estimating gene and isoform expression levels from RNA\-Seq data. \" \"The RSEM package provides an user\-friendly interface\, supports threads for parallel computation \" \"of the EM algorithm\, single\-end and paired\-end read data\, quality scores\, variable\-length reads \" \"and RSPD estimation. In addition\, it provides posterior mean and 95\% credibility interval \" \"estimates for expression levels. For visualization\, It can generate BAM and Wiggle files in both \" \"transcript\-coordinate and genomic\-coordinate. Genomic\-coordinate files can be visualized by both \" \"UCSC Genome browser and Broad Institute\'s Integrative Genomics Viewer \(IGV\). Transcript\-coordinate \" \"files can be visualized by IGV. RSEM also has its own scripts to generate transcript read depth \" \"plots in pdf format. The unique feature of RSEM is\, the read depth plots can be stacked\, with read \" \"depth contributed to unique reads shown in black and contributed to multi\-reads shown in red. In \" \"addition\, models learned from data can also be visualized. Last but not least\, RSEM contains a \" \"simulator.\" .. conda:package:: rsem |downloads_rsem| |docker_rsem| :versions: .. raw:: html
1.3.3-121.3.3-111.3.3-101.3.3-91.3.3-71.3.3-61.3.3-51.3.3-41.3.3-3 ``1.3.3-12``,  ``1.3.3-11``,  ``1.3.3-10``,  ``1.3.3-9``,  ``1.3.3-7``,  ``1.3.3-6``,  ``1.3.3-5``,  ``1.3.3-4``,  ``1.3.3-3``,  ``1.3.3-2``,  ``1.3.3-1``,  ``1.3.3-0``,  ``1.3.2-1``,  ``1.3.2-0``,  ``1.3.1-1``,  ``1.3.1-0``,  ``1.3.0-4``,  ``1.3.0-3``,  ``1.3.0-2``,  ``1.3.0-1``,  ``1.3.0-0``,  ``1.2.28-2``,  ``1.2.28-0``,  ``1.2.22-0``,  ``1.2.21-5``,  ``1.2.21-4``,  ``1.2.21-3`` .. raw:: html
:depends on bioconductor-biobase: :depends on bioconductor-ebseq: :depends on htslib: ``>=1.22.1,<1.23.0a0`` :depends on libgcc: ``>=13`` :depends on libstdcxx: ``>=13`` :depends on libzlib: ``>=1.3.1,<2.0a0`` :depends on perl: ``>=5.32.1,<5.33.0a0 *_perl5`` :depends on perl-module-build: ``0.4234.*`` :depends on r-base: :depends on samtools: :depends on ucsc-bigwigsummary: :additional platforms: .. raw:: html linux-aarch64osx-arm64 Installation ------------ You need a conda-compatible package manager (currently either `pixi `__, `conda `__, or `micromamba `__) 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 rsem to add into an existing workspace instead, run:: pixi add rsem 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 rsem Alternatively, to install into a new environment, run:: conda create -n envname rsem 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/rsem: (see `rsem/tags`_ for valid values for ````). 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_rsem| image:: https://img.shields.io/conda/dn/bioconda/rsem.svg?style=flat :target: https://anaconda.org/bioconda/rsem :alt: (downloads) .. |docker_rsem| image:: https://quay.io/repository/biocontainers/rsem/status :target: https://quay.io/repository/biocontainers/rsem .. _`rsem/tags`: https://quay.io/repository/biocontainers/rsem?tab=tags .. raw:: html 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/rsem/README.html) .. |install-with-bioconda| image:: https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat :target: http://bioconda.github.io/recipes/rsem/README.html