Closed sooheelee closed 4 years ago
This came up again recently. It looks like HTSJDK discovers the crai
index correctly when it's in a bucket, but throws that information away in SamReaderFactory.open()
when it calls indexMaybe.asFile()
, which returns null
Might actually be a simple fix in HTSJDK...
That would be great...
Fix is a few lines of code in the increasingly abominable SamReaderFactory. PR is https://github.com/samtools/htsjdk/pull/1125.
This has been fixed for quite a while. Its the test PR that was controversial.
For a PrintReads command that requires accessing the index, e.g. when specifying
-L
intervals, running locally works but running ongs://
CRAM fails even if index is explicitly specified.Local run (server)
A command that accesses a local CRAM runs fine.
Cloud CRAM
Running just PrintReads without
-L
intervals succeeds.Adding in
-L
causes the command to error despite the presence of the index within the same folder.Still fails with
-readIndex
specified (.cram.crai OR .crai):Confirm all files present in bucket