From: Brian Gough <bjg@network-theory.co.uk>
To: Kai Trukenmueller <trukenm@ag2.mechanik.tu-darmstadt.de>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: gsl_multifit
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15309.21550.715964.974298@debian> (raw)
In-Reply-To: <20011017013629.A7648@abb121.ram1st.wh.tu-darmstadt.de>
Kai Trukenmueller writes:
> I benchmarked the programs on system with Athlon 1GHz, 640MB running Linux-2.4.10 with the following results:
>
> Dimensions (120,80) (300,200) (600,400) (900,600) (1200,800)
> Octave-Script 0.060s 0.410s 3.390s 12.260s 39.790s
> Compiled gsl 0.110s 2.240s 31.310s 2m7.590s seg.fault
>
> The gsl routine not just turns out to be much slower, it also seems to
> be `instable' for higher orders (the results do not convege -> inft..)
> Maybe sth. is wrong in my code. For low-orders (~<500) both results are
> equivalent.
Regarding the segfault, your program contains some fixed length arrays
which are accessed outside the array bounds -- if you allocate them
dynamically that problem should go away.
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 gsl_multifit Kai Trukenmueller
2001-12-19 13:20 ` gsl_multifit Brian Gough
2001-12-19 13:20 ` gsl_multifit Kai Trukenmueller
2001-12-19 13:20 ` Brian Gough [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 gsl_multifit Mikael Adlers
2001-12-19 13:20 ` gsl_multifit Kai Trukenmueller
2001-12-19 13:20 ` gsl_multifit Brian Gough
2001-12-19 13:20 ` gsl_multifit Henry Sobotka
2001-12-19 13:20 ` gsl_multifit Brian Gough
2001-12-19 13:20 ` gsl_multifit Dirk Eddelbuettel
2001-12-19 13:20 gsl_multifit Mikael Adlers
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=15309.21550.715964.974298@debian \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
--cc=trukenm@ag2.mechanik.tu-darmstadt.de \
/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).