Closed btmonier closed 1 month ago
@btmonier Should we add a diagram to the documentation? I think I had posted one, which I can look for if you don't have it.
Also, did you want to add any information about other variant callers, e.g. Octopus or Clair3? I had the comparison document here: https://docs.google.com/document/d/181wfF55q7FyhQNfUNyEK3CqGNAeJ9zKZXE6qJk8Wjd0/edit?tab=t.0#heading=h.1718lhxeqy60
@btmonier Should we add a diagram to the documentation? I think I had posted one, which I can look for if you don't have it.
Also, did you want to add any information about other variant callers, e.g. Octopus or Clair3? I had the comparison document here: https://docs.google.com/document/d/181wfF55q7FyhQNfUNyEK3CqGNAeJ9zKZXE6qJk8Wjd0/edit?tab=t.0#heading=h.1718lhxeqy60
Since this update was taking longer than expected, I was going to hold off on adding images for now. This will probably be included in the next wave of updates.
Also, did you want to add any information about other variant callers, e.g. Octopus or Clair3? I had the comparison document here: https://docs.google.com/document/d/181wfF55q7FyhQNfUNyEK3CqGNAeJ9zKZXE6qJk8Wjd0/edit?tab=t.0#heading=h.1718lhxeqy60
Will add to next PR
Description
This PR updates the resequencing documentation to better "flow" with the prior "Building and Loading" and "Imputation" docs.
Type of change
What type of changes does your code introduce? Put an
x
in boxes that apply.CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Checklist:
Changelog entry
Please add a one-line changelog entry below. This will be copied to the changelog file during the release process.