You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, it's fairly common in large pdbs to have 2 letter chain names (I think up to 3 letters is possible, though I've never seen 3 supposedly they exist), and as far as I can tell voronota only reads in one letter for the chain name (if there are 2, only the first character will be read and the atom numbering can become strange). I'm aware there is some capability to rename the chains, but if only one character is used, there are pdbs that will have more chains than there are single character chain names, so 2 character chain names are sometimes necessary (especially if you are consolidating multiple models into one structure, which voronota does).
Are there any plans to make voronota compatible with 2 letter chain names?
The text was updated successfully, but these errors were encountered:
Thanks for the question, it is an important issue.
Longer chain names should be supported in case of input in mmCIF format, but the multi-character chain name usage is not tested extensively. Maybe you can provide some PDB IDs where the mmCIF input failed for you?
Hello, it's fairly common in large pdbs to have 2 letter chain names (I think up to 3 letters is possible, though I've never seen 3 supposedly they exist), and as far as I can tell voronota only reads in one letter for the chain name (if there are 2, only the first character will be read and the atom numbering can become strange). I'm aware there is some capability to rename the chains, but if only one character is used, there are pdbs that will have more chains than there are single character chain names, so 2 character chain names are sometimes necessary (especially if you are consolidating multiple models into one structure, which voronota does).
Are there any plans to make voronota compatible with 2 letter chain names?
The text was updated successfully, but these errors were encountered: