Opened 5 years ago
Closed 5 years ago
#3858 closed defect (not a bug)
Hybrid-36 chain assignment fails when 2-char chain ID includes a numeral
| Reported by: | Tristan Croll | Owned by: | Eric Pettersen |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Input/Output | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
(Failed to submit via ChimeraX - looks like the server is down). Anyway, this model is once again confidential, so please remove from the list. It's in the Phenix Hybrid-36 format. ChimeraX appears to get the two-character chain ID right for all chains other than H1 or H2 - these are assigned as chains 1 and 2, with 4-character residue IDs.
Change History (5)
comment:1 by , 5 years ago
| Component: | Unassigned → Input/Output |
|---|---|
| Owner: | set to |
| Platform: | → all |
| Project: | → ChimeraX |
| Status: | new → accepted |
comment:2 by , 5 years ago
comment:3 by , 5 years ago
From #3857:
Hmm... phenix.pdb_as_cif messes this up as well (chains H1 and H2 both become simply H). Will check with them whether these chain IDs are simply not allowed by the format.
comment:4 by , 5 years ago
from #3859:
Hmm... could swear the first time I tried this, both H1 and H2 failed, but with repeated attempts it was only H1. Turns out this is the first two-character chain in the PDB - if I rearrange it so that H1 and H2 come after the first two-letter chain, then it appears to read correctly. Strangely, chain C1 seems to work fine despite being the new first chain (and Phenix handles C1 correctly as well).
comment:5 by , 5 years ago
| Resolution: | → not a bug |
|---|---|
| Status: | accepted → closed |
You need a TER card between the end of chain H1 and the start of chain C1.
Attachment deleted as per request