Your suggestions worked ok in the example, but in my case there is yet another
package that implements a plot method.
Now the plotting from within the package works, but plotting from outside the
package, on the console, gives an error as if plot.default is invoked.
> class(myplot)
[1] "gt.barplo
Full_Name:
Version: 3.2.1
OS: RHEL AS 4.0 update 4
Submission from: (NULL) (151.152.101.44)
Error in make check:
running code in 'reg-tests-1.R' .../bin/sh: line 1: 9538 Segmentation fault
LC_ALL=C SRCDIR=. R_DEFAULT_PACKAGES= ../bin/R --vanilla reg-tests-1.Rout 2>&1
make[3]: *** [reg-tes
Ioannis Dimakos wrote:
> Forgive me for being naive,
>
> but I have not seen any reference where the ISBN was required. The apa
> style that I use does not require the ISBN.
>
> Best,
>
> Ioannis
You can put that part in note field as it is done in output of
citation() function.
--
Lep pozdr
On 9/11/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> On Mon, 11 Sep 2006, Deepayan Sarkar wrote:
>
> > Hi,
> >
> > I know S manuals used to warn against using the same names for a
> > variable and a function, but I have never seen that cause problems in
> > R, so I usually don't pay much atte
Forgive me for being naive,
but I have not seen any reference where the ISBN was required. The apa
style that I use does not require the ISBN.
Best,
Ioannis
=
On Tue, Sep 12, 2006 16:22, Gregor Gorjanc wrote:
> Friedrich Leisch wrote:
>>> On Tue, 12 Sep 2006 07:53:52 +0200,
>>> Gre
valgrind solves this:
> plot(x, y, col = aFactor)
==10339== Invalid write of size 4
==10339==at 0x4F70CE: Rf_FixupCol (plot.c:354)
==10339==by 0x4FC124: do_plot_xy (plot.c:1554)
==10339==by 0x4D75DC: do_internal (names.c:1094)
==10339==by 0x499C05: Rf_eval (eval.c:431)
==10339==
Thank you, Bjørn-Helge.
A shorter version is
plot(1:500, col = gl(2,250))
Interestingly, with much shorter vectors of length (n), the correct warning
is produced (n times).
And once that has happened, you can use longer vectors without
any problem.
As you said ``issued just after starting R''
After the following commands (issued just after starting R)
set.seed(1)
n <- 600
x <- rnorm(n)
y <- rnorm(n)
aFactor <- factor(rep(1:5, length = n))
plot(x, y, col = aFactor)
R prints
*** caught segfault ***
address 0x10, cause 'memory not mapped'
Segmentation fault
and dies.
(Yes, I know tha
Uwe Ligges <[EMAIL PROTECTED]> writes:
> Currently, the main problems with many packages are missing *recent*
> binaries (after the latest S4 changes) of BioC packages, hence many
> dependencies may not be working. I do not want to compile the whole BioC
> repository as well.
The Bioconductor b
Full_Name: Chris Andrews
Version: 2.3.1
OS: Windows
Submission from: (NULL) (128.205.253.147)
?mcnemar.test
ends with an example:
## Agresti (1990), p. 350.
## Presidential Approval Ratings.
## Approval of the President's performance in office in two surveys,
## one month
Friedrich Leisch wrote:
>> On Tue, 12 Sep 2006 07:53:52 +0200,
>> Gregor Gorjanc (GG) wrote:
>
> > Hello!
> > I keep my local bib file and up to now I had entry
>
> > @Manual{R:2003,
> > title = {R: A Language and Environment for Statistical Computing},
> > author = {{
compiler/platform?
I did this:
R CMD SHLIB helloworld.cpp
Then this in R:
> dyn.load("helloworld.so")
> .Call("helloworld")
and it doesn't segfault. (x86_64 linux with 32-bit R).
Tom McCallum wrote:
> Hi everyone,
>
> I have been attempting to build a very simple R package interfacing with
On Tue, 12 Sep 2006, Tom McCallum wrote:
> Hi everyone,
>
> I have been attempting to build a very simple R package interfacing with
> some very simple C++ code. Everything I try though results in the
> function working but on return it produces a memory error. Here is the
> output:
>
>
Hi everyone,
I have been attempting to build a very simple R package interfacing with
some very simple C++ code. Everything I try though results in the
function working but on return it produces a memory error. Here is the
output:
***OUTPUT***
> library(My
> "MM" == Martin Maechler <[EMAIL PROTECTED]>
> on Tue, 12 Sep 2006 08:56:41 +0200 writes:
> "BDR" == Prof Brian Ripley <[EMAIL PROTECTED]>
> on Mon, 11 Sep 2006 22:25:58 +0100 (BST) writes:
BDR> At least some of this will go away if you use a current
BDR
Thank you for the interest in my problem.
>From the questions I see I forgot to provide some
vital information, for which I am sorry.
Based on the question Uwe Ligges, I scrutinized
my PATH settings and saw that my system administrators
included a reference to a Cygwin installation (which
caused p
> On Tue, 12 Sep 2006 07:53:52 +0200,
> Gregor Gorjanc (GG) wrote:
> Hello!
> I keep my local bib file and up to now I had entry
> @Manual{R:2003,
> title = {R: A Language and Environment for Statistical Computing},
> author = {{R Development Core Team}},
> organ
Prof Brian Ripley wrote:
> At least some of this will go away if you use a current version of 2.4.0
> alpha rather than one that is a week old (as the posting guide does ask).
> We are now at r39258, and some of those binary packages were built against
> a substantially later version of 2.4.0
> "BDR" == Prof Brian Ripley <[EMAIL PROTECTED]>
> on Mon, 11 Sep 2006 22:25:58 +0100 (BST) writes:
BDR> At least some of this will go away if you use a current
BDR> version of 2.4.0 alpha rather than one that is a week
BDR> old (as the posting guide does ask). We are now
Hi
R version 2.4.0 alpha (2006-09-06 r39158)
MacOSX 10.4.7
There was a thread some time ago as to whether the structure created by
package.skeleton() would pass R CMD check.
I have an example where package.skeleton() gives an R file that gives an
error when sourced.
If I type
setClass("brob
20 matches
Mail list logo
