From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add PePr.
Date: Mon, 26 Oct 2015 15:40:21 +0100 [thread overview]
Message-ID: <87lhap4rsa.fsf@gnu.org> (raw)
In-Reply-To: <idjbnbpyfli.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Fri, 23 Oct 2015 13:44:09 +0200")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> From 6aa9c0cb97350d5cccb43a78e69e2b8887347df0 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
> Date: Fri, 2 Oct 2015 16:37:03 +0200
> Subject: [PATCH] gnu: Add PePr.
>
> * gnu/packages/bioinformatics.scm (pepr): New variable.
[...]
> + (modify-phases %standard-phases
> + (add-after 'unpack 'disable-egg
> + (lambda _
> + (substitute* "setup.py"
> + (("from setuptools import setup")
> + "from distutils.core import setup"))
It would be nice if we had a bug ID or something to refer to this issue:
we don’t want to duplicate the explanation everywhere, yet it’d be nice
to have a pointer to the explanation. WDYT?
> + (description
> + "PePr is a ChIP-Seq peak calling or differential binding analysis tool
> +that is primarily designed for data with biological replicates. It uses a
> +negative binomial distribution to model the read counts among the samples in
> +the same group, and look for consistent differences between ChIP and control
> +group or two ChIP groups run under different conditions. PePr was published
> +on Bioinformatics on Jun 2014.")
I’d remove the last sentence.
Otherwise LGTM.
Thank you!
Ludo’.
next prev parent reply other threads:[~2015-10-26 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 11:44 [PATCH] Add PePr Ricardo Wurmus
2015-10-26 14:40 ` Ludovic Courtès [this message]
2016-03-01 10:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhap4rsa.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.