par(mfrow=c(2,2))
y<-1:20
plot(y, pch="+")
plot(y, pch="+")
plot(y, pch="+")
plot(y, pch="+")
produces a pdf that is viewable in Preview (copied from the
clipboard) but fails to print.
pch default or ="." or =3 prints.
Unfortunately pch=3 doesn't fix the mfrow=c(5,6) graph that I'm
actua
On Mon, 7 Sep 2009, paul.m.mcguire...@att.net wrote:
No graphics device is specified here: which was it?
My guess is quartz() and that this is nothing to do with R but with
copying in Mac OS X from a quartz() window.
> par(mfrow=c(2,2))
> y<-1:20
> plot(y, pch="+")
> plot(y, pch="+")
> plot(y
Hello,
I am using "R CMD INSTALL --clean" so that when my package is finished
installed, a cleanup script is executed to post-process the generated
html index file and add some more information. The cleanup (or
cleanup.win script eventually calls the R code below)
This works well, but it dep
Hi,
this is perhaps not so much an issue, but as you are currently
working on the Rd parser anyway...
When you want to document specific S4 methods for an S4 generic
by \S4method{} within a \usage{} environment, and the second
(signature_list) argument is "long", be it because you use multiple
di
On 07/09/2009 7:27 AM, Peter Ruckdeschel wrote:
Hi,
this is perhaps not so much an issue, but as you are currently
working on the Rd parser anyway...
When you want to document specific S4 methods for an S4 generic
by \S4method{} within a \usage{} environment, and the second
(signature_list) arg
On Sat, Sep 05, 2009 at 08:31:18PM +0200, Peter Juhasz wrote:
> I don't understand how is this possible. Maybe there is an issue of
> thread-safety with the R backend, meaning that the two R *interpreter*
> instances are talking to the same backend that's capable of processing
> only one thing at
On Mon, Sep 07, 2009 at 05:36:38PM +0200, Peter Juhasz wrote:
> But please see http://www.perlmonks.org/index.pl?node_id=793907 ,
> where I posted my R code in its simplest form along with an example
> run which exhibits the symptoms I originally wrote about.
Ah, your two-process serialization is
Hi all,
Using character indexing on a vector is quite fast up through vector
length of 46340, then it suddenly it gets 3 orders of magnitude slower.
This is true at least of the special case in which the index vector is
the complete (though possibly out-of-order) set of vector names:
test <-
Many thanks to those (Martin Morgan, Duncan Murdoch) who tried to straighten
me out on ... arguments. It didn't work until I accidentally made two examples
I thought were the same but one worked and the other didn't. Finally I
achieved enlightenment. The following section has been added to the
h
