Compatible Chain IDs about ngl HOT 5 CLOSED

Hi, thanks for your report.

Yes, I think NGL should use the author supplied names when possible. It is currently not coherent, e.g. auth_seq_id is used but not auth_asym_id. I will look into changing it. There needs to be a fallback if auth_asym_id is not there as it is not required, but label_asym_id is required. Moreover, some data in the mmcif file is linked by the label_asym_id (_pdbx_struct_assembly_gen.asym_id_list), so that field need to be read anyway.

from ngl.

Hi, thanks for your prompt reply.

I put in a dirty hack in my copy for now, to allow my development to continue. I'm not sure if or when I will run into issues because of that. I look forward to your proper fix whenever you get a chance. Next on my list is to extend it's API to support a more convenient to me syntax of custom coloring residues. I can do a pull request for that, but I understand if you don't accept it. That's the beauty of JavaScript, I don't need anything officially added to do it. I can extend at run time.

This project is a lifesaver. I have been using Jmol, but Java is dead. Chrome dropped support, Firefox will be dropping Java support soon, and may other browsers don't have Java support either. JSmol is too slow for large molecules without WebGL. Unless they get serious about making their WebGL version work, NGL Viewer is the best option for sure.

from ngl.

Fixed this in commit 8afe455. Testing appreciated. With that auth_asym_id is used instead of label_asym_id as the chainname. Additionally I made sure that label_asym_id in _pdbx_struct_assembly_gen.asym_id_list and in other places is mapped to the corresponding auth_asym_id during parsing.

from ngl.

Next on my list is to extend it's API to support a more convenient to me syntax of custom coloring residues. I can do a pull request for that, but I understand if you don't accept it.

Please do make a PR or open an issue. I am very happy to discuss the API!

from ngl.

OK great. I'm working on some other parts of my program right now. When I get back to NGL, I will switch to your dev version, test your changes, and develop my api feature.

from ngl.