public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Patrick Alken <patrick.alken@Colorado.EDU>
To: gsl-discuss@sourceware.org
Subject: Re: Fwd: log probability density functions (PDFs)
Date: Mon, 09 Jul 2012 17:39:00 -0000	[thread overview]
Message-ID: <4FFB173C.50905@colorado.edu> (raw)
In-Reply-To: <CAPEJTf4jH_mmk_e5TiT1HxrF3fpLGozL2bikH4F4W_L+Rtpo2w@mail.gmail.com>

The best option would be to make a standalone extension (see the main 
gsl page for examples), so people can look at it and try it out. We can 
add the extension to the main web page and possibly add it to the main 
source code later if it looks useful.

On 07/09/2012 11:29 AM, Sam Mason wrote:
> Hi,
>
> I sent the following message to the help-gsl list a while ago, but
> haven't received a reply...
>
> Is this sort of contribution useful to the project?
>
> Thanks,
>
>    Sam
>
>
> ---------- Forwarded message ----------
> From: Sam Mason <s.a.mason@warwick.ac.uk>
> Date: 15 June 2012 17:59
> To: help-gsl@gnu.org
>
>
> Hi,
>
> I sent a message to this a couple of months ago enquiring about the
> availability of log-density functions.  I've been using my own
> versions of these since then, and thought it would be good to send
> them back to the community.
>
> I've gone through most of the distributions and added in code
> calculating their log-densities.  I've copied the naming and layout
> convention of the dirichlet distribution; which already had the
> gsl_ran_dirichlet_pdf() and gsl_ran_dirichlet_lnpdf() functions.  I've
> not updated the docs yet, as I wanted to gage interest first.
>
> The code compiles and the tests run successfully on my computer.  I've
> also used the test code as a mini-benchmark, and the changed code
> takes basically the same amount of time to execute (median = 1.0038
> times GSL 1.15, 95%CI=1.0009-1.0064).
>
> Let me know what would make this more useful.
>
>   Sam


  reply	other threads:[~2012-07-09 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPEJTf6T8vk+KgnoDBaZgJzjRUvJfLK+w-S-xwoZ_=f_wgNH3g@mail.gmail.com>
2012-07-09 17:30 ` Sam Mason
2012-07-09 17:39   ` Patrick Alken [this message]
     [not found]   ` <d75321b0fc2d4b7fb010d63b6252dd89@IDMEXCHT02.ads.warwick.ac.uk>
2012-07-09 21:05     ` Sam Mason

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=4FFB173C.50905@colorado.edu \
    --to=patrick.alken@colorado.edu \
    --cc=gsl-discuss@sourceware.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.
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).