|
12h
|
|
comment |
Create R Windows Binary from .tar.gz linux For example, Jeffrey Horner no longer maintains Windows binaries of RMySQL, but when I compile from source on my own Windows box, it works just fine... |
|
12h
|
|
comment |
Create R Windows Binary from .tar.gz linux @BenBolker -- Agreed. I just came back here to note +/- the same thing (although I've got limited experience of whether compiled packages can fail some of CRAN's checks, but still be practically useful). Do you happen to know what r-oldrel-windows-ix86+x86_64 (one of the architectures referenced on bigmemory's check results page) is, and how it differs from r-release-windows-ix86+x86_64 included (e.g.) here?
|
|
12h
|
|
answered | Create R Windows Binary from .tar.gz linux |
|
14h
|
|
comment |
logical test if object is a directory @TylerRinker -- Glad that helped. Rather than trying to memorize all of R's file-related functions, I often find myself doing apropos("^file"). It misses some, but gives a good starting list ;)
|
|
20h
|
|
revised |
The arcane formals(function(x){})$x added 50 characters in body |
|
20h
|
|
revised |
The arcane formals(function(x){})$x added 136 characters in body |
|
20h
|
|
revised |
The arcane formals(function(x){})$x added 149 characters in body |
|
20h
|
|
answered | The arcane formals(function(x){})$x |
|
21h
|
|
comment |
logical test if object is a directory As for how file.info really works, that's in the C function called by .Internal(file.info), do_fileinfo -- but I'm guessing (?) that that's not what you're actually wanting...
|
|
21h
|
|
answered | logical test if object is a directory |
|
1d
|
|
answered | strange jags.parallel error / avoiding lazy evaluation in function call |
|
1d
|
|
comment |
Manually defining the colours of a wireframe Probably not worth posting untested wild-assed guesses that, if I understood it correctly, were reported later in the thread to not have worked out ;). If it actually does somehow work, could you show us how? |
|
1d
|
|
comment |
Manually defining the colours of a wireframe Unfortunately, this looks ungodly difficult to accomplish in lattice. The rendering of 3-D objects is the one part of the package that uses a C-level function ( wireframePanelCalculations, in latticePackageSource/src/threeDplot.c). wireframePanelCalculations is called (using .Call()) in the function lattice:::panel.3dwire, and it in turn calls a just-previously defined R function, wirePolygon, once for each facet of the surface. All that gets passed across between the C and R functions are the z-values and vector of color levels, and there's just no way to bypass this. Too bad!
|
|
1d
|
|
comment |
find all disjoint (non-overlapping) sets from a set of sets @user1322491 -- If I understand your question, here's an idea that should help. replicate(5, sample(1:50, size=20)) (This example gives you five sets of 20 integers selected from between 1 and 50, which you can then use as indices into your list of subsets.)
|
|
1d
|
|
comment |
determine when an R base function was added Although that news database only goes back to R 2.10.0. The R sources include text files ONEWS and OONEWS that together go back to R-0.50, but I can't immediately find how to get them loaded into the database accessed by news(). I suppose one could paste them together into NEWS and then recompile R, but that seems like a heavy handed solution. Anyone know another way?
|
|
2d
|
|
comment |
R: matrix of doubles turns into a matrix of strings Set options(error=recover). Then, when the error is thrown, you will be popped into a browser, of sorts, from which you can enter any of the frames that were active at the time of the error. At that point, go to a frame from which you can have a look at im's value, and check whether it's a character vector. Here is an example of what that process looks like.
|
|
May
21 |
|
comment |
Recursive object-listing Super. Thanks for this. I'm sure I'll use it as a template for other tree-walking functions in the future. |
|
May
21 |
|
revised |
Recursive object-listing added 86 characters in body |
|
May
21 |
|
revised |
Recursive object-listing added 86 characters in body |
|
May
21 |
|
answered | Recursive object-listing |
