The POPScomp server invokes the POPS program to compute the Solvent Accessible Surface Area (SASA) of a given PDB structure. For protein or RNA/DNA complexes, the POPScomp server creates internally all pair combinations of chains to compute the buried SASA upon complexation. Details of those functionalities are explained in the published papers on implicit solvent, POPS and POPSCOMP; see 'About' tab for the list of publications.
SASA tables are initialised without any values; therefore, before 'run POPScomp' execution, the user sees only the table header and below the notice 'Showing 0 to 0 of 0 entries'. After selecting a PDB file and pressing 'run POPScomp', the server runs the POPS program on the selected PDB file. The output is SASA tables, which are automatically loaded into the respective tabs. Because that computation is a shell command, the success of the computation is returned as exit code and shown below the 'run POPScomp' button. It should normally read 'Exit code: 0', otherwise consult the 'Exit Codes' tab.
The SASA result tabs are 'Atom', 'Residue', 'Chain' and 'Molecule'. Those tabs contain a second layer of tabs to accommodate the POPSCOMP functionality, as follows. 'Input Structure': SASA values of the PDB structure as input. 'DeltaSASA': The SASA difference between isolated chains and chain pair complexes. 'Isolated Chains': SASA values of isolated chains. Only structures containing multiple chains will yield values for 'DeltaSASA' and 'Isolated Chains' tabs.
Results will be kept for one day on the server. Please use the 'Download ...' buttons under the tables to save their content in 'csv' format. The 'Download All Results' button on the side panel returns the zipped content of the output directory.
Refresh the browser between runs, otherwise the same (random) output directory will be used, which may be confusing if results for single-chain structures and complexes are being mixed. This behaviour will be improved upon in future releases.
In case the server does not work as expected or server-related issues need clarification, please email the maintainers: Jens Kleinjung (email@example.com) and Franca Fraternali (firstname.lastname@example.org). For software and output errors, feature suggestions and similar topics, please add an entry to the Issues tab on the POPScomp GitHub page .
This is version 3.1 of the POPScomp Shiny App. There are several options to run this code:
1. Use our server at http://popscomp.org:3838 -> POPScomp .
2. Download the POPScomp Docker image and use the App on your local computer without any further installation.
3. Clone the POPScomp GitHub repository and compile POPSC and run the App on your local computer.
For source code and Wiki visit Fraternali Lab's POPScomp GitHub repository .
The POPScomp server is based on two software packages:
1. POPSC: A GNU Autotools package of the POPS C program.
2. POPSR: An R package containing this Shiny App.
POPScomp is part of the FunPDBe resources .
Users publishing results obtained with the program and its applications should acknowledge its use by citation.
Fraternali, F. and van Gunsteren, W.F. An efficient mean solvation force model for use in molecular dynamics simulations of proteins in aqueous solution. Journal of Molecular Biology 256 (1996) 939-948. DOI Pubmed
Usage of the software and server is free under the GNU General Public License v3.0.
2002-2020 Franca Fraternali (author, maintainer)
2008-2020 Jens Kleinjung (author, maintainer)
2002 Kuang Lin and Valerie Hindie (translation to C)
2002 Luigi Cavallo (parametrisation)
* No PDB source input! - Enter PDB identifier or upload PDB file from local file system at the top of the side panel.
* Two PDB sources input! - Only one PDB source is accepted per computation. Refresh the browser page and either speficy a PDB identifier or upload a PDB file, not both.
* 0 - Success
* 1 - Catchall for general errors
* 2 - Misuse of shell builtins (according to Bash documentation
* 126 - Command invoked cannot execute
* 127 - Command not found
* 128 - Invalid argument to exit
* 128+n - Fatal error signal 'n'
* 130 - Script terminated by Control-C
* 255* - Exit status out of range
The PDB file could not be read, most possibly because something went wrong during up/down-loading. If you used the 'Enter PDB entry' field, check your internet connection.