<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Helvetica, Arial, sans-serif">In addition, the PDB
standard, as defined by the wwPDB consortium, specifies that the
chain ID is a single character in the record. Just because COOT
breaks the standard does not mean Chimera should.<br>
<br>
<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 4/17/19 1:27 PM, Eric Pettersen
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:38869DCC-5C79-417F-9C2A-4C37F698FA91@cgl.ucsf.edu">
<pre class="moz-quote-pre" wrap="">We are discussing possible options internally, but FYI Amber and Amber-compatible programs frequently make use of 4-character residue names for terminal amino acids (e.g. NALA, CALA).
—Eric
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Apr 17, 2019, at 1:01 AM, Pu Qian <a class="moz-txt-link-rfc2396E" href="mailto:p.qian@sheffield.ac.uk"><p.qian@sheffield.ac.uk></a> wrote:
Hi Eric Pettersen,
Thanks for your emails.
I understand that current version of chimera still only use one letter ID, and column 21 is for 4-letter residues. The problem is: in current version of COOT, user can assign two-letter to a polypeptide, and the column 21 is used for it. When pdf file was output from COOT, than chimera can not use the pdb file as we expected. It could be better to use column 21 for two-letter ID. After all, very few people will use 4-letter residues. In this way, chimera still can be used for visualisation of the COOT two-letter ID pdb file, which can be convert to mmCIF format. Before conversion, we need to view it making sure there are no problems. Otherwise, it is not convince for uses who are working on bigger complex that has more than 62 polypeptides.
Best regards
Dr. Pu Qian
---------------------------------------------------------------------------------------------
To elaborate a little on this, column 21 in an ATOM record is unassigned and Chimera conscripts that column to allow for 4-character residue names rather then 2-character chain IDs (the former were more far common a million years ago when Chimera was originally designed). So knowing that that column is part of the residue name may help you work around some things. For instance PDB residue name LIG in chain AB will be treated by Chimera as residue name LIGA in chain B (so, an atom spec of :LIGA.B rather than :LIG.AB).
?Eric
Eric Pettersen
UCSF Computer Graphics Lab
_______________________________________________
Chimera-users mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Chimera-users@cgl.ucsf.edu">Chimera-users@cgl.ucsf.edu</a>
Manage subscription: <a class="moz-txt-link-freetext" href="http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users">http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
Chimera-users mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Chimera-users@cgl.ucsf.edu">Chimera-users@cgl.ucsf.edu</a>
Manage subscription: <a class="moz-txt-link-freetext" href="http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users">http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users</a>
</pre>
</blockquote>
<br>
</body>
</html>