fix: increase GREM1 stretch #13
Merged
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
RenanWA
approved these changes
Nov 11, 2025
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.
card: https://trello.com/c/8jWAE3SQ/414-altera%C3%A7%C3%A3o-no-c%C3%A1lculo-de-cobertura
Atualmente, a
bioinfo-sapienscalcula as coberturas por gene, usando o arquivocoverages.json, que resulta da intersecção entre as regiões representadas emgenes.bede as regiões do arquivo de referência de targets do kit. Recentemente, entraram reanálises de GSPv1 com apenas o gene GREM1. Este só tem alvos na sua região promotora, de modo que a cobertura horizontal saiu como zero, mesmo com os targets estando bem cobertos.Nest PR iremos expandir o start do gene GREM1 em
genes.bedpara cobrir as suas regiões promotoras.