Full_Name: Sigbert Klinke
Version: 2.1.1
OS: Suse Linux 10.0 (Full DVD)
Submission from: (NULL) (141.20.100.252)
Suse 10.0 installs only a Fortran 95 compiler with g77 compability mode. Using
this leads in "configure" to an abortion with problems about "FPICFLAGS".
Deinstalling g77 compatiblity m
I am afraid
1) This is a message about an outdated version of R, and
2) The problem is most likely the compiler and the way it (mis)compiles
src/modules/lapack/dlamc.f. This is covered in the R-admin manual (which
INSTALL asked you to read). This said in 2.1.1
It seems that @samp{gcc 3.4.
[EMAIL PROTECTED] writes:
> Suse 10.0 installs only a Fortran 95 compiler with g77 compability mode. Using
> this leads in "configure" to an abortion with problems about "FPICFLAGS".
> Deinstalling g77 compatiblity mode, using f2c, compiles R. But after calling
> R()
> the program shows its entra
(Moved from R-help).
This comes up often enough that I'm starting to think most functions
that take filename arguments should have file.choose() as the default
value. Then one could do
read.table()
and have a dialog box pop up in Windows, or some other prompt for a
filename in other platform
There is a fairly new bug in wilcox.test in R-2.2.1 (stable).
It wasn't there when I last taught nonparametrics in fall 2003.
Line 86 of wilcox.test.R
achieved.alpha<-2*psignrank(trunc(qu),n)
It should be
achieved.alpha<-2*psignrank(trunc(qu)-1,n)
If you don't see why, decode the cookb
Full_Name: Greg Kochanski
Version: 2.2.1
OS: Debian Linux (testing)
Submission from: (NULL) (212.159.16.190)
In writing class notes to teach people how to use R, I came across
a design failure of dataentry().
It seems that if you add a new value outside the bounds of an array,
dataentry() fills
I would argue against this.
If this were the default, that is requiring user interaction, it would
break a fair amount of code that I (and I am sure a lot of others have)
where automation is critical.
A lot of the issues seem to be user errors, file permission errors,
hidden extensions as is poin
On 1/29/2006 12:55 PM, Marc Schwartz wrote:
> I would argue against this.
>
> If this were the default, that is requiring user interaction, it would
> break a fair amount of code that I (and I am sure a lot of others have)
> where automation is critical.
I don't see how this change could affect a
Full_Name: Greg Kochanski
Version: 2.2.1
OS: Debian Linux (testing)
Submission from: (NULL) (212.159.16.190)
This is really a feature request.
When you do mosaicplot() on a data set where the probability of
several nearby rows is small, then the labels for those
rows are plotted overlapping each
On Sun, 29 Jan 2006, Marc Schwartz wrote:
I would argue against this.
If this were the default, that is requiring user interaction, it would
break a fair amount of code that I (and I am sure a lot of others have)
where automation is critical.
I don't see how. The current default is
read.ta
Full_Name: Greg Kochanski
Version: 2.2.1
OS: Debian Linux (testing)
Submission from: (NULL) (212.159.16.190)
mosaicplot(x, shade=TRUE) is intended to color the blocks
blue if they are more common than one might expect
and red if they are rarer than one might expect.
Unfortunately, if a block is
Duncan,
OK. I mis-understood the proposal. My error.
Thanks for the clarification.
Marc
On Sun, 2006-01-29 at 13:08 -0500, Duncan Murdoch wrote:
> On 1/29/2006 12:55 PM, Marc Schwartz wrote:
> > I would argue against this.
> >
> > If this were the default, that is requiring user interaction, i
On 1/29/2006 1:29 PM, Prof Brian Ripley wrote:
> On Sun, 29 Jan 2006, Marc Schwartz wrote:
>
>> I would argue against this.
>>
>> If this were the default, that is requiring user interaction, it would
>> break a fair amount of code that I (and I am sure a lot of others have)
>> where automation is
On 1/29/2006 1:24 PM, Gabor Grothendieck wrote:
> Normally one expects stdin to be the default on command line
> programs and something like file.choose to be the default on GUI
> programs and this would break that expectation.
We don't currently meet that expectation, so I don't think it would
On 1/29/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 1/29/2006 1:24 PM, Gabor Grothendieck wrote:
> > Normally one expects stdin to be the default on command line
> > programs and something like file.choose to be the default on GUI
> > programs and this would break that expectation.
>
> We
On 1/29/2006 5:20 PM, Gabor Grothendieck wrote:
> On 1/29/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
>> On 1/29/2006 1:24 PM, Gabor Grothendieck wrote:
>> > Normally one expects stdin to be the default on command line
>> > programs and something like file.choose to be the default on GUI
>> >
The bibtex citations provided by citation() do not
work all that well in cases where there is no printed
document to reference:
(1) A version field is needed, as the note field is
required for other purposes, currently trying to
sort out nuances that cannot be sorted out in the
author list (author,
On 1/29/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> On 1/29/2006 5:20 PM, Gabor Grothendieck wrote:
> > On 1/29/06, Duncan Murdoch <[EMAIL PROTECTED]> wrote:
> >> On 1/29/2006 1:24 PM, Gabor Grothendieck wrote:
> >> > Normally one expects stdin to be the default on command line
> >> > program
I would like to bring to your attention the following error message
which didn't appear on previous versions (long time ago?)
Thanks for all your effort
Karl
Version 2.2.1 Patched (2006-01-21 r37153)
> f <- rep(c(1,2),each=5)
> x <- tapply(f,f,sum)
> colnames(x)
Error in dn[[2]] : subscript
19 matches
Mail list logo
