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
acepentalene aromaticity perception #2895
Comments
Sorry I didn't manage to get to this on the mailing list. I agree that what's currently happening is definitely not right. |
I didn't understand the discussion about antiaromaticity on the list or in the wikipedia article. That's a 10 pi electron system and, based on the way the RDKit counts electrons, should be aromatic. |
I've emailed Peter about your response, since he's the one who made that comment. And because I still don't know enough about aromaticity perception to provide reasonable feedback. |
probably better to have the discussion on the list. I will reply there now |
Publication by Paul v.R. Schleyer (https://pubs.acs.org/doi/pdf/10.1021/jo980089f) demonstrates anti-aromaticity of acepentalene using ab-initio NMR shift calculations. (NICS). Abstract also mentions that acepentalene is non-planar. |
Quick summary of the discussion on the list: |
Configuration:
Description:
Take a look at the following, which uses the SMILES from https://en.wikipedia.org/wiki/Acepentalene :
Why is there an aromatic "c" in the fused center of the 3 5-membered rings. It's connected by non-aromatic bonds to the rest of the system.
This broke some code of mine which expects that every aromatic atom must have at least two aromatic bonds. I thought that all aromatic atoms had to be in aromatic rings, and that all aromatic rings had to have aromatic bond.
I searched for "acepentalene" and "antiaromatic" in the issue tracker and the mailing list but found nothing relevant.
I brought this up on the mailing list. Peter Shenkin further commented:
There was no other response to the thread, so I'm posting here for when someone has time to look into it further.
The text was updated successfully, but these errors were encountered: