Deprecate MSMBuilder - #853
Merged
dwhswenson merged 4 commits intoSep 19, 2019
Merged
Conversation
how stupid can I be?
Member
Author
|
This is ready for review. I'll leave this up for comment for at least 24 hours (will not merge before evening of 18 September). |
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
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.
MSMBuilder is not being maintained. Its
conda-forgebuild pins numpy to 1.12. OpenMM 7.4 requires numpy>=1.14, (although this requirement is implicit, not explicit, so we end up with test failures when we try to run OpenMM with an old version of numpy, see openmm/openmm#2385).I think the solution on our end is to deprecate the integration with MSMBuilder (
MSMBFeaturizerCV). In principle, we can keep it around, but we can't test it in the same environment as the newest OpenMM.I'm marking it as deprecated and to be removed in 2.0, with the thoughts that: