-
Notifications
You must be signed in to change notification settings - Fork 71
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
FIxing modeller bug for WT case #1074
Conversation
Tests are passing, but I'm not sure if I've got the test for the WT case correct |
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.
The fix looks good! For the test, I wouldn't add a new one but just add to test_modeller_mutations
something like
# We haven't set the strip_protons options, so this shouldn't do anything
exp_builder._db._setup_molecules(mol_id)
assert not os.path.exists(output_path)
# ADD THIS BLOCK
# Calling modeller with WT creates a file (although the protein is not mutated).
exp_builder._db.molecules[mol_id]['pdbfixer'] = {
'apply_mutations' : {
'chain_id' : 'A',
'mutations': 'WT',
}
}
setup_molecule_output_check(exp_builder._db, mol_id, output_path)
os.remove(output_path) # Remove file for next check.
# NEW BLOCK ENDS
# Now we set the strip_protons options and repeat
exp_builder._db.molecules[mol_id]['modeller'] = {
'apply_mutations': {
'chain_id': 'A',
'mutations': 'T85I',
}
}
setup_molecule_output_check(exp_builder._db, mol_id, output_path)
Whops! Sorry, it looks like the test I suggested fails because when using setup_molecule_output_check(exp_builder._db, mol_id, output_path)
os.remove(output_path) # Remove file for next check. with exp_builder._db._setup_molecules(mol_id)
assert not os.path.exists(output_path) Can you also update the release history (docs/whatsnew.rst) before merging? |
Hmm weirdly, it looks like it's actually the second yank/Yank/tests/test_experiment.py Line 1356 in bd9a493
Do I need to reinitialize the |
Hmm. I don't think you should! Can you check what |
Tests finally pass! Should I merge this and go ahead with a bugfix release? |
Yep!
… On Aug 24, 2018, at 4:42 PM, Andrea Rizzi ***@***.***> wrote:
Tests finally pass! Should I merge this and go ahead with a bugfix release?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Modeller was throwing an error when given
WT
in the yaml pipeline.