You could look at some extension packages, bigmemory for example. A recent
paper http://www.jstatsoft.org/v55/i14 (though for more developer-level
capabilities you would need to look at the package itself). Although the
big.matrix objects can't be used seamlessly as if they were matrices, they
do
Hin-Tak Leung wrote:
...
Somewhat related, I have finally gotten round to make two small bundles,
which replace the small cairo.dll/cairo.so' in the official
windows or Mac R binaries, to fix quite a few problems with them,
the first of which was reported almost a year ago. Just move the two
smal
Jay, Duncan,
Thank you for your replies.
The confusing part for me is that vector allows large indices, while array does
not allow.
Also, is there an estimate when R would support long arrays?
Thanks,
Boris
From: Jay Emerson [mailto:jayemer...@gmail.com]
Sent: Monday, January 06, 2014 4:37 AM
On 14-01-06 4:12 PM, Boris Aronshtam wrote:
Jay, Duncan,
Thank you for your replies.
The confusing part for me is that vector allows large indices, while array does
not allow.
See section 12 of the R Internals manual for a discussion of the issues.
Also, is there an estimate when R would
Is the following passage from help("file.info"):
"Junction points and symbolic links are followed, so information is
given about the file/directory to which the link points rather than
about the link."
correct? Could it be that Windows was not considered?
help("file.symlink") mentions several Wi
With that much RAM, you probably have many cores. Consider splitting
your long array across several R sessions with distributed parallel
processing so that no one segment is over the limit. You will likely
need the parallel processing anyway to make your computation time
tolerable. See the pbdD
Just before the holiday, I asked the freetype developers what is the context
of these two comments about freetype in the code of R's grDevices:
=== R/src/library/grDevices/src/cairo/cairoFns.c around line 720 =
/* some FreeType versions have broken index support,
