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

Allow skipping files that do not exist during merge. #89

Closed
donaldcampbelljr opened this issue Feb 14, 2025 · 0 comments · Fixed by #92
Closed

Allow skipping files that do not exist during merge. #89

donaldcampbelljr opened this issue Feb 14, 2025 · 0 comments · Fixed by #92

Comments

@donaldcampbelljr
Copy link
Member

@nleroy917 Good idea. By the time the program gets this far, it has checked that the chromosomes exist in the bam file. However, it could raise an error during writing to the bed file line by line, but we should see this error in the terminal (which I don't in this case). We could skip that file. As long as the program communicates that it was expecting a chromosome file but didn't find one that would be fine. Currently, the messaging is inadequate either way as I'm not sure which chrom failed from the backtrace. :) Also, I would think the consumer handle would produce an empty file either way by this point.

Originally posted by @donaldcampbelljr in #74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant