You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For feature files with no header (like a BED file, which may have no header), 0 is a legitimate offset, even if the file is block gzipped and the offset represents a virtual file offset. However, the binning indexer always sets the window for a bin to the lowest feature offset for that bin that is not 0. i.e., BED files can have the first feature at offset 0.
@magicDGS I created this ticket so we could track the BinningIndexBuilder part of the issue separately from the .gz part. So there is some overlap, but not exactly a dup.
For feature files with no header (like a BED file, which may have no header), 0 is a legitimate offset, even if the file is block gzipped and the offset represents a virtual file offset. However, the binning indexer always sets the window for a bin to the lowest feature offset for that bin that is not 0. i.e., BED files can have the first feature at offset 0.
Fixed in #906.
The text was updated successfully, but these errors were encountered: