Mousing over any column name shown in link font will provide more information on the data it contains
There is a window at the bottom of the page where you can entery SQL queries and view the results in a number of formats
| viper_residue_contact | |||||
| viper_residue_contact is a derived data table. For each entry, the pairwise residue contacts at all unique interfaces between capsid protein subunits was calculated and recorded in this table. | |||||
| Field | Type | Null | Key | Default | Extra |
| viper_residue_contact_key | int(11) | NO | PRI | auto_increment | |
| entry_key | int(11) | YES | MUL | ||
| entry_id | varchar(32) | YES | MUL | ||
| layer_key | int(5) unsigned | YES | |||
| layer_name | varchar(10) | YES | |||
| auth_1_seq_id | smallint(5) unsigned | YES | |||
| auth_1_comp_id | varchar(255) | YES | |||
| auth_1_asym_id | varchar(255) | YES | |||
| auth_2_seq_id | smallint(5) unsigned | YES | |||
| auth_2_comp_id | varchar(255) | YES | |||
| auth_2_asym_id | varchar(255) | YES | |||
| res_type_1 | varchar(5) | YES | |||
| res_type_2 | varchar(5) | YES | |||
| viper_matrix_1 | int(11) | YES | |||
| viper_matrix_2 | int(11) | YES | |||
| com_dist | double | YES | |||
| dist_cutoff | double | YES | |||
| interface_type | varchar(10) | YES | |||
| symmetry | int(11) | YES | |||
Note: Only SELECT, SHOW or DESCRIBE queries can be performed, any other command will generate an error
 |
 |
|
|
Main |
Data & Analysis |
Utilities |
Search |
Contact Us |
Help |
Links |
Mailing List |
Cite VIPERdb |
Disclaimer
|
|
