-
Notifications
You must be signed in to change notification settings - Fork 12
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
[DOC] Example (with plots) of using the windowed functionality #70
Comments
perhaps something like this (in the attachement)? it is from a recent manuscript I am working on.
… Am 07.02.2019 um 11:09 schrieb George Datseris ***@***.***>:
I think it will be easy to create an example where a big recurrence matrix is plotted and then "subsections" of it are created using the @windowed functionality. Something very similar with how it is displayed in Norbert's papers, but not as a static image: as a Julia code.
If someone provides an example that using @windowed makes sense (scientifically I mean) I will take care of the plotting part.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#70>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7WkBdBA5gyC7Fqd1GlX9nMbaVh40HFks5vK_t3gaJpZM4am9ht>.
|
Figure caption: Exemplary recurrence plot (D) showing the recurrence structure of |
Yeah this is exactly what I had in mind!!! It would be even better though if we can use something more real that comes from a system we can simulate. this seems to be a "Frankenstein-timeseries" :P |
I think it will be easy to create an example where a big recurrence matrix is plotted and then "subsections" of it are created using the
@windowed
functionality. Something very similar with how it is displayed in Norbert's papers, but not as a static image: as a Julia code.If someone provides an example that using
@windowed
makes sense (scientifically I mean) I will take care of the plotting part.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: