epam / epam/Indigo

Dearomatization doesn't work if "Implicit H count" value greater than 2 if atom with Aromaticy query feature present on the canvas

Open
#1,757 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Priority: Low Query features
Dominant language
C++
Stars
406
Forks
134
Avg merge
2d 11h
Merged PRs (30d)
24

Description

Describe the bug
Dearomatization doesn't work if "Implicit H count" value greater than 2

Steps to Reproduce

  1. Load from file (unzip first): Dearomatization doesn't work if Implicit H count value greater than 2 if atom with Aromaticy query feature present on the canvas.zip
    image
  2. Press Aromatize button (Ctrl+Alt+A)
  3. Press Dearomatize button (Ctrl+Alt+D)

Actual behavior
Dearomatization doesn't work if "Implicit H count" value greater than 2
image

Expected behavior
Dearomatization should work according to https://en.wikipedia.org/wiki/H%C3%BCckel%27s_rule

Environment details (please complete the following information):

  • Indigo Toolkit Version 1.18.0-rc.9.0-gc7efb4e71-wasm32-wasm-clang-12.0.0
  • Ketcher Version 2.18.0-rc9 Build at 2024-02-27; 16:16:47
  • Chrome Version 122.0.6261.70 (Official Build) (64-bit)
  • Win10
  • Issue found while testing https://github.com/epam/Indigo/issues/1446

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure using the attached archive and the Aromatize and Dearomatize actions in the reported Ketcher/Indigo WASM environment. Trace the Indigo dearomatization entry point for the molecule containing an Aromaticy query feature and implicit H count greater than 2; done means the attached structure dearomatizes successfully according to the stated Hückel-rule expectation.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, wasm
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.