Closed davmlaw closed 1 month ago
I can provide a better error message but is it more appropriate for the program to run over such a VCF or to break and let you know that you either have a broken VCF and/or you are providing the wrong fasta reference or chain file?
You have a good point in that potentially someone could mix up the VCF/references, which would be caught by the error.
In my case, it was historical hand typed data, which I should have pre-processed.
I have changed my mind and think catching the reference mixup is more important than not relying on people providing a valid VCF, so am happy to close the issue
A single record out of range (chr17 contig size is 83,257,441):
Expected:
Actual:
Entire program exits with message:
Output:
Workaround