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
Generate NonStandard InChI #253
Comments
@vedina have you been able to confirm if this is a dependency problem? |
it certainly affects cdk 1.5.14 and not cdk 1.5.13. had not checked if the underlying inchi library is different - is it? |
No it's not - but there are lots of test cases that generate non-standard InChIs thats didn't fail. Can you check on 2.0-SNAPSHOT. John |
Oh and I added you exact test case to check - the output is correct: |
@vedina will close 1 day please let me know if you want to keep open |
will check during the weekend, there was a problem when upgrading to 1.5.14 |
@johnmay here is the test Works with cdk <=1.5.13, fails with 1.5.14 . There is maven profile for CDK versions . |
@johnmay it's weird, the tests (including the one in CDK) fail only on Windows machines (both JDK 7 and 8). In fact other tests in the cdk/storage/inchi folder are also failing on Windows. Any hints what might have changed since 1.5.13 will be very useful!
|
Ahhhh that makes more sense. Putting this together with something I saw on the InChI mailing list. InChI in it's infinite wisdom has different syntax depending on the OS. Windows uses '/' and everything else uses '-'. Windows: When we modified the handling to allow the 15T/KET etc I added output as '-KET -15T' etc. I really thought the '/' was not needed at the API level... but apparently this is the case. I'll get this fixed ASAP, hopefully by tomorrow. Here (https://github.com/cdk/cdk/blob/master/storage/inchi/src/main/java/org/openscience/cdk/inchi/JniInChIInputAdapter.java#L79) the '-' needs to be replaced with a constant based on OS (like line separation). |
I'see .... |
1.5.14 has issue with inchi on windows cdk/cdk#253
Via Nina:
The text was updated successfully, but these errors were encountered: