Displaying 20 results from an estimated 3000 matches similar to: "(PR#1558)"
2002 May 15
0
(PR#1558) language: bug or feature: vector-subscript of
On Wed, 15 May 2002 mark.bravington@csiro.au wrote:
> Full_Name: Mark Bravington
> Version: R1.3.1 & R1.5.0
> OS: Windows 2000
> Submission from: (NULL) (140.79.2.3)
>
>
> R doesn't like the use of subscripts with length > 1, to get into recursive
> lists:
>
> > listio_ list( a=list( b=9, c='hello'), d=1:5)
> > listio[[ c( 1, 2)]]
>
2003 Jan 30
2
print.default and attributes
When something gets printed by the "print.default" function, any extra
attributes are printed without regard to their class attribute (if any). For
example:
> x <- 1:3
> attr( x, 'other') <- factor( c( 'cat', 'dog'))
> attr( x, 'other')
[1] cat dog
Levels: cat dog
> x
[1] 1 2 3
attr(,"other")
[1] 1 2
which is perhaps
2001 Jul 13
6
AnonCVS
Hi All,
I would like to use anonymous cvs, but it appears not to be working
(again?). There was a discussion back in Jan-Feb about whether to
continue supporting it, but it seemed that Tony Rossini got it working
and the discussion left off there. Did someone decide to disable it, or
is it just not working properly?
Here's the details:
$ cvs -d
2003 Sep 24
1
getAnywhere (PR#4275)
'getAnywhere' is not reporting methods when there are periods in the class name or the generic name
(in R-devel).
> getAnywhere( 'predict.loess')
A single object matching 'predict.loess' was found
It was found in the following places
registered S3 method for predict from namespace modreg
namespace:modreg
with value
<<...>>
> getAnywhere(
2002 Aug 30
5
density() returns a density function that does not add up to 1
Dear R users,
I ran into this curious problem:
> d <- rnorm(100)
> d.density <- density(d)
> sum( d.density$x * d.density$y)
[1] 2.517502
Admittedly the method of computing the mass under the density curve at
line 3 is crude.
But 2.5 is pretty far from 1, the value it should be.
I tried a few other dataset and got similar result. Am I missing
something obvious?
Or is the return
2002 Oct 21
1
savehistory directories and quitting R (PR#2038)
Thanks-- as Duncan Murdoch also noted, R_HISTFILE can be used to solve my
problem, as below. BTW it's not easy to find out about R_HISTFILE in the
help system or manuals, though, unless you already know it exists-- it only
seems to be described under startup options, not things to do with history.
However, Duncan's reply did hint at an inconsistency, in that savehistory()
defaults to
2002 Dec 27
1
Wish list: add an "until" or "EOF.marker" parameter to scan & rea dLines
A bit late for Santa, but on my wish-list nevertheless:
is there any chance that "scan" and "readLines" could be extended to take a
parameter "until" or "EOF.marker", which would be a character string that
(if encountered while reading) would cause the reading to stop, just as if
an end-of-file had been found? [But leaving a connection open, so that
2002 Jul 02
4
XEmacs vs. GNU Emacs?
As a user of only R, I don't use much of the potential of ESS and Emacs.
Without entering a religious feud, is there any reason I should use XEmacs
rather than my current GNU Emacs?
(I looked on the XEmacs site, but I didn't understand the programming
issues they were talking about (over my head).)
Martin Henry H. Stevens, Assistant Professor
338 Pearson Hall
Botany Department
Miami
2008 Nov 10
3
how to stop without error message?
Dear list
Can anyone suggest a simple way to abort execution like stop(...) does, but without issuing an "Error: ..." message?
I don't want to set 'options( show.error.messages=TRUE)' because I want normal behaviour to resume after this particular stop.
(Please reply personally as well as to the list, as I'm not subscribed to R-help)
Thanks
Mark
--
Mark Bravington
2004 Sep 08
3
having trouble building r-devel
Dear R-devel
On my Windows 2000 machine, I can build R-patched but not R-devel (since at least 1/9/2004). An error message pops up during the execution of some R code during "make", as below. In terms of "make" etc., I am totally clueless (not being a user of either Linux or C) and just mechanically follow the instructions in the R documentation; hence I've got no idea
2002 Nov 20
2
restart
Dear group
I use "restart" in part of my code, in a way that's not easily changed to
"try". As I convert code from R1.5.0 to R1.6.1, I'm getting ugly messages;
the help system says to contact r-devel, so here I am. This one's a bit
complicated-- sorry!
The context is inside a debugger (I have an R and S debugger that offers
stand-alone code windows, line numbered
2003 Mar 26
5
predict (PR#2686)
# r-bugs@r-project.org
`predict' complains about new factor levels, even if the "new" levels are
merely levels in the original that didn't occur in the original fit and were
sensibly dropped, and that don't occur in the prediction data either. (At
least if `drop.unused.levels' was set to TRUE, which the default.)
test> scrunge.data.2_ data.frame( y=runif( 3),
2002 Aug 09
2
error starting SJava: classpath
Dear R experts,
Sorry, I am resending this, since I have not received this mail myself for
the past 5 hours.
I saw a similar question dated July 2. But there is no answer to it. Does
anybody have a solution to it?
I am using window NT, and the R version is 1.5.1, the SJava package is the
binary version SJavaWin_0.62-8.zip.
Here are the error message:
> library(SJava)
> .JavaInit()
2003 Mar 26
2
predict (PR#2685)
There is a bug in `predict' whereby the order of variables sometimes gets
re-arranged compared to the original fit, and then disaster results.
Specifically, the 'variables' and 'predvars' attributes of a 'terms' object
get out of synch. This only happens when the terms in the original formula
get re-ordered during fitting:
test> scrunge.data_ data.frame(
2002 Apr 08
4
Missing data and Imputation
Hi Folks,
I'm currently looking at missing data/imputation
methods (including multiple imputation).
S-Plus has a "missing data library".
What similar resources are available within R?
Or does one roll one's own?
Best wishes to all,
Ted.
--------------------------------------------------------------------
E-Mail: (Ted Harding) <Ted.Harding at nessie.mcc.ac.uk>
2011 Sep 16
1
grep problem in R-devel 2.14 r57004
Problem below with PCRE grep in R-devel; works fine in R-patched. (Unless there's been an absolutely massive change in rules for updated PCRE version 8.13; jeez I hope not)
> grep( '[.][.]', '', perl=TRUE)
Error in grep("[.][.]", "", perl = TRUE) :
invalid regular expression '[.][.]'
In addition: Warning message:
In grep("[.][.]",
2002 Jun 30
4
modifying a vector
Hello everyone,
Thanks to all who offered suggestions after my initial query to the list.
I've been busy trying to absorb the docs as fast as possible, but this
little thing has me stumped for the moment.
I'm creating a random sample of 100 item and saving it to a vector named
'iq'. I'd like to create a second vector (iq_prime, say) by adding 20 to
each element of the
2002 Jun 30
4
modifying a vector
Hello everyone,
Thanks to all who offered suggestions after my initial query to the list.
I've been busy trying to absorb the docs as fast as possible, but this
little thing has me stumped for the moment.
I'm creating a random sample of 100 item and saving it to a vector named
'iq'. I'd like to create a second vector (iq_prime, say) by adding 20 to
each element of the
2002 Nov 27
5
further on ESS/XEmacs for Windows
Dear list members,
I've had helpful feedback from a number of people, several of whom
experienced some problems getting my XEmacs/ESS configuration files for
Windows to work properly. I will, of course, make changes based on this
feedback, but the following information may be of use in the interim:
(1) It's clear that my instructions and installation procedure were
insufficiently
2002 Nov 27
5
further on ESS/XEmacs for Windows
Dear list members,
I've had helpful feedback from a number of people, several of whom
experienced some problems getting my XEmacs/ESS configuration files for
Windows to work properly. I will, of course, make changes based on this
feedback, but the following information may be of use in the interim:
(1) It's clear that my instructions and installation procedure were
insufficiently