Hi,
I have been trying to use regionFinder to find statistic bumps in large genomic data sets, but I have noticed that the output doesn't make sense. Here is an example:
The first couple lines of the output look like this:
chr start end value area cluster indexStart indexEnd L
3 chr12 2224708 2225580 5.416306 59.579368 3 1 18 18
6 chr12 2279596 2279661 5.432257 10.864514 6 5 10 6
clusterL
3 11
6 2
Those numbers don't make sense though, L should not be longer than clusterL, and if you look at what's actually contained in the first range, it's only 9 sites, not 18. I have noticed that the issue goes away if I manually order my data, but because the default for assumeSorted = FALSE it seems that I shouldn't have to. My data comes from multiple locations so it is a pain to have to pull it all together to order, rather than just being able to pull the relevant vectors. My version in use is bumphunter_1.28.0.
Hi, I have been trying to use regionFinder to find statistic bumps in large genomic data sets, but I have noticed that the output doesn't make sense. Here is an example:
The first couple lines of the output look like this:
Those numbers don't make sense though, L should not be longer than clusterL, and if you look at what's actually contained in the first range, it's only 9 sites, not 18. I have noticed that the issue goes away if I manually order my data, but because the default for
assumeSorted = FALSE
it seems that I shouldn't have to. My data comes from multiple locations so it is a pain to have to pull it all together to order, rather than just being able to pull the relevant vectors. My version in use isbumphunter_1.28.0
.