1. 05 Nov, 2015 2 commits
  2. 04 Nov, 2015 1 commit
  3. 03 Nov, 2015 1 commit
    • Robert McGibbon's avatar
      Improve docstrings · 98d053d4
      Robert McGibbon authored
      Swigged python docstrings now include documented return values and type
      information or their arguments. They are generated in numpydoc format.
      Furthermore, all of the Python app layer docstrings have been changed
      to numpydoc format. The filterPythonFiles.py script which helps to
      generate the Doxygen Python API docs has been updated to reflect these
      changes.
      98d053d4
  4. 09 Oct, 2015 1 commit
  5. 27 Aug, 2015 1 commit
  6. 22 Apr, 2015 1 commit
  7. 20 Apr, 2015 1 commit
  8. 10 Apr, 2015 1 commit
    • Jason Swails's avatar
      Improve CHARMM parsing when resnums have inscodes · 7b30da6e
      Jason Swails authored
      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.
      7b30da6e
  9. 05 Mar, 2015 1 commit
  10. 11 Feb, 2015 1 commit
  11. 09 Feb, 2015 1 commit
  12. 23 Oct, 2014 1 commit
  13. 20 Aug, 2014 1 commit
  14. 10 Aug, 2014 1 commit
    • Jason Swails's avatar
      Redo the way CHARMM PSF files are parsed. This should be much more robust in · 4b9221e3
      Jason Swails authored
      terms of supporting PSF files that don't really conform to the "standard" way
      that CHARMM prints them.
      
      The downside is that it relies on ! comment tags which I think are comments for
      CHARMM.  However, the use of !NATOM and !NBOND and other tags seem to be _much_
      more conserved than the general format of the PSF file across different dialects
      of PSFs.  So the current approach should be more flexible.
      4b9221e3
  15. 18 Jul, 2014 4 commits
  16. 07 Jul, 2014 1 commit
  17. 03 Jul, 2014 1 commit
    • Jason Swails's avatar
      Small fixes: · f5cbd31e
      Jason Swails authored
          - Adjust CharmmPsfFile parser to accept multiple blank lines before the
            NATOM record (I saw 1 PSF file like this... not sure how common it really
            is)
          - Removed the shebang line from element.py and removed execute permissions--
            it should never be executed directly (evidenced by the fact that the
            original shebang line was wrong and would never work, anyway).
          - Fix a test to determine if a Bond is part of an Angle in the PSF data
            structures.
      f5cbd31e
  18. 30 May, 2014 1 commit
    • Jason Swails's avatar
      Make separate lists for dihedrals and the dihedrals with loaded parameters. The · 2b0962e0
      Jason Swails authored
      former has a single entry for all unique dihedrals. The latter has a separate
      entry for every _term_ of every dihedral (and the latter is the one with the
      parameters loaded into it). This way, parameter sets can be reloaded at will
      without relying on the hack that createSystem previously employed (i.e., backing
      up the dihedral array, clobbering it, then putting it back). This way is cleaner
      and safer (although functionally equivalent for typical OpenMM use).
      2b0962e0
  19. 29 May, 2014 1 commit
  20. 21 Apr, 2014 1 commit
  21. 20 Apr, 2014 1 commit
  22. 19 Apr, 2014 1 commit
  23. 18 Apr, 2014 4 commits
  24. 16 Apr, 2014 4 commits
  25. 15 Apr, 2014 4 commits
  26. 14 Apr, 2014 1 commit
  27. 12 Apr, 2014 1 commit