GitLab

createSystem for both Amber and CHARMM files.

Add relevant tests (that used to fail). This also fixes a subtle bug where
switching functions were not applied when NBFIXes were specified.

Also fixes the test case.  Everything should pass now.

Apparently CHARMM PSF files (particularly those printed by VMD's psfgen) can
have an insertion code tacked on to the end of the residue number, meaning that
casting to an integer will invariably fail.  We can't just ignore the insertion
code, though, since it will differentiate from the residues that came before and
after (which will likely have the same number -- same general idea as insertion
codes from PDB files). So instead we pull the insertion code off of the residue
number and extend the Residue object to accommodate that.

This is the port of the fix from ParmEd: ParmEd/ParmEd#98

I added a test for this case.

simtk.openmm.app namespace to allow users to filter that warning out if they
want to.

(again, code pulled from ParmEd) and update the tests to include this.

pick up some bugs that were not caught in my initial test following the port
from ParmEd.

All 4 tests pass right now, although no periodic systems are being tested.
Currently CHARMM, XPLOR, and VMD tests are all being run (for the same ala-3
system).

Disable implicit solvent tests, since there is no robust radii assignment
routine yet (the radii are stored in the Amber topology file).  I will port my
assignment routine from ParmEd here shortly and then re-enable the GB tests.