Full_Name: Andrew Robinson
Version: 2.6.2 Patched (2008-02-12 r44439)
OS: FreeBSD 6.3-RC1
Submission from: (NULL) (211.28.206.186)
I believe that the computation for GCV is incorrect in the lm.ridge function in
MASS.
>From lm.ridge:
GCV <- colSums((Y - X %*% coef)^2)/
(n - colSums(matrix(d
You are of course right, library(tools) is not necessary.
Duncan Murdoch wrote:
> On 09/02/2008 6:44 PM, Erich Neuwirth wrote:
>> I think Rprofile.site as installed with R-2.6.2
>> contains some misleading information.
>> It contains the following lines
>>
>> # set a CRAN mirror
>> # local({r <- g
Hello all,
I've developed a prototype package called PopCon (short for popularity
contest), a package for tracking the popularity of R and its packages.
I'd like this work to be similar in spirit to the Debian package
popularity-contest: http://popcon.debian.org/.
Once Popcon is loaded, it cap
On Thu, 14 Feb 2008, Paul Murrell wrote:
> Hi
>
>
> Erik Iverson wrote:
>> Hello -
>>
>> If I create multiple pieces of output in grid, and use grid.remove() to
>> try to remove the output from the graphics device, I cannot seem to
>> remove the final piece of output from the device until I 'refre
> Prof Brian Ripley writes:
> The R front end sets (via etc/ldpath) R_LIBRARY_PATH, including
> R_JAVA_LD_LIBRARY_PATH. Perhaps the later is too obliging, as I've just
> be caught by it in a way that took me a while to track down.
> One of my machines has a Sun jdk1.6.0* JDK installed, and
On 2/13/08, Deepayan Sarkar <[EMAIL PROTECTED]> wrote:
> On 2/13/08, Wolfgang Huber <[EMAIL PROTECTED]> wrote:
> > Hi Deepayan,
> >
> > levelplot from the lattice package produces a peculiar output when
> > called on a matrix whose column or row names contained duplicated
> > elements. In particula
On 2/13/08, Wolfgang Huber <[EMAIL PROTECTED]> wrote:
> Hi Deepayan,
>
> levelplot from the lattice package produces a peculiar output when
> called on a matrix whose column or row names contained duplicated
> elements. In particular, the plot contains white stripes, and the
> arrangement of data r
On Feb 13, 2008 11:07 AM, Paul Gilbert <[EMAIL PROTECTED]> wrote:
> I think in general it is a good idea to use on.exit() to reset the
> seed if you mess with it. Otherwise you can generate unintended
> consequences for other programs. Something like:
> old.seed <- setRNG(kind = "default", se
Hi
Erik Iverson wrote:
> Hello -
>
> If I create multiple pieces of output in grid, and use grid.remove() to
> try to remove the output from the graphics device, I cannot seem to
> remove the final piece of output from the device until I 'refresh' the
> graphics device by giving it focus. The
I think in general it is a good idea to use on.exit() to reset the
seed if you mess with it. Otherwise you can generate unintended
consequences for other programs. Something like:
old.seed <- setRNG(kind = "default", seed = test.seed, normal.kind =
"default")
on.exit(setRNG(old.seed))
Hello -
If I create multiple pieces of output in grid, and use grid.remove() to
try to remove the output from the graphics device, I cannot seem to
remove the final piece of output from the device until I 'refresh' the
graphics device by giving it focus. The function grid.remove() does
appear t
When is this really necessary? I have seen functions that do this, I
have never seen any usage where I think it is necessary. Usually it
is because the functions do say mcmc or cross-validation and wants
repeatable behaviour. But if the user really wants that, he/she can
just do it outside
On Feb 13, 2008 9:32 AM, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> On Wed, 13 Feb 2008, Henrik Bengtsson wrote:
>
> > Hi,
> >
> > this is related to a question just raised on Bioconductor where one
> > function sets the random seed internally but never resets it, which
> > results in enforced
On Wed, 13 Feb 2008, Henrik Bengtsson wrote:
> Hi,
>
> this is related to a question just raised on Bioconductor where one
> function sets the random seed internally but never resets it, which
> results in enforced down streams random samples being deterministic.
>
> What is the best way to reset
Hi,
this is related to a question just raised on Bioconductor where one
function sets the random seed internally but never resets it, which
results in enforced down streams random samples being deterministic.
What is the best way to reset the random seed when you use set.seed()
within a function?
Hi Deepayan,
levelplot from the lattice package produces a peculiar output when
called on a matrix whose column or row names contained duplicated
elements. In particular, the plot contains white stripes, and the
arrangement of data regions and axes labels seems messed up. I did not
see this docume
On 13-Feb-08 12:40:48, Barry Rowlingson wrote:
> hadley wickham wrote:
>
>> It's more than that as though, as floating point addition is
>> no longer guaranteed to be commutative or associative, and
>> multiplication does not distribute over addition. Many concepts
>> that are clear cut in pure ma
:) Well, yes, but what do you do with a named vector if you want to
remove an element by name?
It is not general: you cannot do that on vectors, matrices, arrays and
all inherited objects anyway. Using a negative index is a standard and
throughout practice of deleting elements in R. Surely one
hadley wickham wrote:
> It's more than that as though, as floating point addition is no longer
> guaranteed to be commutative or associative, and multiplication does
> not distribute over addition. Many concepts that are clear cut in
> pure math become fuzzy in floating point math - equality, sin
But what about by name?
a <- list(a = 1, b = 2, c = 3)
a$b <- NULL
On Feb 13, 2008 9:39 AM, Oleg Sklyar <[EMAIL PROTECTED]> wrote:
> Hmm, I think the pretty traditional R style does the job...
>
> a = list(1,2,3)
> a[-2]
>
> So I really do not see a good reason for doing a[2] = NULL instead of
Hmm, I think the pretty traditional R style does the job...
a = list(1,2,3)
a[-2]
So I really do not see a good reason for doing a[2] = NULL instead of a
= a[-2]
Jeffrey J. Hallman wrote:
>>From your tone, I gather you don't much like this behavior, and I can see your
> point, as it not very in
The R front end sets (via etc/ldpath) R_LIBRARY_PATH, including
R_JAVA_LD_LIBRARY_PATH. Perhaps the later is too obliging, as I've just
be caught by it in a way that took me a while to track down.
One of my machines has a Sun jdk1.6.0* JDK installed, and as a result
we have
${R_JAVA_LD_LIBRARY
On Wed, 13 Feb 2008, Heikki Kaskelma wrote:
> hadley wickham:
>> It's more than that as though, as floating point addition is no longer
>> guaranteed to be commutative or associative, and multiplication does
>> not distribute over addition. Many concepts that are clear cut in
>> pure math become
On 2/13/2008 3:27 AM, Gerhard Thallinger wrote:
> Hi Duncan,
>
>>> I just wanna add a related suggestion that when you have multiple
>>> installations and you run "Unistall R 2.6.0" the first dialog
>>> ('R for Windows Uninstall') you see says "Are you sure you want to
>>> completely remove R for
Hi Duncan,
>> I just wanna add a related suggestion that when you have multiple
>> installations and you run "Unistall R 2.6.0" the first dialog
>> ('R for Windows Uninstall') you see says "Are you sure you want to
>> completely remove R for Windows and all of its components?" This
>> message do
hadley wickham:
> It's more than that as though, as floating point addition is no longer
> guaranteed to be commutative or associative, and multiplication does
> not distribute over addition. Many concepts that are clear cut in
> pure math become fuzzy in floating point math - equality, singularit
Dear all,
there are a few issues regarding Section 2.5: Sub-architectures in the
R Installation and Administration manual (referring to Version 2.6.2)
that I would like to raise:
1.) The manual states:
@code{R CMD INSTALL} will detect if more that one build is installed
and try to insta
27 matches
Mail list logo
