Closely related to the different QR variations, Claudia Beleites and I
have a very crude start on some attempts to categorize different svd
approaches in R. Perhaps it's worth combining efforts with QR because of
the overlap and producing a sort of enlarged vignette or even a Task
View. I suggest c
Thanks for the input Peter. I suppose I never looked at lm() to see how it
was used there. Given that though, do you see any reason then to not
create an S3/S4 method if different methods are used for different
functions? I'm just looking for some design guidance from the community
here before I
Not strictly what you're asking, but at some point it may be important to note
that the "QR" method used by lm() and friends (notably anova() and aov())
actually relies on successive orthogonalization. This does yield a QR
decomposition but the reverse is not true. A generic X=QR decomposition d
Hello,
I am currently working on an implementation of QR decomposition (leveraging
a C++ library via Rcpp). Naturally I would like to have the R syntax as
similar as possible to base R 'qr' function. Given the class structure of
my package my instinct was to export an S4/S3 method.
However, the
