Skip to content
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

Change behaviour of varfish_export with path_exon_bed #389

Closed
holtgrewe opened this issue Apr 19, 2023 · 0 comments · Fixed by #390
Closed

Change behaviour of varfish_export with path_exon_bed #389

holtgrewe opened this issue Apr 19, 2023 · 0 comments · Fixed by #390

Comments

@holtgrewe
Copy link
Member

Is your feature request related to a problem? Please describe.
The varfish_export step currently relies on the the library type on using the BED file for filtering the variants to exons etc.

Describe the solution you'd like
Remove the is_wgs check in the code and only rely on the path_exon_bed setting.

Describe alternatives you've considered
N/A

Additional context
N/A

@holtgrewe holtgrewe changed the title Change behaviour Change behaviour of varfish_export with path_exon_bed Apr 19, 2023
holtgrewe added a commit that referenced this issue Apr 20, 2023
Previously, the BED file value was always used for WGS data and never
used for WES data.  Now, it is used when it has been provided (not
the empty string and not null/None).
This was referenced Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant