From: Navid Afkhami <navid.afkhami@mdc-berlin.de>
To: 61250@debbugs.gnu.org
Subject: [bug#61250] [PATCH 1/3] gnu: Add r-viper.
Date: Fri, 3 Feb 2023 13:18:52 +0100 [thread overview]
Message-ID: <20230203121854.95308-1-navid.afkhami@mdc-berlin.de> (raw)
* gnu/packages/bioconductor.scm (r-viper): New variable.
---
gnu/packages/bioconductor.scm | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/gnu/packages/bioconductor.scm b/gnu/packages/bioconductor.scm
index 711b988e7f..aeef6f4106 100644
--- a/gnu/packages/bioconductor.scm
+++ b/gnu/packages/bioconductor.scm
@@ -8307,6 +8307,27 @@ (define-public r-variantannotation
coding changes and predict coding outcomes.")
(license license:artistic2.0)))
+(define-public r-viper
+ (package
+ (name "r-viper")
+ (version "1.32.0")
+ (source (origin
+ (method url-fetch)
+ (uri (bioconductor-uri "viper" version))
+ (sha256
+ (base32
+ "11i2q9nakh534nx2l736id7k1yqhk7jpg32sbfl4vrnh398q86h6"))))
+ (properties `((upstream-name . "viper")))
+ (build-system r-build-system)
+ (propagated-inputs (list r-biobase r-e1071 r-kernsmooth r-mixtools))
+ (home-page "https://bioconductor.org/packages/viper")
+ (synopsis
+ "Virtual inference of protein-activity by enriched regulon analysis")
+ (description
+ "Inference of protein activity from gene expression data.
+Including the VIPER and msVIPER algorithms")
+ (license license:gpl2+)))
+
(define-public r-vsn
(package
(name "r-vsn")
--
2.34.1
next reply other threads:[~2023-02-03 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:18 Navid Afkhami [this message]
2023-02-03 12:18 ` [bug#61251] [PATCH 2/3] gnu: Add r-bcellviper Navid Afkhami
2023-02-03 15:49 ` bug#61251: " Ricardo Wurmus
2023-02-03 12:18 ` [bug#61252] [PATCH 3/3] gnu: Add r-dorothea Navid Afkhami
2023-02-03 15:49 ` bug#61252: " Ricardo Wurmus
2023-02-03 15:47 ` bug#61250: [PATCH 1/3] gnu: Add r-viper Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230203121854.95308-1-navid.afkhami@mdc-berlin.de \
--to=navid.afkhami@mdc-berlin.de \
--cc=61250@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).