maickrau / MBG

MIT License
57 stars 2 forks source link

Crash in latest tip version #16

Closed skoren closed 1 year ago

skoren commented 1 year ago

I have a crash in some HiFi data w/the latest from the repo:

Building graph with reads:
  ../hifi-corrected.fasta.gz

MBG Branch master commit 6d99031a734ba92caa997e4167a1b8c36d3d2e85 2022-12-14 13:35:36 +0200
Parameters: k=1001,w=100,a=1,u=2,t=4,r=15000,R=4000,hpcvariantcov=25,errormasking=collapse-msat,endkmers=no,blunt=no,keepgaps=no,guesswork=yes,cache=no
Collecting hpc variant k-mers

and the end:

try resolve k=14407, replaced 0 nodes with 0 nodes
try resolve k=14732, replaced 0 nodes with 0 nodes
around center node 2324
Read close to assertion: SRR15243707.1.1241822.1
Read close to assertion: SRR15243707.1.408273.1
Read close to assertion: SRR15243707.1.286292.1
Read close to assertion: SRR15243707.1.273718.1
around edge node 2463
Read semi-close to assertion: SRR15243707.1.922481.1
Read semi-close to assertion: SRR15243707.1.1244239.1
Read semi-close to assertion: SRR15243707.1.1806475.1
around edge node 5716
Read semi-close to assertion: SRR15243707.1.1416649.1
Read semi-close to assertion: SRR15243707.1.125704.1
Read semi-close to assertion: SRR15243707.1.684411.1
Read semi-close to assertion: SRR15243707.1.897660.1
Read semi-close to assertion: SRR15243707.1.1610364.1
MBG: src/UnitigResolver.cpp:617: std::pair<UnitigGraph, std::vector<ReadPath> > resolvableToUnitigs(const ResolvableUnitigGraph&, const std::vector<PathGroup>&, const std::vector<ReadPathInfo>&): Assertion `coverages[i][j] > 0' failed.
/var/spool/slurm/slurmd/job55696171/slurm_script: line 34: 104763 Aborted                 /data/korens/devel/MBG-tip/bin/MBG $iopt -t 4 -k 1001 -r 15000 -R 4000 -w 100 --kmer-abundance 1 --unitig-abundance 2 --error-masking=collapse-msat --output-sequence-paths paths.gaf --hpc-variant-onecopy-coverage 25 --do-unsafe-guesswork-resolutions --out hifi-resolved.gfa

All the data is in the globus share under tomato_crash

skoren commented 1 year ago

I believe this has been resolved by the updates.