search for: biocparallel

Thanks - I'll find another way to send messages to the main thread for printing. -Winston On Tue, Nov 21, 2017 at 12:42 PM, <luke-tierney at uiowa.edu> wrote: > On Tue, 21 Nov 2017, Winston Chang wrote: > >> Is it safe to call Rprintf and REprintf from a background thread? I'm >> working on a package that makes calls to fprintf(stderr, ...) on a >>

Good day, I'm trying the example cl <- makeCluster(2, type = "SOCK") from the makeCluster documentation and the R command prompt never returns. I am using a 32-bit Windows 10 computer. The problem doesn't happen on another 64-bit Windows 10 computer but does happen on another 32-bit Windows 7 computer. Can anyone reproduce it? Are there any other options that can be passed to

Thanks for all your great answers. The app I?m working on is indeed an exploratory data analysis tool for gene expression, which requires a bunch of bioconductor packages. I guess for now, my best solution is to divide my app into modules and load/unload packages as the user switch from one module to another. This brought me another question: it seems that unload package with the

...packages will need to be rebuilt: * COPASI * R-abind * R-acepack * R-affy * R-affydata * R-affyio * R-ALL * R-AnnotationDbi * R-ape * R-argon2 * R-ascii * R-askpass * R-assertthat * R-AUC * R-backports * R-base64enc * R-Bessel * R-BH * R-biglm * R-bindr * R-bindrcpp * R-Biobase * R-BiocGenerics * R-BiocParallel * R-biomaRt * R-Biostrings * R-bit * R-bit64 * R-bitops * R-blob * R-brew * R-BSgenome * R-BSgenome.Celegans.UCSC.ce2 * R-BufferedMatrix * R-BufferedMatrixMethods * R-Cairo * R-callr * R-car * R-caTools * R-cellranger * R-chron * R-cli * R-cliapp * R-clipr * R-clisymbols * R-coda * R-colorspace * R...