Open mrvollger opened 1 year ago
Thanks for reporting the issue, it seems this is a bug related to the mapped IO interface. The reason why d4tools view
doesn't have this issue is because d4tools view
uses the streamed IO. I've committed a potential fix to the repo, please let me know if the latest commit solved your issue.
Thanks! Hao
Hi @38 and @arq5x,
I am getting an error when trying to open a d4 matrix in pyd4:
I have tried remaking the input file a few times but I keep getting this error. Interestingly if I use the command line tool d4tools I get no error accessing the same region. I have also used the python code successfully on three other samples but it is failing here, so I am at a bit of a loss.
I include details and inputs below, thanks in advance!
Details: Here is a full traceback of the error
But when I access the same region with
d4tools
it works fine:Here is a link to the file: https://eichlerlab.gs.washington.edu/help/mvollger/tracks/fiberseq/fdr.coverages.d4 and here is the python code I have that gives the error: