Difference between revisions of "Pdb conect nodup"

From PyMOLWiki
Jump to: navigation, search
(fix broken link to PDB page (conect format))
(add see also (Pdb_conect_all and Pdb_use_ter_recordsl))
Line 14: Line 14:
 
* Jmol support for bond order: http://wiki.jmol.org/index.php/Support_for_bond_orders
 
* Jmol support for bond order: http://wiki.jmol.org/index.php/Support_for_bond_orders
 
* Aromatic bonds are stored using four duplication of the same CONECT records, as specified in, for example, MOL format. See http://wiki.jmol.org/index.php/Support_for_bond_orders
 
* Aromatic bonds are stored using four duplication of the same CONECT records, as specified in, for example, MOL format. See http://wiki.jmol.org/index.php/Support_for_bond_orders
 +
 +
=== See Also ===
 +
[[Pdb_conect_all]], [[Pdb_use_ter_records]]
 +
 
[[Category:Settings|pdb_conect_nodup]]
 
[[Category:Settings|pdb_conect_nodup]]

Revision as of 19:30, 15 September 2015

Overview

The pdb_conect_nodup setting in pymol controls if duplicated connectivity record (CONECT) in saved PDB is used to stored bond order.

This is an unofficial PDB feature to store bond order and is supported by several applications that read PDB files, but may break PDB file loading in other applications which don't support it. PyMOL always wrote duplicated connect records (pdb_conect_nodup=0) and the setting allows you to switch that off (pdb_conect_nodup=1).

Syntax

get pdb_conect_nodup     # get current value 
set pdb_conect_nodup, 1  # no CONECT duplication is used to store bond order

Notes

See Also

Pdb_conect_all, Pdb_use_ter_records