public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dirk Eddelbuettel <edd@debian.org>
To: Peter Teuben <teuben@astro.umd.edu>
Cc: "gsl-discuss\@sourceware.org" <gsl-discuss@sourceware.org>,
	Patrick Alken <patrick.alken@Colorado.EDU>
Subject: Re: Robust linear least squares
Date: Sun, 12 May 2013 18:13:00 -0000	[thread overview]
Message-ID: <20879.56271.237184.255948@max.nulle.part> (raw)
In-Reply-To: <518FD7B4.8070100@astro.umd.edu>


On 12 May 2013 at 13:56, Peter Teuben wrote:
| Patrick
| I agree, this is a useful option!
| 
|    can you say a little more here how you define robustness. The one I
| know takes the quartiles Q1 and Q3 (where Q2 would
| be the median), then define D=Q3-Q1 and only uses points between
| Q1-1.5*D and Q3+1.5*D to define things like  a robust mean and variance.
| Why 1.5 I don't know, I guess you could keep that a variable and tinker
| with it.
| For OLS you can imagine applying this in an iterative way to the Y
| values, since formally the errors in X are neglibable compared to those
| in Y. I'm saying iterative, since in theory the 2nd iteration could have
| rejected points that should have
| been part or the "core points".  For non-linear fitting this could be a
| lot more tricky.

There is an entire "task view" (ie edited survey of available packages)
available for R concerning robust methods (for model fitting and more):

   http://cran.r-project.org/web/views/Robust.html

So there is not just one generally accepted best option.  That said, having
something is clearly better than nothing. But let's properly define the
method and delineat its scope/

Dirk

-- 
Dirk Eddelbuettel | edd@debian.org | http://dirk.eddelbuettel.com

  reply	other threads:[~2013-05-12 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 22:01 Patrick Alken
2013-05-12 17:56 ` Peter Teuben
2013-05-12 18:13   ` Dirk Eddelbuettel [this message]
2013-05-12 18:14   ` Patrick Alken
2013-05-24 19:23 Timothée Flutre
2013-05-24 20:12 ` Patrick Alken

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=20879.56271.237184.255948@max.nulle.part \
    --to=edd@debian.org \
    --cc=gsl-discuss@sourceware.org \
    --cc=patrick.alken@Colorado.EDU \
    --cc=teuben@astro.umd.edu \
    /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).