-
Notifications
You must be signed in to change notification settings - Fork 100
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
How to change the force-field in an ATB file (to OLPSAA) #91
Comments
Hello Hao Changing the force field is not a one-line change. Moltemplate can be used to setup simulations with very unorthodox force-fields. But for standard all-atom force-fields like OPLSAA, you may find other molecule builders that are more convenient to use. Try a more user-friendly program?Some molecule-builder programs are comparatively easy to use, and you can change the force-field with a single line of text or with a button. Unfortunately moltemplate cannot do that. When using moltemplate, whenever you change the force field for a molecule, internally the number of angles, dihedrals, and impropers will probably also change. Some programs hide all this complexity from the user. Moltemplate does not. Those details are sometimes stored explicitly in the LT file. This is true for the files created by the ATB server. That's why they are ready to use after downloading them. So you will have to change the LT file in many places to change the force-field for that molecule. ATB files were only intended for use with the special ATB version of the GROMOS force-field. If my understanding is correct, the authors of ATB argue that these custom ATB force-field parameters are potentially more accurate than parameters from more traditional force-fields such as OPLSAA, CHARMM, AMBER, GROMOS, PCFF, or even SMIRNOFF, that use simple rules and tables instead of DFT. Try LigParGen?If you want to use OPLSAA, why not download the molecule from the LigParGen server?
You have to be careful using the LigParGen server. It has some issues with atom typing (eg. this one). Files generated by LigParGen use the OPLSAA force field, the atom type names are incompatible with molecules built by hand (using the "oplsaa.lt" file, as explained below). But if all of your files come from the LigParGen server, this doesn't matter. Either way, the .lmpdat files generated by LigParGen are a useful starting point for building your own molecule files in moltemplate (.lt) format. Build your LT files from scratch?Alternatively, you can create your .lt file by hand (or modify the one created by ATB).
I hope this reply is not too late to be useful. I'll leave this question open so other people can read it. |
If I create a structure with VMD/topotools, and I want to use the “ltemplify.py” utility to convert this data file into “LT” format with force-field OLPSAA. |
Sadly, no. There are no examples in the manual that explain how to use these all-atom force fields (OPLSAA, AMBER/GAFF, DREIDING, COMPASS, ...). I don't have time to add this information to the moltemplate manual. (And the procedure for using all-atom force-fields changes frequently.) The only way to learn how to use those force fields is to look at the current examples, and modify them. |
HI,
I am new to Moltemplate. I am trying to build a small organic molecule for lammps. I obtained the all_atom_geometry_optimized.lt, In this file it automatically using GROMOS_54A7_ATB which I wanna replace with OPLASS but there seems it has problem if I just replace the GROMOS_54A7_ATB with OPLASS in all_atom_geometry_optimized.ltand also add "import 'OPLASS'" in the system.lt. It complains the bonds part in the all_atom_geometry_optimized.lt. Do you have any solution for this?
BW
Hao
The text was updated successfully, but these errors were encountered: