Dear all,
I was playing around with factor contrasts, and found the argument nmax on
function factor. When using nmax=1, R froze completely, and I had to close it
from task manager. After some debugging, I found that the problem is actually
in unique-function, where the internal unique function
> Gábor Csárdi
> on Tue, 29 Oct 2013 10:31:14 -0400 writes:
> Oh, you mean to put Matrix:: in the functions that need
> Matrix, right, of course. Then yes, this could be a
> solution. I have some issue with some new class
> definitions, but I can probably work them out
> Gábor Csárdi
> on Tue, 29 Oct 2013 10:31:14 -0400 writes:
> Oh, you mean to put Matrix:: in the functions that need
> Matrix, right, of course. Then yes, this could be a
> solution. I have some issue with some new class
> definitions, but I can probably work them out
I can reproduce this bug.
> sessionInfo()
R version 3.0.1 (2013-05-16)
Platform: i386-w64-mingw32/i386 (32-bit)
locale:
[1] LC_COLLATE=Dutch_Belgium.1252 LC_CTYPE=Dutch_Belgium.1252
LC_MONETARY=Dutch_Belgium.1252
[4] LC_NUMERIC=C LC_TIME=Dutch_Belgium.1252
attached base packa
R-developers:
I have a small python script that I'd like to include in an R package I'm
developing, but I'm a bit unclear about which subfolder it should go in. R
will be calling the script via a system() call. Thanks!
--j
--
Jonathan A. Greenberg, PhD
Assistant Professor
Global Environmental
On 30 October 2013 at 13:54, Jonathan Greenberg wrote:
| R-developers:
|
| I have a small python script that I'd like to include in an R package I'm
| developing, but I'm a bit unclear about which subfolder it should go in. R
| will be calling the script via a system() call. Thanks!
Up to you
On Oct 30, 2013, at 1:54 PM, Jonathan Greenberg wrote:
> R-developers:
>
> I have a small python script that I'd like to include in an R package I'm
> developing, but I'm a bit unclear about which subfolder it should go in. R
> will be calling the script via a system() call. Thanks!
>
> --j
Hi all,
Can anyone help me understand why an implicit print (i.e. just typing
df at the console), is so much slower than an explicit print (i.e.
print(df)) in the example below? I see the difference in both Rstudio
and in a terminal.
# Construct large df as quickly as possible
dummy <- 1:18e6
df
On Wed, Oct 30, 2013 at 6:22 PM, Hadley Wickham wrote:
> Hi all,
>
> Can anyone help me understand why an implicit print (i.e. just typing
> df at the console), is so much slower than an explicit print (i.e.
> print(df)) in the example below? I see the difference in both Rstudio
> and in a termin
Hadley,
As far as I can tell from a quick look, it is because implicit printing
uses a different mechanism which does a fair bit more work.
>From comments in print.c in the R sources:
* print.default() -> do_printdefault (with call tree below)
*
* auto-printing -> PrintValueEnv
*
The old convention was that it went in the exec/ directory, but as you
can see at
http://cran.at.r-project.org/doc/manuals/r-devel/R-exts.html#Non_002dR-scripts-in-packages
it can be in inst/anyName/. A minor convenience of exec/ is that the
directory has the same name in source and when insta
11 matches
Mail list logo