-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more entry points to the workflow #261
Comments
break this down into smaller issues
|
I've made a draft version of this. This is just to have something concrete to look at - I don't think it's necessarily the right way, as I don't know the pipeline that well.
Incomplete:
Problem:
See changes in my fork fa2k@ff78904 |
I've made it run with both the existing test and a new test for bam input (and cleaned up a bit). The test outputs are not identical, but I've checked two vcf files:
check_samplesheet.py I made a polymorphic RowChecker - it's a bit strange and we can consider alternatives. Overall, here's the changes compared to the dev branch: dev...fa2k:raredisease:multiple-entry-points The test_bam profile requires an override sample sheet, and needs bam file to exist locally. |
I have updated to integrate the upstream changes from |
Any updates on this feature? Starting from bam-files would be extremely useful. |
Sorry for the late reply. As far as I know, there is no work that has been started. I'm even unlikely to start in the near future. I still need it, and will start eventually if nobody else takes it. |
I'd happily share the logic with have in Sarek for this, and really we should converge on more subworkflows and bits of code for this kind of things |
Description of feature
It would be nice to have entry points for different parts of the pipeline ex. snv/sv annotation, mitochondrial analysis.
The text was updated successfully, but these errors were encountered: