public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@network-theory.co.uk>
To: <adam@kleczkowski.net>
Cc: "Gsl-Discuss" <gsl-discuss@sources.redhat.com>
Subject: Re: Simulated annealing
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <15374.32845.301912.301838@debian> (raw)
In-Reply-To: <NCBBIJNHCKHEPHMAPMMIAEKJDCAA.ak133@cus.cam.ac.uk>

Adam Kleczkowski writes:
 > What is the current status of 'simulated annealing' part of GSL?
 > The example program (sim_test.c) does not agree with the help
 > file(s) in the call to gsl_siman_solve. It also contains just a
 > simple 1D case, and all the more complicated 1D, 2D, 3D cases are
 > commented out. gsl_siman_Usolve (used in more complicated part of
 > sim_test.c) does not exist in the library.
 >  I need to use simulated annealing for parameter fitting. I could
 > probably implement it from scratch (it is not too difficult), but
 > it would be nice to simply call a GSL function.

The simulated annealing needs to be cleaned up, also the documentation
is out of date. 

In the meantime siman_tsp.c is a working program that you can use as
an example.

Brian

WARNING: multiple messages have this Message-ID
From: Brian Gough <bjg@network-theory.co.uk>
To: <adam@kleczkowski.net>
Cc: "Gsl-Discuss" <gsl-discuss@sources.redhat.com>
Subject: Re: Simulated annealing
Date: Mon, 03 Dec 2001 15:31:00 -0000	[thread overview]
Message-ID: <15374.32845.301912.301838@debian> (raw)
Message-ID: <20011203153100.jsCkKSiCxEe1IwZ3rmBX8ES3fKIQLC7G89s5PDR52l8@z> (raw)
In-Reply-To: <NCBBIJNHCKHEPHMAPMMIAEKJDCAA.ak133@cus.cam.ac.uk>

Adam Kleczkowski writes:
 > What is the current status of 'simulated annealing' part of GSL?
 > The example program (sim_test.c) does not agree with the help
 > file(s) in the call to gsl_siman_solve. It also contains just a
 > simple 1D case, and all the more complicated 1D, 2D, 3D cases are
 > commented out. gsl_siman_Usolve (used in more complicated part of
 > sim_test.c) does not exist in the library.
 >  I need to use simulated annealing for parameter fitting. I could
 > probably implement it from scratch (it is not too difficult), but
 > it would be nice to simply call a GSL function.

The simulated annealing needs to be cleaned up, also the documentation
is out of date. 

In the meantime siman_tsp.c is a working program that you can use as
an example.

Brian

  parent reply	other threads:[~2001-12-19 13:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Adam Kleczkowski
2001-12-03 10:59 ` Adam Kleczkowski
2001-12-19 13:20 ` Brian Gough [this message]
2001-12-03 15:31   ` Brian Gough
2002-12-31  9:55 Simulated Annealing Andrey V. Panov
2002-02-04 21:18 ` Andrey V. Panov
2002-12-31  9:55 ` Brian Gough
2002-02-05 11:56   ` Brian Gough
2002-12-31  9:55 simulated annealing Francisco J Molina
2002-06-16  6:24 ` Francisco J Molina
2002-12-31  9:55 ` Brian Gough
2002-06-25  9:39   ` Brian Gough
2003-03-24 13:59 Achim Gädke
2003-03-26 22:49 ` Brian Gough
2003-03-31 18:37 ` Brian Gough
2003-08-27 11:52 Simulated annealing Rampas, Tomas
2003-08-27 12:31 ` Achim Gädke

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=15374.32845.301912.301838@debian \
    --to=bjg@network-theory.co.uk \
    --cc=adam@kleczkowski.net \
    --cc=gsl-discuss@sources.redhat.com \
    /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).