recipe bioconductor-isobayes

IsoBayes: Single Isoform protein inference Method via Bayesian Analyses

Homepage:

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

License:

GPL-3

Recipe:

/bioconductor-isobayes/meta.yaml

IsoBayes is a Bayesian method to perform inference on single protein isoforms. Our approach infers the presence/absence of protein isoforms, and also estimates their abundance; additionally, it provides a measure of the uncertainty of these estimates, via: i) the posterior probability that a protein isoform is present in the sample; ii) a posterior credible interval of its abundance. IsoBayes inputs liquid cromatography mass spectrometry (MS) data, and can work with both PSM counts, and intensities. When available, trascript isoform abundances (i.e., TPMs) are also incorporated: TPMs are used to formulate an informative prior for the respective protein isoform relative abundance. We further identify isoforms where the relative abundance of proteins and transcripts significantly differ. We use a two-layer latent variable approach to model two sources of uncertainty typical of MS data: i) peptides may be erroneously detected (even when absent); ii) many peptides are compatible with multiple protein isoforms. In the first layer, we sample the presence/absence of each peptide based on its estimated probability of being mistakenly detected, also known as PEP (i.e., posterior error probability). In the second layer, for peptides that were estimated as being present, we allocate their abundance across the protein isoforms they map to. These two steps allow us to recover the presence and abundance of each protein isoform.

package bioconductor-isobayes

(downloads) docker_bioconductor-isobayes

Versions:

1.8.0-01.4.0-01.0.1-0

Depends:
  • on bioconductor-s4vectors >=0.48.0,<0.49.0

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

  • on bioconductor-summarizedexperiment >=1.40.0,<1.41.0

  • on bioconductor-summarizedexperiment >=1.40.0,<1.41.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-data.table

  • on r-doparallel

  • on r-dorng

  • on r-foreach

  • on r-ggplot2

  • on r-glue

  • on r-hdinterval

  • on r-iterators

  • on r-rcpp

  • on r-rcpparmadillo

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

to add into an existing workspace instead, run:

pixi add bioconductor-isobayes

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-isobayes

Alternatively, to install into a new environment, run:

conda create -n envname bioconductor-isobayes

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

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