[ENH] Added test cases for feature based clustering

[Ramana-Raja]

Reference Issues/PRs

What does this implement/fix? Explain your changes.

Added test cases for feature based clustering

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

Any other comments?

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 after the PR has been merged.
• 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/function 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.

[aeon-actions-bot]

Thank you for contributing to aeon

I have added the following labels to this PR based on the title: [ $\color{#FEF1BE}{\textsf{enhancement}}$ ].
I have added the following labels to this PR based on the changes made: [ $\color{#4011F3}{\textsf{clustering}}$ ]. 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.

PR CI actions

These checkboxes will add labels to enable/disable CI functionality for this PR. This may not take effect immediately, and a new commit may be required to run the new configuration.

• Run pre-commit checks for all files
• Run mypy typecheck tests
• Run all pytest tests and configurations
• Run all notebook example tests
• Run numba-disabled codecov tests
• Stop automatic pre-commit fixes (always disabled for drafts)
• Disable numba cache loading
• Push an empty commit to re-run CI checks

[MatthewMiddlehurst]

Hi, this does not seem to add much that the general testing does not test. It would be better to add any expected results to the testing/ utilities. Cases which are not covered by the general testing are ususally parameters or other model specific functionality. I would check out coverage report to see if there are any uncovered bits.

[Ramana-Raja]

Hi, this does not seem to add much that the general testing does not test. It would be better to add any expected results to the testing/ utilities. Cases which are not covered by the general testing are ususally parameters or other model specific functionality. I would check out coverage report to see if there are any uncovered bits.

Hi, I added extra test cases and made sure they cover 80%+ of the code (except for cases where an estimator is passed), here’s what the tests check:

1.Whether the ARI scores are correct
2.If the output length matches the input length
3.Both Catch22 and Catch24 are tested(using catch24=False)
4.The summary clusterer with all summary stats
5.The TSFresh clusterer with all fc_parameters.
6.That there are no NaN values in the output(when summary clusterer uses all summary stat and when TSFresh clusterer uses all fc parameters) .

Let me know if this is fine or if I should add more.I will use this as a reference for the other 2 PR if it is

[MatthewMiddlehurst]

Some of these are unnecessarily costly. consider users smaller data.

[Ramana-Raja]

Some of these are unnecessarily costly. consider users smaller data.

I have reduced the dataset size and removed functions/test cases that are already covered by general tests.

The testing covers the following cases:
1.catch22 is being tested with catch24 set to false
2.Testing with all summary stats for both univariate and multivariate cases for the Summary Clusterer
3.Testing with all FC parameters for both univariate and multivariate cases for the TSFresh Clusterer