Re: Hybrid-36 chain assignment fails when 2-char chain ID includes a numeral

[Tristan Croll]

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).
________________________________
From: Tristan Croll <tic20@cam.ac.uk>
Sent: 21 October 2020 15:25
To: ChimeraX-bugs@cgl.ucsf.edu <ChimeraX-bugs@cgl.ucsf.edu>
Subject: Re: Hybrid-36 chain assignment fails when 2-char chain ID includes a numeral

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.
________________________________
From: Tristan Croll
Sent: 21 October 2020 14:38
To: ChimeraX-bugs@cgl.ucsf.edu <ChimeraX-bugs@cgl.ucsf.edu>
Subject: Hybrid-36 chain assignment fails when 2-char chain ID includes a numeral

(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.