FGF14 motifs #284
Draft
FGF14 motifs #284
Conversation
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
✅ Deploy Preview for strchive ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Name
Egor Dolzhenko
Username
@egor-dolzhenko
Email
[email protected]
Description
The current FGF14 motifs
GAAGGAandGAAGAAGAAGAAGCAare one base away from a perfect GAA repeat. We recently reviewed a case where reads contained some sporadic C -> A mismatches, turning GAAs into GCAs. This had a significant impact on motif segmentation and made the repeat appear much more mosaic than it actually is. I wanted to suggest replacingGAAGGAandGAAGAAGAAGAAGCAmotifs withGGAandGCAto remove these segmentation ambiguities and reduce the risk of confusion. What do you think?