nChunks, nChunks2, nTastks, mc.cores, chunkSize about bgdata HOT 2 CLOSED

Agreed on all of them except mc.cores because detectCores() is not reliable on the cluster and nTasks is undefined if not specified. I would further suggest to rename mc.cores to nCores in case a better multicore package comes along in the future. I think blockSize could also use a complementary nBlocks just like the chunking does.

from bgdata.

sounds good. note that if we set mc.cores (or nCores) to min(detectCores(),nTasks) we will control everything with nTasks. If nTasks has default value of 1, then we will just be assuming that the user will not send a job requestin x cores and then use in the scripts nTasks>x.

In any case this won't be a big deal because it is just a matte of how to define default values. We also need to think carefully about setting default values. I suggest chunkSize and blockSize will preceed over nChunks and nBlocks.

from bgdata.