Displaying 20 results from an estimated 2000 matches similar to: "Summary: Warnings with no INDEX file in a package"
2001 Nov 06
1
R CMD check, undoc and package checking
As cool and wonderful as the package checking tools for R are, I sometimes am
stymied when trying to track down a problem. For example, I occasionally see
error messages when running R CMD check like the following:
[...]
* checking Rd files ... OK
* checking for undocumented objects ... ERROR
* in parse(file, n, text, prompt) : syntax error on line 932
* in undoc(dir =
2001 Oct 03
0
RE: [R] Several R vs S-Plus issues (PR#1112)
Also in assign() there some arguments lacking in R such as 'frame' and
'where', though I guess that 'frame' in S may be similar to 'pos' in R.
Harvey
-----Original Message-----
From: David Brahm [SMTP:a215020@agate.fmr.com]
Sent: Wednesday, October 03, 2001 11:36 AM
To: r-help@stat.math.ethz.ch
Cc: Kurt.Hornik@ci.tuwien.ac.at; r-bugs@r-project.org
Subject:
2002 May 14
0
FW: Summary of Suggestions for poor man's parallel processing
It turns out that my web host doesn't allow direct links. Try going to
http://www.warnes.net/downloads or getting it from the sourceforge snippet
library https://sourceforge.net/snippet/detail.php?type=snippet&id=101149.
-Greg
> -----Original Message-----
> From: Warnes, Gregory R [mailto:gregory_r_warnes at groton.pfizer.com]
> Sent: Monday, May 13, 2002 10:15 AM
> To:
2003 Jan 09
2
Warnings with no INDEX file in a package.
In previous versions of R (at least in 1.5.1, I think), my practice was not to
include an INDEX file in the package. R CMD check did not complain and an INDEX
was created for me when I use R CMD build.
At least, this is how I remember it. I thought that this was a good way to
behave since it ensured that my INDEX was automatically kept up to date by R,
without me having to worry about what
2001 Sep 13
1
rowsum dimnames
Hi,
The result of rowsum() in R doesn't have the dimnames I'd expect, e.g.:
> rowsum(matrix(1:12, 3,4), c("Y","X","Y"))
[,1] [,2] [,3] [,4]
1 2 5 8 11
2 4 10 16 22
whereas S-Plus gives the more useful result:
[,1] [,2] [,3] [,4]
X 2 5 8 11
Y 4 10 16 22
This is because R's rowsum() code gives
2001 Sep 14
1
rowsum dimnames (PR#1092)
The result of rowsum() in R doesn't have the dimnames I'd expect, e.g.:
> rowsum(matrix(1:12, 3,4), c("Y","X","Y"))
[,1] [,2] [,3] [,4]
1 2 5 8 11
2 4 10 16 22
whereas S-Plus gives the more useful result:
[,1] [,2] [,3] [,4]
X 2 5 8 11
Y 4 10 16 22
This is because R's rowsum() code gives the
2002 May 16
0
is.na() can coerce character vectors to be factors within a dataframe
Thanks to Brian Ripley for suggesting, to my previous post about a problem with
merge, that I trace through merge.data.frame. I did so with my test case and
all seemed to be well until I got to:
if (all.x)
for (i in seq(along = y)) is.na(y[[i]]) <- (lxy +
1):(lxy + nxx)
I believe that this code sets observations in y (which has been expanded to be the
2002 Oct 18
0
Correct placement of .tex files in an R package
I have a package in which I would like to store a LaTeX .tex file. It is not
documentation on any particular function, but is related to the package. In
thought that I could just create a "doc" directory under the "inst"
subdirectory and place it there. I thought that things in "inst" were just
recursively copied when the package was installed.
Alas, when I check the
2001 Nov 13
1
modification time warning with R CMD check
I often get warnings like the following when running R CMD check
[...]
* checking for code/documentation mismatches ... OK
* checking tests ...
make: *** Warning: File `Makevars' has modification time in the future (2001-11-13 12:54:37.381546042 > 2001-11-13 12:54:37.314975985)
[...]
I am ready to believe that this is not a bug (i.e., that the timing on my
various machines and file
2001 Oct 03
0
Several R vs S-Plus issues (PR#1110)
Hi, all,
I've been converting code from S-Plus ("S" for short) to R for a few weeks.
Here are some differences I've found, aside from the big well-known ones
(scoping, models, data storage) and the contents of Kurt Hornik's FAQ section
3.3.3. Let me start with the ones that seem like serious bugs or deficiencies:
1) LETTERS[c(NA,2)] in S is
2002 Jul 10
1
bug in all.equal.character (PR#1767)
There is a bug in all.equal.character:
> all.equal.character(c("A", "B", "C"), c("A", "B", "C"))
[1] TRUE
> all.equal.character(c("A", "B", "C"), c("A", "B", NA))
Error in sum(out) : Object "out" not found
> traceback()
3: sum(out)
2: paste("`is.NA' value
2002 May 20
1
(PR#1577) is.na<- coerces character vectors to be factors
The inconsistency is that you use $<- to set the column, then [[<- to
change it. Had you tried to set the column by
x[[1]] <- as.character(x[[1]])
you would have seen the problem immediately (it does not work as you would
have intended). If you want to be sure to turn off conversion to factor,
you need to set the column to class "AsIs". My belief is that
will behave
2001 Sep 27
5
Reading and writing to S-like databases
Hi,
I asked this question 2 years ago, and would like to know if the answer has
changed.
In S-Plus, I build databases of many large objects. In any given analysis,
I only need a few of those objects, but attach'ing the whole database is fine
since objects are only read as needed. How can I do the same thing in R,
without reading the entire database?
One possibility is to treat
2002 May 29
1
merge.data.frame can coerce character vectors to factor in some circumstances (PR#1608)
If the following two conditions are met:
1) all.x is TRUE
2) at least 1 row in y does not have a match in x
then any character vectors in y will be coerced to be factors. Here is a simple
example (previously provided on r-devel):
> x <- data.frame(a = 1:4)
> y <- data.frame(b = LETTERS[1:3])
> y$b <- as.character(y$b)
> z <- merge(x, y, by = 0, all.x = TRUE)
> z
2001 Sep 25
2
read.table() suggestions
Hi,
I understand work is being done to improve read.table(), especially by
Prof. Brian D. Ripley. I offer below a version that I wrote, in the hope some
aspects of it may prove useful or at least inspire discussion.
Be aware that my version differs in a couple fundamental ways that reflect
my aversion to dataframes and factors. So it returns a list of vectors which
are all character,
2001 Oct 03
8
Several R vs S-Plus issues
Hi, all,
I've been converting code from S-Plus ("S" for short) to R for a few weeks.
Here are some differences I've found, aside from the big well-known ones
(scoping, models, data storage) and the contents of Kurt Hornik's FAQ section
3.3.3. Let me start with the ones that seem like serious bugs or deficiencies:
1) LETTERS[c(NA,2)] in S is
2001 Oct 03
8
Several R vs S-Plus issues
Hi, all,
I've been converting code from S-Plus ("S" for short) to R for a few weeks.
Here are some differences I've found, aside from the big well-known ones
(scoping, models, data storage) and the contents of Kurt Hornik's FAQ section
3.3.3. Let me start with the ones that seem like serious bugs or deficiencies:
1) LETTERS[c(NA,2)] in S is
2009 Feb 04
3
auth_debug_passwords
Hi. I'm new to Dovecot and about to start using it in production. In
the config file, I set the option, auth_debug_passwords, to yes. I do
not see any failed passwords logged, however. It did cause more verbose
authentication logging, but failed passwords are still hidden.
I have also set these options to yes, because I thought they might be
required for auth_debug_passwords to work:
2005 Feb 16
1
config.status: error: cannot find input file: po/Makefile.in.in
The tarballs
R-devel_2005-02-16.tar.gz,
R-devel_2005-02-15.tar.gz and
R-devel_2005-02-14.tar.gz
all had the property that when I run ./configure on them I get the following
error message:
config.status: error: cannot find input file: po/Makefile.in.in
which terminates the configure script.
After R-devel_2005-02-15.tar.gz was posted but before R-devel_2005-02-16.tar.gz
was posted, Jeff Gentry
2002 Aug 13
2
Word and samba
Greetings Group
I think the Word crashing problem is quite common and does not confine
itself to Samba as PDC. Running Word with any file open on a Samba server
seems to invite trouble and file trashing.
This seems to more of a problem with Win2000 and XP than Win9X and NT. I
suspect that Micorsoft have "improved" the code to "optimise" performance
for Micorsoft