[ENH] Included RSAST as a alternative to SAST

[nirojasva]

What does this implement/fix? Explain your changes.

I included a transformer RSAST and a classifier RSASTClassifier which are tools to use in time series classification. The method RSAST is based on shapelets in order to transform dataset of Time Series.

Does your contribution introduce a new dependency? If yes, which one?

Yes, I used f_oneway, DegenerateDataWarning, ConstantInputWarning from the "scipy.stats" toolkit. Also, acf and pacf from the "statsmodels.tsa.stattools" implementation.

PR checklist

For all contributions

• I've added myself to the list of contributors. Alternatively, you can use the @all-contributors bot to do this for you.
• The PR title starts with either [ENH], [MNT], [DOC], [BUG], [REF], [DEP] or [GOV] indicating whether the PR topic is related to enhancement, maintenance, documentation, bugs, refactoring, deprecation or governance.

For new estimators and functions

• I've added the estimator to the online API documentation.
• (OPTIONAL) I've added myself as a __maintainer__ at the top of relevant files and want to be contacted regarding its maintenance. Unmaintained files may be removed. This is for the full file, and you should not add yourself if you are just making minor changes or do not want to help maintain its contents.

For developers with write access

• (OPTIONAL) I've updated aeon's CODEOWNERS to receive notifications about future changes to these files.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[aeon-actions-bot]

Thank you for contributing to aeon

I did not find any labels to add based on the title. Please add the [ENH], [MNT], [BUG], [DOC], [REF], [DEP] and/or [GOV] tags to your pull requests titles. For now you can add the labels manually.
I have added the following labels to this PR based on the changes made: [ $\color{#BCAE15}{\textsf{classification}}$, $\color{#45FD64}{\textsf{examples}}$, $\color{#41A8F6}{\textsf{transformations}}$ ]. Feel free to change these if they do not properly represent the PR.

The Checks tab will show the status of our automated tests. You can click on individual test runs in the tab or "Details" in the panel below to see more information if there is a failure.

If our pre-commit code quality check fails, any trivial fixes will automatically be pushed to your PR unless it is a draft.

Don't hesitate to ask questions on the aeon Slack channel if you have any.

[nirojasva]

Hi, I'm new to using forks on github. I already changed the init.py file, including a "LearningShapeletClassifier" classifier that I thought was causing conflicts with the code I'm trying to merge. However, I have not been able to complete the PR. What else should I check to correctly modify the code? Thanks for the help.

[MatthewMiddlehurst]

Hi @nirojasva, you will want to pull from the main branch main repository remote aeon-toolkit/aeon, then resolve any conflicts.

How different is this from the original SAST, can it be integrated into that implementation instead? I think @TonyBagnall reviewed the original?

[nirojasva]

Hi @MatthewMiddlehurst,

Yes, it is a little bit different since in SAST every subsequence in time series is extracted for the transformation of dataset and in RSAST just some randomly selected shapelet are used to do the transformation.

I have about the validation, if I make push from my local aeon github project it will automaticlly recalcalculate the conflicts?

Thanks,

[MatthewMiddlehurst]

It sounds like this could be in the same classifier as the regular SAST as a parameter (like the ROCKET variants). If the transformer can't be in the same class, it could be in the same file to keep it more organised.

I have about the validation, if I make push from my local aeon github project it will automaticlly recalcalculate the conflicts?

No, you will have to pull the main branch first. After merging there, you can then push the merged commits to your branch and it will update here.

[nirojasva]

It seems now is merged, thanks.

[MatthewMiddlehurst]

For this branch it looks like you overwrote the contents with main rather then merging. You may have to create a new PR, or maybe adding new changes will reopen.

[nirojasva]

I tried to create another PR: [ENH] Included RSAST as a alternative to SAST (2.0) #1383