On 17/02/2012 06:50, Martin Morgan wrote:
Running R CMD check on a package can take quite a lot of time. Checks
seem like they could be run in parallel (separate processes for, e.g.,
codoc, examples, tests, ...). Is there a way to do this? My current
usage is typically
R CMD build
R CMD check p
I'm sure I'm being an absolute bonehead (again), but can someone
suggest what I might be doing wrong?
Trying to build latest r-devel on Ubuntu 10.04; as recommended in
various places, trying to build it in a separate build directory (since
starting to compose this e-mail I've found that it wor
On 02/17/2012 01:42 AM, Prof Brian Ripley wrote:
On 17/02/2012 06:50, Martin Morgan wrote:
Running R CMD check on a package can take quite a lot of time. Checks
seem like they could be run in parallel (separate processes for, e.g.,
codoc, examples, tests, ...). Is there a way to do this? My curr
On 12-02-17 01:19 PM, Martin Morgan wrote:
On 02/17/2012 01:42 AM, Prof Brian Ripley wrote:
On 17/02/2012 06:50, Martin Morgan wrote:
Running R CMD check on a package can take quite a lot of time. Checks
seem like they could be run in parallel (separate processes for, e.g.,
codoc, examples, t
Ben,
On 17 February 2012 at 11:31, Ben Bolker wrote:
|
| I'm sure I'm being an absolute bonehead (again), but can someone
| suggest what I might be doing wrong?
|
| Trying to build latest r-devel on Ubuntu 10.04; as recommended in
Happy to take this off-list --- I do build every now and the
I've got another edition of my simulation replication framework. I'm
attaching 2 R files and pasting in the readme.
I would especially like to know if I'm doing anything that breaks
.Random.seed or other things that R's parallel uses in the
environment.
In case you don't want to wrestle with att
thanks,
I will not submit to CRAN.
I am having trouble going about including the .exe files in my package.
>From the readings I see that the .exe files must be placed in a 'src'
folder. But I don't see how I can access those files in R, without having
to specify its path in the R command 'system'.
If you put your prebuilt.exe into a directory under the
'source' package's inst directory, say yourPkg/inst/executables/win32,
then the installed package will have them in in
yourPkg/executables/win32 and the user (via code you
write, presumably) can get the full path to the executable
in the insta
Paul
I think (perhaps incorrectly) of the general problem being that one
wants to run a random experiment, on a single node, or two nodes, or ten
nodes, or any number of nodes, and reliably be able to reproduce the
experiment without concern about how many nodes it runs on when you
re-run it.
On Fri, Feb 17, 2012 at 3:23 PM, Paul Gilbert wrote:
> Paul
>
> I think (perhaps incorrectly) of the general problem being that one wants to
> run a random experiment, on a single node, or two nodes, or ten nodes, or
> any number of nodes, and reliably be able to reproduce the experiment
> without
Ok, I guess I need to look more carefully.
Thanks,
Paul
On 12-02-17 04:44 PM, Paul Johnson wrote:
On Fri, Feb 17, 2012 at 3:23 PM, Paul Gilbert wrote:
Paul
I think (perhaps incorrectly) of the general problem being that one wants to
run a random experiment, on a single node, or two nodes, or
On Fri, Feb 17, 2012 at 02:57:26PM -0600, Paul Johnson wrote:
> I've got another edition of my simulation replication framework. I'm
> attaching 2 R files and pasting in the readme.
>
> I would especially like to know if I'm doing anything that breaks
> .Random.seed or other things that R's paral
On Fri, Feb 17, 2012 at 5:06 PM, Petr Savicky wrote:
> On Fri, Feb 17, 2012 at 02:57:26PM -0600, Paul Johnson wrote:
> Hi.
>
> Some of the random number generators allow as a seed a vector,
> not only a single number. This can simplify generating the seeds.
> There can be one seed for each of the
13 matches
Mail list logo
