Adding initial draft of ww-mosdepth WILDS WDL module#356
Draft
tefirman wants to merge 4 commits into
Draft
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
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.
Type of Change
Description
Adds an initial draft of the
ww-mosdepthmodule, wrapping mosdepth (Pedersen & Quinlan, 2018) for fast per-base, per-region, and per-window coverage depth calculation from BAM/CRAM alignments. The module exposes a singlecalculate_depthtask with optional reference FASTA (for CRAM), optional regions BED, and a configurable window size (default 100bp). Uses the pinnedgetwilds/mosdepth:0.3.14container image, includes a zero-configtestrun.wdlthat pulls test data viaww-testdata, and ships a README documenting inputs, outputs, usage, and citation.Testing
How did you test these changes?
Ran
testrun.wdlwith auto-provisioned test BAM and hg38 chr1 reference fromww-testdata, scattered over a single demo sample.What workflow engine did you use?
Sprocket locally; CI will exercise Cromwell, miniWDL, and Sprocket.
Did the tests pass?
Yes.
Documentation
make docs-previewto check documentation rendering (if applicable)