Change cores=1 so that it doesn't create parallel clusters #304
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes it easier to debug problems. If you set cores=1 with current master, you still have everything run on a cluster (with 1 core) which means error messages are often obfuscated to the effect of "no connection" type errors.
This just turns off the creation (and destruction) of the cluster, allowing everything to run as per usual. Errors then get reported directly.
NOTE: There is an additional
parallel::makeCluster()command inEnsemble_TMLA.Rthat appears to be incorrect. I have no idea what it is supposed to be doing, so have not changed this one. If you can direct me as to it's use, I'm happy to incorporate into this framework :)