-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MOL file bond types aromatic single (6) and aromatic double (7) not recognized #2
Comments
The error is propagating from InChI itself, which returns a molecule with no atoms: https://github.com/metamolecular/inchi-js/blob/master/src/inchi.c#L34 The aromatic bond are only valid for queries. As the CTfile Formats documentation states in the Bond Block table:
|
Isn't a lot of what this is about "queries"? I understand you are saying On Wed, Mar 9, 2016 at 12:22 PM, Richard Apodaca [email protected]
Robert M. Hanson If nature does not answer first what we want, -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 |
Although the request is simple, the solution is not. InChI.js is the actual InChI C library, compiled to JavaScript. The C file I linked is a thin wrapper that the JavaScript runtime communicates with. All InChI.js is doing is handling an error propagated from the InChI C library. The InChI team might be in a position to address your request, though. |
Sure, that makes sense. OK. On Wed, Mar 9, 2016 at 1:12 PM, Richard Apodaca [email protected]
Robert M. Hanson If nature does not answer first what we want, -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 |
MOL files created using some software use the "single or aromatic" (6) and "double or aromatic" (7) bond types as described in http://accelrys.com/products/informatics/cheminformatics/ctfile-formats/no-fee.php
The presence of these bond types causes a loading error:
Molfile is invalid.
But these would be easily interpreted as "single" and "double", respectively. Suggestion is to read bond type 6 as single and bond type 7 as double
The text was updated successfully, but these errors were encountered: