You can close the x11() device using dev.off() in your example. You
may also want to look at interactive() so you can test in your example
is the code is run interactively or not; the latter is the case for R
CMD check.
/H
On 9/25/06, Dominick Samperi <[EMAIL PROTECTED]> wrote:
> One of my demos
Ross Boylan <[EMAIL PROTECTED]> writes:
> The code has a couple of decisions for which I could imagine
> alternatives. First, even simple get/set operations on class elements
> are wrapped in functions. I suppose I could just use [EMAIL PROTECTED] to
> do some of these operations, though that is
Full_Name: Otto Shtirlitz
Version: 2.3.1
OS: Win XP SP2
Submission from: (NULL) (71.102.102.246)
I believe it's the same situation as described in bug 9248. R script editor
cannot open file exceeding 1000 characters even if created in the same editor.
File is
all ANSI with symbols < 128 and with
One of my demos runs x11() so that I can resize the
window and avoid the "too large for margins" message
from plot. This seems to have a problematic side
effect.
When I run R CMD check on the package that demo
is displayed, because it appears as an example in
one of the man pages, and after this h
On Tue, 2006-09-26 at 00:20 +, Ross Boylan wrote:
> I have a small S4 class for which I've written a page grouping many of
> the accessors and replacement functions together. I would be interested
> in people comments on the approach I've taken.
>
> The code has a couple of decisions for whic
I have a small S4 class for which I've written a page grouping many of
the accessors and replacement functions together. I would be interested
in people comments on the approach I've taken.
The code has a couple of decisions for which I could imagine
alternatives. First, even simple get/set oper
Hello!
In my opinion read.fwf()'s behaviour of header is not really useful. Say
I have the following data:
col1 col2 col3
123 123 123
a b
123412 1234
65.4 4.5
Now if I want to read this data into R I can not use read.table due to
missing fields.
read.table(file=
Hello!
na.encode does not have any effect on format of NA values of Date and
POSIXct (POSIXlt?) "atomic" classes in a data.frame. Here is the example
(the same in R 2.3.1 and 2.5.0 (2006-09-19 r39409)):
testData <- data.frame(num=c(NA, 2.6),
int=c(1, NA),
This is fron R-2.5.0-to-be, windows XP
The following excerpt from ?asin cannot be right:
For asin() and acos(), there are two cuts, both along the real axis: *(-Inf,
1]* and *[1, Inf)*. Functions asin() and acos() are continuous from above on
the interval *(-Inf, -1]* and continuous from below on
Doug
I do indeed have a Makevars file after all. Thanks for spelling out the
interpretation of the warning message.
Paul
Douglas Bates wrote:
> On 9/25/06, Paul Gilbert <[EMAIL PROTECTED]> wrote:
>> I am still confused about this (and it is still happening with R-beta).
>> Writing R Extensions s
On 9/25/06, Paul Gilbert <[EMAIL PROTECTED]> wrote:
> I am still confused about this (and it is still happening with R-beta).
> Writing R Extensions suggests I need a Makefile or Makevars in my
> package, but that has not been the case previously. Is there now a
> requirement that all packages ne
Christoph,
This is more complicated than your analysis.
1) apply takes a matrix as an argument, not a data frame, and so first
coerced 'dat' to a character matrix.
2) unlist is working quite correctly. The issue is array(), which
contains as.vector(data). Thus although the result could be a
I am still confused about this (and it is still happening with R-beta).
Writing R Extensions suggests I need a Makefile or Makevars in my
package, but that has not been the case previously. Is there now a
requirement that all packages need Makefiles or Makevars if there is
fortran to be compiled
> Dear,
> I have developed and tested some models in soil
> hydrology with NLME library in R. I want to ask
> if it could be possible to submit this to the NLME
> library (with sample data) as a toolbox or something
> so
> that anyone downloading new components of new
> versions
> of R may simply c
Dear R-core
There is a different output for the apply function due to the
change of unlist as mentioned in the R news.
Newly, applying as.factor() (or factor()) in
str(dat <- data.frame(x = 1:10, f1 = gl(2,5,labels = c("A", "B"
(d1 <- apply(dat,2,as.factor))
newly returns a character matrix
Peter Dalgaard <[EMAIL PROTECTED]> writes:
> This is *not* a bug (it is also not a FAQ, although I'm beginning to
> think it should be).
Just to be clear: I'm aware of FAQ 7.8, but it is about file names.
Issue is whether we need a generic "backslashes in text strings"
entry.
--
O__
[EMAIL PROTECTED] writes:
> Full_Name: Michael Bauer
> Version: 2.3.1
> OS: Mac OS X 10.4.7
> Submission from: (NULL) (131.130.124.155)
>
>
> > sessionInfo()
> Version 2.3.1 (2006-06-01)
> powerpc-apple-darwin8.6.0
>
> attached base packages:
> [1] "methods" "stats" "graphics" "grDevic
On Mon, 25 Sep 2006, [EMAIL PROTECTED] wrote:
> Full_Name: Michael Bauer
> Version: 2.3.1
> OS: Mac OS X 10.4.7
> Submission from: (NULL) (131.130.124.155)
>
>
>> sessionInfo()
> Version 2.3.1 (2006-06-01)
> powerpc-apple-darwin8.6.0
>
> attached base packages:
> [1] "methods" "stats" "graph
Full_Name: Michael Bauer
Version: 2.3.1
OS: Mac OS X 10.4.7
Submission from: (NULL) (131.130.124.155)
> sessionInfo()
Version 2.3.1 (2006-06-01)
powerpc-apple-darwin8.6.0
attached base packages:
[1] "methods" "stats" "graphics" "grDevices" "utils"
[6] "datasets" "base"
>
spr
19 matches
Mail list logo
