Skip to content
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

Disagreement between which element the spiro atom should be: Ru and C #26

Closed
dan2097 opened this issue Jan 24, 2016 · 1 comment
Closed
Labels
bug Something isn't working major

Comments

@dan2097
Copy link
Owner

dan2097 commented Jan 24, 2016

Original report by Anonymous.


Latest implementation presents above message when spiro involves transition metal center. No problem before server update of 21-23 Jan, 2016.

@dan2097
Copy link
Owner Author

dan2097 commented Jan 24, 2016

Original comment by Daniel Lowe (Bitbucket: dan2097, GitHub: dan2097).


Strictly speaking in IUPAC names when a spiro center involves a heteroatom that heteroatom is supposed to be specified in each of the individual rings (or the ruthenium should be applied to the complete spiro system i.e. be outside the spiro bracket). This change was designed to address the issue that it could be quite arbitrary which heteroatom was used when the rings are spiro fused.

In the case you had the intended interpretation was pretty clear so the message you're seeing, will now only occur in the case where the conflicting elements are heteroatoms.
This change is now live and the name in question should work.

BTW The OPSIN server has crashed a couple of times over the last few days since we've moved it to a new virtual machine. I'm still working to get to the bottom of what exactly the issue is although I'm still hopeful I'll figure it out next week. Nonetheless if reliability is important you may want to consider running OPSIN locally or running your own instance of the web service (depending on what your use case is) [even when working normally I tend to bring the public service down for a couple of minutes every few weeks to update it]

@dan2097 dan2097 closed this as completed Jan 24, 2016
@dan2097 dan2097 added major bug Something isn't working labels Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working major
Projects
None yet
Development

No branches or pull requests

1 participant