-
Notifications
You must be signed in to change notification settings - Fork 5
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
Test openfe 1.0.0rc0 + refresh showcase #99
Conversation
url to test on colab https://colab.research.google.com/github/OpenFreeEnergy/ExampleNotebooks/blob/openfe-1.0.0rc0-test/openmm_rbfe/OpenFE_showcase_1_RBFE_of_T4lysozyme.ipynb NOTE: I've hardcoded the installer into the notebook, so that needs to be changed and point it towards the new env |
First error in the showcase notebook |
I'll start working on fixing that notebook! Should I make a PR into this PR @mikemhenry ? |
@hannahbaumann yep I imagine so |
The showcase tutorial goes over how to create settings from the Settings classes directly, instead of through the default options from the protocol. I'm not sure if this is the best way for the user to learn about / access the settings, since we usually say settings should be modified starting from the default option of the protocol. A problem that arises here, e.g. is that some settings (e.g. |
@hannahbaumann Yeah creating defaults then customising these is probably the intended/recommended route. This means we can avoid importing individual sub-settings entirely |
@hannahbaumann feel free to either make a PR into this one, or commit directly to the |
There are three notebooks in the |
…ory in showcase/openfe_showcase.ipynb history.
* fix showcase notebook * small fixes
…t' into openfe-1.0.0rc0-test
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Switching to TYK2 as example system throughout the showcase notebook
Looks like things work on python 3.10, I updated the notebooks we test as well to |
Hmmm, the |
For the sake of getting this shipped, I will use some larger result files that could be smaller, but I rather get this out the door then figure that out right now. |
Good catch! fixed in 33cca55 |
Running the colab notebook as a test, if it passes I will merge in the PR... super close now! |
a few time outs and this error is still showing up, but the showcase is working so I will merge it in after one more check on colab! |
Fixed the syntax issue and I am updating the cookbook and then we should be good (except for the time outs but we can fix that later) |
@richardjgowers I am not sure how to fix this: So I think if we want this assert to work, we need to change the default to be like I feel like this is something we spin out into an issue and just comment out the assert check in the cookbook for now |
First spruce up CI, then see if our tests pass using the RC