Clarify sampling logic for small vs large control type groups #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addressed review question about why the proposed code doesn't sample small groups (≤250 samples) when handling control type sampling in UMAP visualization.
Clarification Provided
The sampling logic correctly handles two cases:
Small groups don't need sampling because they're already at or below the target size. Sampling them would be unnecessary computation with no benefit.
Context
The reviewer suggested refactoring to avoid pandas
GroupBy.applydeprecation warnings:This approach is correct and more efficient than the current
apply(lambda grp: grp.sample(n=min(250, len(grp))))implementation.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.