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
Hi,
I came across a very strange bug. It seems that starting with v2.29 -f does not function properly anymore if used in conjunction with option -split.
read-file
cat b.bed
X 10 30 A2 1 + 0 30 255,0,0 1 20 0
cat x.bed
X 0 20 B1 0 +
cat y.bed
X 0 20 B1 0 +
X 0 20 B2 0 +
cat z.bed
X 0 20 B1 0 +
X 0 20 B2 0 +
X 0 20 B1 0 +
One difference I observed is the extent of overlap printed in the last column. it seems v2.29 sums this one up for all the regions in b a read in a is overlapping. If I create an example where one read can overlap the regions in y.bed then I get this:
There was a bug in -f -split fixed in 2.29, but the fix may have introduced another issue. I will be able to dig into this in a few days. Thanks for reporting.
Hi,
I came across a very strange bug. It seems that starting with v2.29 -f does not function properly anymore if used in conjunction with option -split.
read-file
v.2.28
v.2.29
One difference I observed is the extent of overlap printed in the last column. it seems v2.29 sums this one up for all the regions in b a read in a is overlapping. If I create an example where one read can overlap the regions in y.bed then I get this:
You can see that for both reads the overlaps are summed up in v2.29 but not in v2.28.
This behavior only occurs if -split is selected.
Hope this helps.
The text was updated successfully, but these errors were encountered: