-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contemplate an rslurm backend #120
Labels
Comments
@kendonB I am particularly curious about your experience trying out |
It almost works: earthlab/rslurm#15 |
Got rslurm to work with the change suggested in earthlab/rslurm#15! |
@kendonB Sorry, I did not mean to sound dismissive of your efforts on |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implementation would be similar to the future_lapply funcionality. @kendonB, do the examples in the rslurm vignette work for you? This would be the biggest reason for adding or not adding a separate backend. I do not want the
drake
code base to get too large, but I may add a special case if it makes or breaks a project that needs serious HPC.The text was updated successfully, but these errors were encountered: