Open ATpoint opened 1 year ago
Alternatively, using the future
package might be an option. Though it is possible to to register future
with BPPARAM
via DoparParam
.
Thanks for your comment -- this is very helpful to know! I will look into an OS-agnostic alternative like the ones you suggest and will update appropriately.
Hello,
Just wanted to circle back on this to see if this has been resolved. Is there a recommended alternative to run the testClusters() function on Windows machines?
Appreciate all your help!
Hi, apologies, I haven't gotten around to this yet! For now, I would recommend sending cores=1
or alternatively parallel=F
.
Hello,
This works! Thanks so much.
Hi, just saw the package on Twitter / the Nature paper and started playing with it a bit. One thing that caught my eye was that the defaults of
testClusters()
will result in an error on Windows machines as it usesmclapply
with > 1 core. My suggestion would be to replacemclapply
with eitherbplapply
fromBiocParallel
to allow the user to register cores appropriately depending on OS (BPPARAM
objects), or switch to any other parallelization function/package that supports Windows. I guess in case you want to submit this to CRAN or Bioc at some point it is in any case advisable to use an "OS-agnostic" rather than mclapply parallelization. Hth.