|
|
|
@ -9,10 +9,13 @@ return overlapping motifs.
|
|
|
|
I remember reading that the distances returned by a matrix profile have an upper
|
|
|
|
I remember reading that the distances returned by a matrix profile have an upper
|
|
|
|
bound. I should see what calculating my distance cutoff with that upper bound
|
|
|
|
bound. I should see what calculating my distance cutoff with that upper bound
|
|
|
|
looks like rather than calculating off the top motif like I do now.
|
|
|
|
looks like rather than calculating off the top motif like I do now.
|
|
|
|
|
|
|
|
|
|
|
|
If two motifs overlap it could be that the window is too small. I don't know what
|
|
|
|
If two motifs overlap it could be that the window is too small. I don't know what
|
|
|
|
other criteria to test yet to tell me if that is the case or not. I do know that
|
|
|
|
other criteria to test yet to tell me if that is the case or not. I do know that
|
|
|
|
this can be determined in discovery stages using a Pan-matrix profile (PMP).
|
|
|
|
this can be determined in discovery stages using a Pan-matrix profile (PMP).
|
|
|
|
|
|
|
|
|
|
|
|
Some form of reference following should occur to ensure that I'm grabbing motifs
|
|
|
|
Some form of reference following should occur to ensure that I'm grabbing motifs
|
|
|
|
which actually relate to one another.
|
|
|
|
which actually relate to one another.
|
|
|
|
|
|
|
|
|
|
|
|
Currently the function is quite primitive. It should be packaged and iterated on
|
|
|
|
Currently the function is quite primitive. It should be packaged and iterated on
|
|
|
|
using the data in further sections of the tutorial.
|
|
|
|
using the data in further sections of the tutorial.
|