Experimental/concurrent futures ensemble #1080
Closed
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
…rface. works locally! but not asynchronous
…ieve nonblocking, then wait on result of ensemble
…- this is more inline with the interface. so the example is now based off give-pregenerated-work. pretty elegant in my opinion
|
This is probably not the implementation we'd want to follow-up on. Closing for now. |
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.
Addresses #1033
Returns a future corresponding to an
Ensemble.run() / libE()on a single thread.In a given script, any generator class/process can return points, then slot them into a np array, then we can pass them in a H0 as part of a pregenerated-work workflow