Adds a parallel manager, allowing parallel execution of reaktoro blocks. #11
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.
Realted to
9
this adds ability for reaktoro to run in parallel using multiprocessing.This PR added a a new ReaktoroBlockManager class, that can be passed into a ReaktoroBlock allowing its aggregation and solving in parallel.
Most functionality remains the same. Typical usage is shown below :
Proceed to use as normal in flowsheet e.g.
once completed working with flowsheet ensure to kill all workers with
m.reaktoro_manager.terminate_workers()
Left to add:
async for when there are more blocks than the maximum allowed processors - currently, no checks or limits are enforced.
Currently, there is no clean way to interact directly with reaktoro_block.reaktoro_model.outputs.
Fix display for reaktoro state.