-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
binseg returns incorrect segment means #47
Comments
Due to other fixes, the last statement errors now. For the first two there was a bug which added an extra 0 to the start of the changepoint list which is why all of them start with 1. For the first example it should just be a mean of 2.33333 as there is 1 segment so I will need to look further into this bug after the current release (2.2.3) as it only seems to happen with small datasets. |
Hi @rkillick thanks for the update. I confirm an error for the third now, but the first two issues persist.
|
I haven't committed the version to github yet! |
Is this R package under active development and maintenance? Can the package author please upddate old issues and bring them to a logical end? Alternatively if the package author recommends there is another package that has superceded this package, it will be nice we know that. Thanks. |
Yes this package is under active development and maintenance. As you can imagine, when someone is an academic and covid hits then other tasks need to take priority. This is unfortunately what happens when packages are maintained by volunteers and not paid staff. If you would like to submit a patch fix we would be happy to accept the pull request for others to benefit. |
hi @rkillick I'm trying to get the segment means computed by binary segmentation, which appear to be incorrect below.
The text was updated successfully, but these errors were encountered: