search for: sendcall

I am interested in running R commands asynchronously. My first choice is in the same R session that I am currently in. Here, the goal would be to run something like RunAsynchSameSession(myfunction(), "outputname.rda") Once RunAsynchSameSession had started myfunction(), RunAsynchSameSession would complete immediately. myfunction would keep going. It is OK if execution of the

...gress bar. When the code is intended to be run on a 'parallel' cluster, it generally cannot rely on its own side effects to report progress. I've found three approaches to progress bars for parallel processes on CRAN: - Importing 'snow' (not 'parallel') internals like sendCall and implementing parallel processing on top of them (doSNOW). This has the downside of having to write higher-level code from scratch using undocumented inferfaces. - Splitting the workload into length(cluster)-sized chunks and processing them in separate parLapply() calls between upd...

...intended to be run on a 'parallel' cluster, it generally cannot rely on > its own side effects to report progress. > > I've found three approaches to progress bars for parallel processes on > CRAN: > > - Importing 'snow' (not 'parallel') internals like sendCall and > implementing parallel processing on top of them (doSNOW). This has > the downside of having to write higher-level code from scratch > using undocumented inferfaces. > > - Splitting the workload into length(cluster)-sized chunks and > processing them in separate...