-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pymbar 3 4 #659
Pymbar 3 4 #659
Conversation
Co-authored-by: Iván Pulido <[email protected]>
Supersedes #630 |
hmmmm, seeing the same errors for pymbar 3&4
|
That test passes fine on |
I yelled when I saw this: https://github.com/choderalab/openmmtools/blob/main/openmmtools/multistate/utils.py#L178-L183 I could not figure out how an import fixed things, well it "solved" the problem that this bare except hid. BUT what is crazier is that we don't get a failure every time, but will essentially calculate a subsample rate larger than than our input array, which causes our equilibrated indices to be Anyway, bare excepts were a bad idea. I can't belive the amount of time I spent on this. |
…n so we can figure out what we are trying to catch
I will be cleaning up those exceptions in this PR as well.... |
Oh yeah, of course bare excepts are biting us, good catch! Thanks. |
On windows-latest, py-3.8.10, OpenMM-8.0, pymbar-4
and on windows-latest, py-3.10, OpenMM-8.0, pymbar-3
All the other windows builds are fine, but we probably do want to catch that error so it doesn't crash a simulation if it happens. That can be done in another PR. |
Okay! Since everything is passing except those two errors, I am now going to switch up the CI matrix so that we are testing mostly with pymbar 4, but will keep a few jobs at pymbar 3 to make sure we maintain support for both. |
Once we finalize the matrix, I will mark them as required |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking great. Just a few comments I think we need to adress.
print("If you see this, open an issue https://github.com/choderalab/openmmtools/issues") | ||
raise e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to raise the exception here? I feel like this might be disruptive for current users/applications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #659 (comment) I think we can see if perses has any problems as well as other downstream packages as a double check. I worry it does more damage leaving it in the codebase. I could be convinced to just log an error but I think no one will see it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks! I tested with perses locally in a tyk2 benchmark system and it seems to be working (using pymbar3). LGTM!
Description
Provide a brief description of the PR's purpose here.
Todos
Status
Changelog message