We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I ran the latest version of cnvkit via docker with these settings:
cnvkit.py batch -n -f REF.fasta -m hybrid -g ACCESSIBLEREGIONS.bed -t PROBESBED.bed --target-avg-size 50000 --antitarget-avg-size 4000000 --antitarget-min-size 1000000
However, it is producing a target.bed file whose average bin size is only 122.79 bp. This should not be possible based on the above settings.
This is with hg38.
So there appears to be a bug in the way batch interprets these parameters: --target-avg-size 50000
Or is this because bins cannot encompass more than one target? If so, I assume then that the segment step integrates information across multiple bins?
Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I ran the latest version of cnvkit via docker with these settings:
cnvkit.py batch -n -f REF.fasta -m hybrid -g ACCESSIBLEREGIONS.bed -t PROBESBED.bed --target-avg-size 50000 --antitarget-avg-size 4000000 --antitarget-min-size 1000000
However, it is producing a target.bed file whose average bin size is only 122.79 bp. This should not be possible based on the above settings.
This is with hg38.
So there appears to be a bug in the way batch interprets these parameters:
--target-avg-size 50000
Or is this because bins cannot encompass more than one target? If so, I assume then that the segment step integrates information across multiple bins?
Thanks
The text was updated successfully, but these errors were encountered: