Open ghost opened 9 years ago
Thanks to an earlier issue here, I've come to realize that the problem is likely not multiple chromosomes, but rather the fact that the chromos are scattered all over the file.
ack -oh "hg38.chr[0-9]*" data/hg38.7way.maf | uniq
results in output like
...
hg38.chr9
hg38.chr17
hg38.chr1
hg38.chr17
hg38.chr11
hg38.chr17
hg38.chr
hg38.chr11
hg38.chr1
hg38.chr4
hg38.chr11
hg38.chr17
hg38.chr15
...
The new MAF-files are not split on chromosomes, so when I try to look up i.e. hg38.chr1 I get the message
/usr/local/lib/ruby/gems/2.1.0/gems/bio-maf-1.0.1/lib/bio/maf/index.rb:266:in
chrom_index': No index available for chromosome hg38.chr1! (RuntimeError)`However, if I try to look up hg38.chr8 it works, presumably because that is the very first chromosome in the maf-file.
This happens to all other MAF-parsers too, so if you update yours you will have the only one that actually works.