Opened 7 years ago
Closed 5 years ago
#1878 closed enhancement (fixed)
Smarter handling of ATOM/HETATM column 21
| Reported by: | Owned by: | Eric Pettersen | |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Input/Output | Version: | |
| Keywords: | Cc: | Elaine Meng, jacob_r_anderson@… | |
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
Column 21 of ATOM/HETATM records is not officially assigned a meaning and currently is interpreted as the fourth character of the residue name (useful for Amber-compatible terminal residue names). COOT (and possibly other programs) use that column as part of a two-character chain ID instead. The proposal to try to allow for that is:
On input: if that column produces consistent 2-character chain IDs with each TER-card-delimited section, then treat as part of chain ID, otherwise as part of residue name (moot if column is all spaces of course).
On output: If multi-character chain IDs in use, use as chain ID, otherwise as part of residue name.
Change History (8)
comment:1 by , 7 years ago
comment:2 by , 6 years ago
Refine the "on output" part to: if possible map the 2-character chain IDs to unique 1-character chain IDs (in case a subset of a larger structure is being written), otherwise use the 2-character chain IDs
follow-up: 3 comment:3 by , 6 years ago
Hi, Does it mean that current version of chimerax accept two-letter ID in Pdb format? Perhaps you already noticed that both coot and Phenix accept this format now. Best regards Pu Qian On Wed, 17 Jul 2019 at 21:02, ChimeraX <ChimeraX-bugs-admin@cgl.ucsf.edu> wrote:
comment:5 by , 5 years ago
| Cc: | added |
|---|
follow-up: 6 comment:6 by , 5 years ago
Hi Eric, Thanks for your email and for responding to my request on the 21 column for two-letter ID. I noticed that ChimeraX accepts two-letter chain IDs. How about Chimera? Best regards Pu Qian On Mon, 15 Jun 2020 at 18:15, ChimeraX <ChimeraX-bugs-admin@cgl.ucsf.edu> wrote:
comment:7 by , 5 years ago
Hi Pu Qian,
Chimera only allows multi-character chain IDs if the input is mmCIF, not PDB -- which is what this ticket is about. Chimera is probably never going to support multi-character chain IDs because the assumption that chain IDs are a single character occurs throughout Chimera's code. That's one of the reasons we wrote ChimeraX -- to handle modern-size structures better.
--Eric
comment:8 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Tomorrow's build will have code to read/write two-character chain IDs in PDB files.
This is an innovation that was introduced by PHENIX some time back, part of their "Hybrid-36" format - see http://cci.lbl.gov/hybrid_36/.