[DOC] Update Partitional clustering notebook

[Akhil-Jasson]

I have addressed issue #1805 by updating the partitional_clustering notebook to include all the supported distance metrics.

Reference Issues/PRs

What does this implement/fix? Explain your changes.

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.

[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{#45FD64}{\textsf{examples}}$ ]. 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

[Akhil-Jasson]

Hi @MatthewMiddlehurst @TonyBagnall,
I hope you're doing well! I’ve submitted a PR and would appreciate it if you could take a look at it whenever you have the time. Please let me know if there are any changes or improvements needed.

Thanks in advance for your feedback!

[review-notebook-app]

View / edit / reply to this conversation on ReviewNB

TonyBagnall commented on 2025-01-14T08:56:08Z
----------------------------------------------------------------

not sure if it is just reviewnb, but Squared and ADTW seem to be on the same line

[TonyBagnall]

thanks, could you just check the line break for ADTW?

[Akhil-Jasson]

Hi @TonyBagnall , I’ve double-checked the code and JSON structure, and everything seems fine. Here’s the relevant snippet for reference:

"<ul>\n",
" <li>K-means, K-medoids supported distances:\n",
" <ul>\n",
" <li>Euclidean - parameter string 'euclidean'</li>\n",
" <li>Manhattan - parameter string 'manhattan'</li>\n",
" <li>Minkowski - parameter string 'minkowski'</li>\n",
" <li>Soft DTW - parameter string 'soft_dtw'</li>\n",
" <li>Shift Scale - parameter string 'shift_scale'</li>\n",
" <li>Squared - parameter string 'squared'</li>\n",
" <li>ADTW - parameter string 'adtw'</li>\n",
" <li>DTW - parameter string 'dtw'</li>\n",
" <li>DDTW - parameter string 'ddtw'</li>\n",
" <li>WDTW - parameter string 'wdtw'</li>\n",
" <li>WDDTW - parameter string 'wddtw'</li>\n",
" <li>LCSS - parameter string 'lcss'</li>\n",
" <li>ERP - parameter string 'erp'</li>\n",
" <li>EDR - parameter string 'edr'</li>\n",
" <li>MSM - parameter string 'msm'</li>\n",
" <li>TWE - parameter string 'twe'</li>\n",
" <li>SBD - parameter string 'sbd'</li>\n",
" </ul>\n",
" </li>\n",
"</ul>\n"

The line break for ADTW looks correct here, but I noticed that in ReviewNB, there are formatting issues where some items appear on the same line as others. I’m not sure why this discrepancy is happening, as the code itself appears fine. Please let me know if you think there’s another aspect I should check!