From: Brian Gough <bjg@network-theory.co.uk>
To: <rlee@fpcc.net>
Cc: <gsl-discuss@sources.redhat.com>
Subject: Re: Here is some GSL code for a rank-revealing QRPT
Date: Wed, 12 Nov 2003 13:28:00 -0000 [thread overview]
Message-ID: <16306.13683.266366.946535@debian.local> (raw)
In-Reply-To: <35906.64.24.109.89.1068572699.squirrel@webmail.fpcc.net>
rlee@fpcc.net writes:
> I posted "Help developing a "better" QRPT routine". I guess sometimes we
> help those who help themselves ;-)
>
> Here GSL code for rank-revealing QRPT. It is just a minor tweak of
> gsl_linalg_QRPT_decomp -- the key feature is a different pivoting
> strategy.
>
> I would appreciate any suggestions on making this more "GSL like".
> I've only tested it with some M>N matrices -- some rank deficient.
>
> So, does anyone think this could be a valuable addition to GSL?
Hi,
If there is an improved algorithm I would be in favor of using it.
Is there a paper or other reference (maybe a Lapack Working Note)
which describes this algorithm? The first step is to find out what
has been written about it.
--
Brian Gough
next prev parent reply other threads:[~2003-11-12 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 17:44 rlee
2003-11-12 13:28 ` Brian Gough [this message]
2003-11-12 15:25 ` rlee
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=16306.13683.266366.946535@debian.local \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
--cc=rlee@fpcc.net \
/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).