Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Finding correct window size for the motif discovery #791

adityabhandwalkar started this conversation in General
Discussion options

Hello @seanlaw ,

I was going through your tutorial for the SKIMP In that tutorial the max_m = 1000 , my question is how did you reach to that value of 1000 when you do not known about maximum length of a subsequence/ window. In my case I have 60k data points only with the sampling rate how can i determine the max_m and min_m is there any alternative to determine this

thanks

You must be logged in to vote

Replies: 2 comments 9 replies

Comment options

@adityabhandwalkar Unfortunately, there is no secret to choosing max_m. Ultimately, you should set max_m to something like 2x the maximum time that you believe an event is likely to take within your domain (nobody can know this but you). Usually, with time series, you might set max_m to an hour, week, month, or year (depending on your data). When you really have no idea then you basically have to set max_m to the length of your time series. Again, there is no magic here and SKIMP is only a tool that may or may not help.

You must be logged in to vote
9 replies
Comment options

@rajivsam I created an issue here and it looks like they actually have notebook with some code!

Comment options

@rajivsam Thank you for sharing this! I wasn't aware that this work was published (by the same authors as the matrix profile) and it seems reasonable. Would you have any time to create a Python implementation that reproduces ones of the listed examples?

@seanlaw , thanks for the template, I was able to recreate the results in the paper. I did the evaluation for two random datasets, the google colab notebook is here:
colab notebook
The template was an excellent start, just needed a little bit of work to reconcile the sketch with section 4 of the paper.

Comment options

Perfect! This is super helpful @rajivsam. Would you be interested in submitting a PR for the issue (of creating a standalone notebook reproducer, which you've basically done)? You've already done a lot so there is absolutely no pressure to, especially if you are busy. We are always looking for new contributors but I can also take it from here if you are not able to.

Comment options

@seanlaw , thanks, if it is just adding this notebook to a known location(forking the repository and adding the notebook, submitting the PR), I am happy to do it. If there is running a bunch of regression tests, then I think its best if someone familiar with the process does it.

Comment options

No, problem. We can handle it. Thanks @rajivsam

Comment options

Cool, thanks.
...
On Fri, Jan 17, 2025 at 11:06 AM Sean M. Law ***@***.***> wrote: @rajivsam <https://github.com/rajivsam> I created an issue here <#1062> and it looks like they actually have notebook with some code! — Reply to this email directly, view it on GitHub <#791 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6PPLJB7IQMEV4ALIVZWTT2LCJFLAVCNFSM6AAAAABVK4EDDWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBWGI3DIOA> . You are receiving this because you were mentioned.Message ID: ***@***.***>
You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /