How can we specify additional forcefield loading statements for LEaP?
See original GitHub issueFor dealing with divalent cations, we need to do more than load a leaprc.*
file.
There is an additional step of loading another frcmod
file:
source leaprc.ff14SB
loadAmberParams frcmod.ionslrcm_hfe_tip3p
Do we currently have the capability to specify these extra lines to be passed to leap?
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
Tutorial: Using Tripos mol2 files within LEaP
Server are to derive RESP or ESP charges and to build force field libraries for small molecules and molecule fragments. Data generated by...
Read more >AmberTools Users` Manual | Manualzz
The most straightforward way to specify which force field you want is to use one of the leaprc files in $AMBERHOME/dat/leap/cmd.
Read more >Tutorial 4 : NMR Refinement of a DNA Duplex
The program LEaP, which reads in the force field, topology and coordinate information ... You could specify another leaprc file by using the...
Read more >Add Amber ff19SB params · Issue #3655 · openmm ... - GitHub
The new ff19SB forcefield has shown to improve amino acid-dependent ... Recent versions of ambertools have ambertools/dat/leap/parm/frcmod.
Read more >LEaP - LEaP Tutorial for AMBER Page 1 of 9 Copyright (C) Pengfei ...
In the classical force field, a molecule can be describedas a collection of many atoms of numerous types connected to each other, in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Currently
parameters
handle both.frcmod
and.leaprc
files. This can work because it loads by default theleaprc.gaff
with small molecules.If we plan to move away from leap, maybe it’s better to expand the syntax to load multiple parameters files (and use the right command based on the extension)? Something like
Note that the OpenMM setup pipeline won’t be in YANK 1.0