On Mon, Sep 24, 2012 at 11:43 AM, Michael Lawrence <
lawrence.michael@gene.com> wrote:

>
> Tricks aside, mclapply has some issues that would be nice to address. The
> main one for me is error handling. I have developed some code that wraps
> the user function in try() and compiles any errors into a special
> "batchCondition" object that provides access to the individual exceptions
> and gives a nice summary of what went wrong. Ideally, that would go into
> parallel, but we could put it in IRanges as a stop gap
>

This is a great idea!   And absolutely would enhance base R if included in
parallel.

I end up wrapping almost all functions passed to mclapply in layers of try(
... ) blocks; it would be great not to reinvent the wheel anymore.

mclapply() is appealing precisely because it is the simplest thing that
could possibly work.  But sometimes that comes back to bite the user.


-- 
*A model is a lie that helps you see the truth.*
*
*
Howard Skipper<http://cancerres.aacrjournals.org/content/31/9/1173.full.pdf>

	[[alternative HTML version deleted]]

