Don't give warning when no/little reads map to antitarget region.

[dodoflyy]

Here

Processing antitarget: AHKYT7DSXX_S73_L001_BQSR
Keeping 0 of 40893 bins
WARNING: most bins have no or very low coverage; check that the right BED file was used

I don't think this should give warning. It's normal thing that little reads cover antitarget region.

[etal]

If you used hybrid capture, then there should be at least a few reads in the antitarget regions. The warning usually kicks in when off-target coverage is vanishingly low. Do you know your off-target coverage in this sample?

This check is in place to see if you used ran the pipeline for hybrid capture (default, batch -m hybrid), but the sequencing data actually came from targeted amplicon sequencing where there are truly no off-target reads. In the latter case, you can use batch -m amplicon to skip antitargets.

[etal]

Warning is intentional; answered. Closing as answered — please reopen, or open a new issue, if a concrete problem remains.

For general usage questions, we now use GitHub Discussions (Q&A): https://github.com/etal/cnvkit/discussions