Minor fix/enhancement for VariantEval: if a vcf has symbolic alleles, program would crash ungracefully - now we'll just skip record without processing. This is a big issue since we can't process 1000G integration files with code as is.
This commit is contained in:
parent
f75573dd54
commit
93f7e632bd
|
|
@ -130,6 +130,10 @@ public class CountVariants extends VariantEvaluator implements StandardEval {
|
||||||
nVariantLoci++;
|
nVariantLoci++;
|
||||||
nMixed++;
|
nMixed++;
|
||||||
break;
|
break;
|
||||||
|
case SYMBOLIC:
|
||||||
|
// ignore symbolic alleles, but don't fail
|
||||||
|
// todo - consistent way of treating symbolic alleles thgoughout codebase?
|
||||||
|
break;
|
||||||
default:
|
default:
|
||||||
throw new ReviewedStingException("Unexpected VariantContext type " + vc1.getType());
|
throw new ReviewedStingException("Unexpected VariantContext type " + vc1.getType());
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue