Closed nathanhaigh closed 5 years ago
If you are using prepare-refseqs with indexed fasta I might have found a bug fix for this https://github.com/GMOD/jbrowse/commit/475f1f55ed6f477ec2ce40d63807e23c02d72445
@cmdcolin that commit will fix the issue i.e. end coordinate was being output as a string in the refSeqs.json
file instead of an numerical. I've manually modified my refSeqs.json
file to unquote the end
value.
It is possible to scroll beyond the end of a chromosome. The end coord stays the same as the chrom end coord, but the start coord ends up being larger than the end of the chrom and the range displayed goes into negative territory.