Skip to content

DOC: clarify that min neighbors for clusters is 0 in permutation_clus…#13774

Open
athishdresu wants to merge 10 commits intomne-tools:mainfrom
athishdresu:main
Open

DOC: clarify that min neighbors for clusters is 0 in permutation_clus…#13774
athishdresu wants to merge 10 commits intomne-tools:mainfrom
athishdresu:main

Conversation

@athishdresu
Copy link
Copy Markdown

Hi! I am Athish M, a GSoC 2026 applicant for Project 4. I've added a note to permutation_cluster_test to clarify that the minimum number of neighbors defaults to 0, which addresses the confusion mentioned in Issue #13008. This is my first contribution to the project

@welcome
Copy link
Copy Markdown

welcome bot commented Mar 21, 2026

Hello! 👋 Thanks for opening your first pull request here! ❤️ We will try to get back to you soon. 🚴

Copy link
Copy Markdown
Member

@larsoner larsoner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will also need a doc/changes/dev/13774.other.rst with the :newcontrib: role to mention the doc improvement

return orders, n_permutations, extra


def _permutation_cluster_test(
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is in a private function so end-users will not see it. It would be better to add a note to one of the public functions

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @larsoner, I've moved the note to the public functions permutation_cluster_test and spatio_temporal_cluster_test. I also added the changelog entry in doc/changes/dev/13774.other.rst
Ready for another look! Thanks for the guidance

@athishdresu
Copy link
Copy Markdown
Author

Hi @larsoner, I've completed the updates you suggested - I moved the note to the public functions and added the changelog entry in doc/changes/dev/13774.other.rst. I also officially submitted my GSoC proposal today! Whenever you have a moment, could you please approve the CI workflows to run so we can verify the tests? Thank you for all the guidance so far!

Comment on lines +1246 to +1249
Note: By default, the minimum number of neighboring
points (e.g., channels) required to form a cluster is 0.
This means a single significant point can
technically constitute a cluster.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this note is in the References section. There's a "Notes" section right above.

Comment on lines +1550 to +1553
Note: By default, the minimum number of neighboring
points (e.g., channels) required to form a cluster is 0.
This means a single significant point can
technically constitute a cluster.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't put notes in References section.

@drammock
Copy link
Copy Markdown
Member

@athishdresu: heads up that there's usually no need to merge main into your PR even if GitHub says "this branch is out-of-date with the base branch". It re-triggers all the CIs (some of which we pay for!) which usually we don't want/need to do. It's only necessary if the CIs are failing AND we know that the failure is unrelated to this PR AND there's a fix for it already merged into main. In that case, it's appropriate to merge in main to get CIs to pass.

@athishdresu
Copy link
Copy Markdown
Author

I've moved the note to the Notes section for both functions as requested. Thank you for catching that, @drammock!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants