Closed rhalperin closed 2 years ago
Thanks for reporting the issue. Surprised to see this bug considering I've processed many samples with results reported in both the autosome and chrX. May I ask what version you are using? Are your chromosome names prefixed with "chr"?
I am using pavfinder 1.8.1. My chromosome names do not have the "chr" prefix. The following edits to adjacency.py
fixes the issue:
613 if chrom.isdigit():
614 return None, int(chrom)
615 elif chrom=="X":
616 return None, 23
617 elif chrom=="Y":
618 return None,24
619 else:
ok, thanks, I'll give this a try and incorporate your fix if everything's ok
@readmanchiu have you gotten a chance to look at this yet?
Sorry for the late reply, I've introduced some changes to fix the bug. Please download again and run to check if the bug is fixed. Thanks for your test in advance!
Sorry, for the delay - just realized I hadn't replied. Yes this appears fixed. Thanks for your help!
Running the
find_sv_transcriptome.py
script, I am seeing the error below. By adding some print statements, it appears to be trying to compare chromosome 'X/Y' to autosomes.