Slight persistence patch and HTMObjectIn/Output constructor change.#419
Merged
Merged
Conversation
added 5 commits
May 1, 2016 20:06
This was referenced May 2, 2016
Collaborator
Author
|
@rhyolight I want to merge this when coveralls stops complaining - its an update needed by @EronWright for flink-htm. I added very minor changes... |
Collaborator
Author
|
@EronWright Do you want to give this a go before I merge it? |
Contributor
|
@cogmission I tried it out and it looks good to me. |
This file contains hidden or 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
3 participants
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.
Fixes #417
Fixes #418
Support not halting the Network when serializing it during non-threaded use. This support is built in to the checkpointing mechanism so halt doesn't have to be called, but in the case where a library has its own checkpointing mechanism (i.e. Flink), this patch will support that use case if the Network is not in threaded mode.
If the Network is in threaded mode then users are forced to use the built in checkpointing mechanism until such time as a need develops to allow some flexibility with that option.