arnaud gaboury writes:
> After a few days of reading and headache, I finally gave a try at
> building R from source with Intel MKL and ICC. Documentation and posts
> on this topic are rather incomplete, sometime fantasist et do not give
> much explanations about configure options.
> As I am not s
On Fri, Sep 4, 2015, 9:24 AM Bjørn-Helge Mevik
wrote:
arnaud gaboury writes:
> After a few days of reading and headache, I finally gave a try at
> building R from source with Intel MKL and ICC. Documentation and posts
> on this topic are rather incomplete, sometime fantasist et do not give
> mu
Thanks for the detailed analysis Simon. I figured out a workaround that
seems to be working in my real application. By limiting the length of the
first argument to mclapply (to the number of cores), I get speedups while
limiting the memory overhead.
### Run mclapply inside of a for loop, ensuring
On Wed, 2015-09-02 at 20:49 +0200, arnaud gaboury wrote:
> On Wed, Sep 2, 2015 at 7:35 PM, arnaud gaboury
> wrote:
> > After a few days of reading and headache, I finally gave a try at
> > building R from source with Intel MKL and ICC. Documentation and posts
> > on this topic are rather incomple
Hi all!
I have written some code in C for simulating the fate of population
using a dll loaded in R. During this simulation the population may go
extinct such that the length of its trajectory is unknown beforehand. I
wonder there is a way to define the size of the result in C and make it
kno
Is there any reason that the R-devel tarball at [1] stucks on r69202?
It seems, that newer R-devel versions are now published on
/pub/misc/cran/src/base-prerelease, for example at
http://ftp5.gwdg.de/pub/misc/cran/, but without an R-devel.tar.gz
tarball ...
Is this intended? Any clarification wou
