public inbox for
 help / color / mirror / Atom feed
From: Matthias Sitte <>
Subject: new interface for simulated annealing
Date: Mon, 06 Jul 2015 18:33:00 -0000	[thread overview]
Message-ID: <> (raw)

Hi all,

I'm currently working on a smaller-size simulated annealing problem. Ideally,
I'd like to use an interface like "ode-initval2", where you can easily select a
different solver while all the dirty work is hidden. Unfortunately, the current
"siman" implementation is rather fixed and doesn't allow what I have in mind.
Expanding it almost immediately breaks the API. So I'm trying to implement a
"new" simulated annealing interface inspired by the "ode-initval2" interface
with separate stepper, control, evolve, and driver objects. It's not yet fully
finished, but I'd like to hear your thoughts on it in general, and how to
proceed if you want to incorporate it into GSL at some point (in terms of
requirements etc).

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?



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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 18:33 Matthias Sitte [this message]
2015-07-06 18:49 ` Gerard Jungman
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).