Open zhenyuwei99 opened 2 weeks ago
That happens when the force field involves NBFIX terms: particular pairs of atom types whose LJ interaction is computed with different parameters than what the standard combining rules would give. NonbondedForce doesn't support that, so it implements the LJ interaction with a CustomNonbondedForce instead.
Hi,
I am running a simulation of the KCSA ion channel using the Charmm forcefield. I noticed that two nonbonded force classes exist in the system created by the
CharmmPSFFile.createSystem
Method. The document states that theNonbondedForce
calculates the LJ and electrostatic interaction. However, when I get the parameter fromnonbondedForce.getParticleParameters(index)
, the epsilon is 0 for all particles, as shown here:And the
CustomNonbondedForce.getEnergyFunction()
returns:I am wondering why to separate the LJ and electrostatic into two parts.
Best,