public inbox for
 help / color / mirror / Atom feed
From: Gerard Jungman <>
Subject: Re: new interface for simulated annealing
Date: Mon, 06 Jul 2015 18:49:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 07/06/2015 12:33 PM, Matthias Sitte wrote:
> There's one more question: The "ode-initval2" implementation always takes a
> "double y[]" array as input/output. Other method like the Nelder-Mead in
> "multimin" (which is one of my other candidate algorithms) work in terms of
> "gsl_vector" and "gsl_matrix". I'm a bit confused: What is the preferred GSL way
> to deal with this?

That was done to insure that the interfaces are as general
as possible. We don't want to force people to use the GSL
containers. Not everybody wants the heap management, etc,
that is implicit in the main containers, and forcing them
to use the "view" containers is not very polite.

In my opinion, the containers are badly designed.
Don't bake them into the interfaces.

G. Jungman

  reply	other threads:[~2015-07-06 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 18:33 Matthias Sitte
2015-07-06 18:49 ` Gerard Jungman [this message]
2015-07-06 20:13 ` Matthias Sitte

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).