Command error:
Picked up JAVA_TOOL_OPTIONS: -Xlog:disable -Xlog:all=warning:stderr
VcfFileIterator.parseVcfLine(133): Fatal error reading file 'input.vcf.gz' (line: 3555):
chr12 31601499 severus_INV2850 N <INV> 60 PASS IMPRECISE;SVTYPE=INV;SVLEN=173;CHR2=chr12;END=31601326;STRANDS=++;DETAILED_TYPE=.;MAPQ=60;CLUSTERID=severus_6 GT:GQ:VAF:hVAF:DR:DV 0/0:959:0.05:1,0,0:79:4
java.lang.RuntimeException: java.lang.RuntimeException: INFO field 'END' is before varaint's 'POS'
END : 31601325
POS : 31601498
at org.snpeff.fileIterator.VcfFileIterator.parseVcfLine(VcfFileIterator.java:134)
at org.snpeff.fileIterator.VcfFileIterator.readNext(VcfFileIterator.java:185)
at org.snpeff.fileIterator.VcfFileIterator.readNext(VcfFileIterator.java:58)
at org.snpeff.fileIterator.FileIterator.hasNext(FileIterator.java:123)
at org.snpeff.snpEffect.commandLine.SnpEffCmdEff.annotateVcf(SnpEffCmdEff.java:473)
at org.snpeff.snpEffect.commandLine.SnpEffCmdEff.annotate(SnpEffCmdEff.java:139)
at org.snpeff.snpEffect.commandLine.SnpEffCmdEff.run(SnpEffCmdEff.java:918)
at org.snpeff.snpEffect.commandLine.SnpEffCmdEff.run(SnpEffCmdEff.java:875)
at org.snpeff.SnpEff.run(SnpEff.java:1141)
at org.snpeff.SnpEff.main(SnpEff.java:160)
Caused by: java.lang.RuntimeException: INFO field 'END' is before varaint's 'POS'
END : 31601325
POS : 31601498
at org.snpeff.vcf.VcfEntry.parseEnd(VcfEntry.java:1187)
at org.snpeff.vcf.VcfEntry.parse(VcfEntry.java:1027)
at org.snpeff.vcf.VcfEntry.<init>(VcfEntry.java:247)
at org.snpeff.fileIterator.VcfFileIterator.parseVcfLine(VcfFileIterator.java:131)
... 9 more
Operating System
Other Linux (please specify below)
Other Linux
Rocky Linux v8.6
Workflow Version
v1.2.1
CLI command run
Workflow Execution - CLI Execution Profile
None
What happened?
We are getting errors due to END<POS
This was reported as fixed for the v0.5.0 release (https://github.com/epi2me-labs/wf-somatic-variation/releases/tag/v0.5.0). This is the relevant commit:
https://github.com/epi2me-labs/wf-somatic-variation/commit/787084c0349f035657dad8f21ba538713ae3805f
However,
I think when severus was swapped for nanomonsv - this filter is no longer implemented, leading to errors.
This is also related to the following discussion point:
https://github.com/KolmogorovLab/Severus/issues/11
Relevant log output