We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
if a rxn file contains agents the function ParseV3000RxnBlock stops with the error message "BEGIN AGENT line not found",
see line 271:
if (tempStr.length()< 14 || tempStr.substr(0, 14) != "BEGIN AGENT") { throw FileParseException("BEGIN AGENT line not found"); }
the string length should be compared with 11 instead of 14.
the same in line 298:
if (tempStr.length() < 12 || tempStr.substr(0, 12) != "END AGENT") { throw FileParseException("END AGENT line not found"); }
please replace 12 by 9
Thanks Brigitte
The text was updated successfully, but these errors were encountered:
Thanks good catch and diagnosis.
Sorry, something went wrong.
fixes rdkit#4183
d07daca
Update testReaction.cpp
654c977
added testcase fixes rdkit#4183
21f6b88
Update MDLParser.cpp (#4218)
e46dbed
* Update MDLParser.cpp Fix length of expected strings "BEGIN AGENT" and "END AGENT" * Add files via upload * Delete v3k_with_agents.rxn * fixes #4183 * Update testReaction.cpp added testcase fixes #4183
bp-kelley
No branches or pull requests
Error reading rxn files in V3000 format that contains agents
if a rxn file contains agents the function ParseV3000RxnBlock stops with the error message "BEGIN AGENT line not found",
see line 271:
if (tempStr.length()< 14 || tempStr.substr(0, 14) != "BEGIN AGENT") {
throw FileParseException("BEGIN AGENT line not found");
}
the string length should be compared with 11 instead of 14.
the same in line 298:
if (tempStr.length() < 12 || tempStr.substr(0, 12) != "END AGENT") {
throw FileParseException("END AGENT line not found");
}
please replace 12 by 9
Thanks
Brigitte
The text was updated successfully, but these errors were encountered: