-
Notifications
You must be signed in to change notification settings - Fork 15
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
Release 2023.5.0 #228
Release 2023.5.0 #228
Conversation
This includes specifying the format of the restraints dictionary and implementing the numerical correction.
Allow correct SOMD config and pert files to be written for multiple distance restraints. Accompanying tests have also been introduced. This involved introducing an additional perturbation type "release_restraint", used exclusively with multiple distance restraints to remove all distance restraints but the "permanent" distance restraint.
Ensure that "endmolecule" is written for all SOMD pert files, and make the tests on the SOMD pert files more detailed (added checks for start and end atom and molecule lines).
Increase the number of directional clusters until the restraint search succeeds or hits the maximum.
system Otherwise this results in 'Error: an illegal memory access was encountered launching kernel kClearForces'
This addresses code review comments here #189.
Pass match_water parameter to specialised solvation functions
Do this by using .residues() on the result of the search.
Make sure disulphide search is converted to a SelectorBond.
Fix issue #225
Sync with BSS 2023.4.1
Synchronise with Exscientia remote. [ci skip]
As usual, on release I see an inexplicable test failure for one CI build. This test has never failed before and passed on the previous PR to |
And on a re-run it passes, which really makes no sense. There is nothing stochastic about this test. I must admit that I'm getting a bit concerned about the number of false positives (or negatives, depending on how you interpret it) from the CI at the moment. |
Same failure for Linux Python 3.10 on the build of the release packages. Absolutely baffling. |
This is the PR for the 2023.5.0 release of BioSimSpace.
devel
into this branch before issuing this pull request (e.g. by runninggit pull origin devel
): [y]