> For tasks which don't involve I/O but fail with mclapply, how does one > work out where the problem is? The handy browser() function which > allows for interactive diagnosis won't work with parallel jobs. > > What other approaches can one use?
?dump.frames - interactive debugging after the fact. Hadley -- Chief Scientist, RStudio http://had.co.nz/ ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
