Repository navigation
Conversation
…st show in the annotation The m.315 C>CC call is the m.310 T>TC insertion ClinVar and gnomAD list, and m.308 CC>C is m.302 AC>A; today neither meets its record. A run whose NuMT filter had no autosomal depth must say so in the table. Both tests fail on main. Bead: lin-35 Bead: lin-32
… a NuMT filter without depth og mito annotate matched an indel only on its exact trimmed spelling, and looked for ClinVar's record at most one base away, so m.315 C>CC never met the m.310 T>TC record of the same poly-C insertion. When the exact spelling finds nothing, both sides are now moved to the left end of their repeat on the rCRS (embedded, GRCh38's chrM, MD5 c68f5267...) and matched there. An exact match still wins, so every table that matched before is unchanged; an allele whose REF is not the rCRS is not moved. ClinVar's chrM records are now read whole, since a record can sit anywhere in its repeat. --numt-default adds a '# numt' header line: the NuMT filter used a default depth (0) and marked nothing. Without it the table is as before. Bead: lin-35 Bead: lin-32
…mal depth Step 20 already warned; it now passes --numt-default to og mito annotate when neither mosdepth output nor AUTOSOMAL_COVERAGE gives a depth. The Nextflow MITO_VARIANTS prints its message as a WARNING on stderr, and MITO_VARIANTS_ANNOTATE passes --numt-default when mosdepth is not in --tools, the one case where MITO_VARIANTS has no depth files. The fake-docker case checks both paths and fails on main. Bead: lin-32
Bead: lin-35 Bead: lin-32
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
…epth A successful task's stderr stays in its work directory, so the MITO_VARIANTS WARNING never reached a Nextflow user. The workflow now says it with log.warn when mito_variants runs without mosdepth.
left_allele trimmed first, so m.314 CG>CCG passed as C>CC on the rCRS and met m.310's record. The docs now say the table writes the trimmed spelling, not the moved one.
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.
GeiserX#536