One very simple question, probably not appropriate to post this to rdevel list,
I put all Fortran files in src, when I do R CMD check, it tries to compile
the files by alphabetical order. I tried to modify Makevar, but no luck
after staring at the manual for hours. It seems that I could use R CM
On 30/08/2012 16:59, LIYING HUANG wrote:
One very simple question, probably not appropriate to post this to rdevel list,
I put all Fortran files in src, when I do R CMD check, it tries to compile
the files by alphabetical order. I tried to modify Makevar, but no luck
after staring at the manual
Hi all,
I'm working with some huge array in R and I need to load several ones to
apply some functions that requires to have all my arrays values for each
cell...
To make it possible, I would like to load only a part (for example 100
cells) of all my arrays, apply my function, delete all cell
On 31/08/2012 9:47 AM, Damien Georges wrote:
Hi all,
I'm working with some huge array in R and I need to load several ones to
apply some functions that requires to have all my arrays values for each
cell...
To make it possible, I would like to load only a part (for example 100
cells) of all my
I'm not an expert in its use, but I believe the bigmemory package offers
the functionality you are looking for (or at least similar functionality
that can be co-opted for your use-case). See the sub.big.matrix function.
Depending on what you mean by "huge" it may offer other benefits as well.
HTH,
On 31/08/2012 15:41, Duncan Murdoch wrote:
On 31/08/2012 9:47 AM, Damien Georges wrote:
Hi all,
I'm working with some huge array in R and I need to load several ones to
apply some functions that requires to have all my arrays values for each
cell...
To make it possible, I would like to load on
There is no such tool to my knowledge, though the mmap package can do
very similar things. In fact, it will be able to do this exactly once
I apply a contributed patch to handle endianess.
The issue is that rds files are compressed by default, so directly
reading requires uncompressing, which mak
On 12-08-24 9:57 PM, Spencer Graves wrote:
Hi, Henrik:
Thanks. That suggests I should ignore this error message. That
was my tentative plan, but I felt a need to mention it to this group
before I did.
Brian Ripley tracked this to a bug in the parser, and I got a
reproducible version
On 8/31/2012 5:48 PM, Duncan Murdoch wrote:
On 12-08-24 9:57 PM, Spencer Graves wrote:
Hi, Henrik:
Thanks. That suggests I should ignore this error message. That
was my tentative plan, but I felt a need to mention it to this group
before I did.
Brian Ripley tracked this to a bug in
