From: Brian Gough <bjg@network-theory.co.uk>
To: tlb@tlb.org
Cc: gsl-discuss@sources.redhat.com
Subject: Re: multifit_nlin on linear data
Date: Sun, 14 Jul 2002 14:05:00 -0000 [thread overview]
Message-ID: <15665.57423.817466.370459@debian> (raw)
In-Reply-To: <200207122024.g6CKODl4055949@tlb.blackwells.net>
tlb@tlb.org writes:
> I have a multiparameter fitting problem which is nonlinear in general,
> but has linear behavior in some regions where I can exactly calculate
> the derivatives. So sometimes when I use gsl_multifit_fdfsolver it's
> able to jump to the correct solution in a single jump, as you'd expect
> it to.
>
> Should I be using a different termination critereon than
> gsl_multifit_test_delta?
I'd recommend using a different termination criterion. The step size
is not a reliable indicator on its own. ETOLF indicates that the
algorithm can't go any further downhill, so you can usually
take that as signalling a minimum if you know that the behavior
of the function is reasonable.
regards
Brian Gough
prev parent reply other threads:[~2002-07-14 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 13:24 tlb
2002-07-14 14:05 ` Brian Gough [this message]
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=15665.57423.817466.370459@debian \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
--cc=tlb@tlb.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).