This is a read-only mirror of pymolwiki.org
Difference between revisions of "Pdb conect nodup"
Jump to navigation
Jump to search
(add see also (Pdb_conect_all and Pdb_use_ter_recordsl)) |
m (3 revisions) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 16: | Line 16: | ||
=== See Also === | === See Also === | ||
| − | [[ | + | [[Pdb_Conect_All]], [[Pdb_use_ter_records]] |
[[Category:Settings|pdb_conect_nodup]] | [[Category:Settings|pdb_conect_nodup]] | ||
Latest revision as of 01:04, 19 October 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
- PyMOL user mailing list discussion on pdb_conect_nodup: http://sourceforge.net/p/pymol/mailman/message/32735483/
- 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