Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upNcpus argument and install2.r #62
Comments
|
That sounds like a great idea, and should be pretty simple. Both |
|
My preference would be for
|
|
I like the option of 'maxing out' but I am not sure I like zero for that special value. Hm. Minus one? NA? NULL? I am indifferent between |
|
I quite like the Do you have a preference for the default? Either |
|
I like |
|
Main question now if we call it |
|
That just occurred to me as I wrote the doc string. Back to Also, I'll go for |
|
Sure. |
|
Looks good. Thanks for catching the rogue I am wondering if we should fold the two branches into one. Ie detect "getOption" as you do but then default to detect the system cores as a fallback, ie
Thoughts? It may well be too aggressive as it would hog all cores unless told otherwise... Similarly, two lines in the |
|
|
I think that is still too much. We share a big box at work with 36 hyperthreaded cores. If someone uses it there... For example We'll make it one line in |
|
Updated the PR:
|
|
It's good. And the double branch is probably also what we need to set options properly. No need to get too cute. One type as you use two hyphens: |
|
Also four space indent not two but all minor -- taken care of now. Thanks again for this. Very nice enhancement. |
I don't think it's possible to use Ncpus with your neat install2.r script. Would you be open to a PR to include this functionality?