Open GerardBCN opened 7 years ago
Yes. Unfortunately the current automatic pipeline is only able to set up systems where the molecules to be alchemically modified is in formats .mol2
, and .sdf
that have a unique residue name.
If you are computing the hydration free energy of a small molecule, I'd suggest you to convert it to .mol2
.
If you are dealing with a small peptide instead, you can use the prmtop
/inpcrd
files generated by the automatic pipeline before the error happened (they should be in the folder output/setup/systems/...
) to specify your system with this syntax instead. Sorry this is just a temporary workaround, but we are planning to add support to alchemically modify peptides in the future.
Also, note that the code is still highly experimental and we haven't fully validated it yet! We are working on building an automated validation set to verify correctness prior to a 1.0 release and paper. So use at your own risk!
I see! Thanks! I did a fork of it and tweaked it a bit to accept my inputs. Seems to work just fine :) By the way, now that you mention validation sets, have you run any tests on solvation free energies? It is what I'm interested the most (for now) and I wonder with which accuracy you can reproduce experimental values for a given test case. Thank you!
@GerardBCN so sorry for missing your last message! Yes we did some preliminary solvation free energy calculations and we have obtained good results so far. The validation was performed using PME with a small number of uncharged molecules though. We are putting together a more comprehensive validation set.
I assume this problem occurs because utils.Mol2File is applied on my input, a pdb, instead of a mol2 file. Should the ligand always passed as mol2 file?