Skip to content
This repository has been archived by the owner on Nov 13, 2021. It is now read-only.

Poor performance: speed and accuracy #25

Open
IkerMesa opened this issue Nov 23, 2016 · 0 comments
Open

Poor performance: speed and accuracy #25

IkerMesa opened this issue Nov 23, 2016 · 0 comments

Comments

@IkerMesa
Copy link

IkerMesa commented Nov 23, 2016

Hi,

I have tried the code and maybe I'm doing something wrong but the performance is not very good in my case. I have tried it with a signal of 118.796 points that has very clear ramps. The result is not very accurate and in addition the program requires more than 2 hours to obtain the result.

On the other hand, I have tried the same data with Matlab 2016b (function findchangepts( ) ) and the result is obtained in less than 1 second, with much better accuracy.

Attached there are:

  • the signal: MyData.csv
  • the result of BreakoutDetection
  • the result of Matlab

Code R:

mydata = read.table("MyData.csv", header=FALSE)
x = unlist(mydata)
myRes = breakout(x, min.size=66, method='multi', beta=0.001, degree=1, plot=FALSE)

Code Matlab:

x = load('MyData.csv');
[ipt,residual] =findchangepts(x, 'Statistic','linear','MinDistance', 66,'MinThreshold',100);

MyData.zip

twitterbreakoutresult

matlabresult

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant