-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
From the README:
Buggy tales
20190110.02 -- Empty InChI for products
- Checking results: some inchi string are empty, e.g.: rule (radius 0)
8a4666fc9dabapplied onMNXM366
8a4666fc9dab:([#6&v4:1]1:[#6&v4:2]:[#6&v4:3]:[#6&v4:4]:[#7&v3:5]:[#6&v4:6]:1)>>([#6&v4:1](-[#6&v4:2]-[#6&v4:3]:[#6&v4:4]-[#7&v3:5]-[#1&v1])(-[#6&v4:6](-[#7&v3](-[#1&v1])-[#1&v1])-[#1&v1])-[#1&v1])MNXM366:[H][O][c]1[c]([C]([H])([H])[H])[n][c]([H])[c]([C]([H])([H])[O][P](=[O])([O][H])[O][H])[c]1[C]([H])([H])[N]([H])[H]- Reason: sanitization issues of products (see below) leading to empty InChI.
[16:06:30] non-ring atom 2 marked aromatic 10/01/2019 16:06:30 -- WARNING -- Partial sanization only [16:06:30] ERROR: Unrecognized bond type: 0 [16:06:30] non-ring atom 2 marked aromatic 10/01/2019 16:06:30 -- WARNING -- Partial sanization only [16:06:30] ERROR: Unrecognized bond type: 0
- Reason: probably due to rule miss-encoding. Below are rule known to raise with bug (checked for radius 1, 3, 5, 7, 9, 10):
Count Rule_hash 15 24f4a1100077 57 300bddc687b7 15 88eee4c1d443 57 e9f88e91236e
- Consequences: probable wrong transformations.
- Workaround: reject all results from a couple substrate-rule as soon as an "empty" InChI is produced
- Fix: commit e980692 @ rule_fire
- Imply: take care of this situation in results already generated / rerun code and make new results (DONE: new results generated)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels