Contact Object Serialization #29
Merged
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
Still problems with json encode in Py3 (Py2 is fine)
Issues with np.int64 not being JSON-serializable; must explicitly convert.
Also std'ized names _atom_contacts & _residue_contacts
dwhswenson
changed the title
Merged
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.
Serializing objects will facilitate task-based parallelization. This provides serialization to Python dicts or to JSON strings.
ContactMap(with tests)ContactFrequency(with tests)ContactDifference(with tests)NOTE: One limitation (as of the current implementation) is that subclasses (or duck-punched versions) of contact objects cannot be stored as the components of a
ContactDifference. In the future, I may try to allow subclasses, but you can't count on duck-typing to work.