Closed jamesc99 closed 3 hours ago
Hi @songbowang125
Is there any update regarding this issue?
Thank you!
Hi,
I will make some upgrades tomorrow.
I haven't test any BAM files produced by VACmap before, but I think CIGAR strings are very essential for SV detection. Why not using the commonly used aligners such as minimap2?
thanks
Hi, I have upgraded the codes and you can try the new version v1.9. If any new errors, please let me know.
@songbowang125
Thanks for your update. I have been able to run SVision-pro on VACmap BAMs.
Why not using the commonly used aligners such as minimap2?
VACmap shows better performance in complex variants detection than minimap2. As an example, in our test, SVision-pro can detect 30-60% more complex SVs in VACmap BAMs.
Best
svision-pro_germline_540201_4294967294.txt test_hg002_pacbio_vacmap.zip uniq_cigar_column_hg002_pacbio_vacmap_region_chr1_40000000_50000000.txt
Hi @songbowang125 ,
I am continuously getting same error when runing SVision-pro on VACmap aligned BAM files.
Errors look like:
SVision-pro version I am using: v1.8 It usually starts normally and begins to report errors like above. I have attached the full log file and test data for your debug.
Script for running SVision-pro:
I am assuming the error is raised due to lack of information on CIGAR column required by SVision-pro. I attached the file of CIGAR column of pacbio_vacmap chr1_40000000_50000000, which corresponds to the first error.
Please let me know if there is anything I can do, thanks again for your time!