This is the mail archive of the
gsl-discuss@sources.redhat.com
mailing list for the GSL project.
Re: Simulated Annealing
- From: Brian Gough <bjg at network-theory dot co dot uk>
- To: =?koi8-r?q?panov=40=D3anopus=2Eiacp=2Edvo=2Eru?= at canopus dot iacp dot dvo dot ru
- Cc: gsl-discuss at sources dot redhat dot com
- Date: Tue, 5 Feb 2002 19:48:42 +0000 (GMT)
- Subject: Re: Simulated Annealing
- References: <200202050518.g155I4j03512@canopus.iacp.dvo.ru>
Andrey V. Panov writes:
> gsl_siman_solve() uses gsl_siman_copy_t copyfunc(),
> gsl_siman_copy_construct_t copy_constructor(),
> gsl_siman_destroy_t destructor() or memcpy() functiions.
> Is it better to implement gsl_siman_solve() through gsl_vector_X functions
> and use gsl_vector * in energy, step functions parameters? I am working on
> this.
It's designed to handle arbitrary data structures, including mixed
integer/real, lists, trees etc, so it takes void *.
If you are working with vectors it should be possible to make small
wrappers of the gsl_vector_alloc, gsl_vector_memcpy and
gsl_vector_free for the copyfunc, copy_constructor and destroy
functions.
Brian