#6095-antisense-creating-work-if-ambiguous-chem-present-in-the-chain-… - #11895
Open
armankarapetyan-svg wants to merge 1 commit into
Conversation
This was
linked to
issues
Sep 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…selection
How the feature works? / How did you fix the issue?
(Screenshots, videos, or GIFs, if applicable)
Creating an antisense strand failed / produced wrong output when the sense chain contained an ambiguous CHEM monomer
Root cause was in
DrawingEntitiesManager.createAntisenseChain:AmbiguousMonomerthe same way it treats a modified phosphate, unconditionally substituting it with the non-modified phosphate library item. This caused ambiguous CHEM monomers to be replaced byPin the antisense strand instead of being mirrored as-is.monomerClassis actuallyPhosphate, the fallback path usedmonomer.monomerItemto recreate the ambiguous monomer on the antisense strand. That object doesn't carry themonomersarray thatAmbiguousMonomerrequires internally, causing:Cannot read properties of undefined (reading 'map')inAmbiguousMonomer.getAttachmentPoints.Fix:
Phosphateor an ambiguous monomer whosemonomerClass === KetMonomerClass.Phosphate.monomer.variantMonomerItem(the original library item, which includes themonomersarray) instead ofmonomer.monomerItemwhen creating the antisense counterpart.Result: selecting a chain with an ambiguous CHEM monomer and creating an antisense strand now mirrors the ambiguous CHEM node as-is (matching the expected screenshot), instead of erroring out or incorrectly replacing it with a phosphate.
Screen.Recording.2026-09-15.110846.mp4
Check list
#1234 – issue name