By the way, all my work on BiocParallel is going to end up here:
https://github.com/DarwinAwardWinner/BiocParallel
If you want to read through the multicore-only pvectorize, it is here:
https://github.com/DarwinAwardWinner/BiocParallel/blob/a3699cf/R/pvectorize.R
It's a little more than one l
On Tue, Dec 4, 2012 at 12:47 PM, Ryan C. Thompson wrote:
> One issue that I see is that for some kinds of parallel backends, there
> may not be any way for "bpworkers" to return something meaningful. For
> example, a backend that submits jobs to a large cluster may not know
> exactly how many node
One issue that I see is that for some kinds of parallel backends, there
may not be any way for "bpworkers" to return something meaningful. For
example, a backend that submits jobs to a large cluster may not know
exactly how many nodes are in the cluster, and in any case returning the
total numb
On Tue 04 Dec 2012 11:31:59 AM PST, Michael Lawrence wrote:
The name "pvec" is not very intuitive. What about "bpchunk"? And since the
function passed to bpvectorize is already vectorized, maybe bpvectorize
should be bparallelize? I know everyone has different
intuitions/preferences when it comes
Looks like great progress has been made. Here are some thoughts:
The *Params objects seem to have two roles: specifying the desired
resources and indicating the scheduler (the thing that actually executes
the jobs). Maybe it would be beneficial to have separate abstractions for
those two things. F
