Closed Jakob37 closed 3 months ago
Unsure who is / feel the responsibility for d4-tools
at the moment. Could anyone of you @38 @arq5x @brentp look into this, or do you know where to turn? Thanks!
If @38 is around, he's the best to confirm but in the absence of that, I will have a look @Jakob37 thanks very much.
This is awesome, thank you for fixing this @Jakob37. I've been using Tasks
recently and could not figure out why each TaskPartition
was being fed positions outside of its boundaries.
This is awesome, thank you for fixing this @Jakob37. I've been using
Tasks
recently and could not figure out why eachTaskPartition
was being fed positions outside of its boundaries.
Happy to hear 😄 Thanks @brentp for wrapping this up
Hi, I pushed v0.3.10 with these changes. Please let me know if you need anything else.
Thank you, @brentp !
Tentative fix for the issue mentioned in issue #78.
I have also included the fix from #77 such that I could run
cargo build
.It has worked well in my local testing. I have also tested manually recalculating the results using
d4tools show
for the regions and counting in a Python script. It looks like it is doing the right thing in my case (a single non-indexed d4 file).The testing.
My bed-file (
intervals_only_19.bed
)Running the master branch version:
Running the current version:
The pattern is the same for me across multiple d4 files I produced. I didn't see it in the provided test data from this repo.