Please see http://www.poissonboltzmann.org/pdb2pqr/release-history for the complete release history Notable new features: PDB2PKA as an alternative to PROPKA for calculating pH values used to protonate residues. This feature is EXPERIMENTAL. The libraries to make this feature available are included in the binary releases. They are NOT included in the source code and are not compiled with the rest of PDB2PQR. Improved web interface. NEW FEATURES Improved look of web interface Option to automatically drop water from pdb file before processing. Integration of PDB2PKA into PDB2PQR as an alternative to PROPKA. Support for compiling with VS2008 in Windows. Option to build with debug headers. PDB2PKA now detects and reports non Henderson-Hasselbalch behavior. PDB2PKA can be instructed whether or not to start from scratch with --pdb2pka-resume Can now specify output directory for PDB2PKA. Improved error regarding backbone in some cases. Changed time format on querystatus page Improved error catching on web interface. BUG FIXES Fixed executable name when creating binaries for Unix based operating systems. Fixed potential crash when using --clean with extensions. Fixed MAXATOMS display on server home page. PDB2PKA now mostly respects the --verbose setting. Fixed how hydrogens are added by PDB2PKA for state changes in some cases. Fixed psize error check. Will now build properly without ligand support if numpy is not installed. Removed old automake build files from all tests ported to scons. Fixed broken opal backend. CHANGES Command line interface to PROPKA changed to accommodate PDB2PKA. PROPKA is now used with --ph-calc-method=propka. --with-ph now defaults to 7.0 and is only required if a different pH value is required. --ph-calc-method to select optional method to calculate pH values used to protonate titratable residues. Possible options are "propka" and "pdb2pka". Dropped support for compilation with mingw. Building on Windows now requires VS 2008 installed in the default location. Updated included Scons to 2.3.3 PDB2PKA can now be run directly (not integrated in PDB2PQR) with pka.py. Arguments are PDB file and Output directory. No longer providing 32-bit binary builds. PDB2PKA support is too memory intensive to make this practical in many cases. KNOWN BUGS If more than one extension is run from the command line and one of the extensions modifies the protein data structure it could affect the output of the other extension. The only included extensions that exhibit this problem are resinter and newresinter. Running ligands and PDB2PKA at the same time is not currently supported. PDB2PKA currently leaks memory slowly. Small jobs will use about twice the normally required RAM (ie ~14 titratable residues will use 140MB). Big jobs will use about 5 times the normally required RAM ( 60 titratable residues will use 480MB ). We are working to fix this.