Update for new OpenMM Namespace - #1263
Conversation
|
fixes #1260 |
|
@jchodera it looks like the CI for Yank has been broken for a very long time, do you know what could be causing these schema errors? It looks like the same errors are showing up in the scheduled CI happening on master |
|
@mikemhenry : From memory, I think we've run into cases where updates to Here's an example of a previous instance in which cerberus broke things: #1180 |
|
Thanks! It looks like it is pinned to 1.1, but the PR makes it sound like it was updated to 1.2 |
|
@jchodera you might want to start using this PR to base your yank updates on since it takes care of the namespace changes in openmm |
Update to support openmm >= 7.6 namespace, but also support older versions of openmm as well