[Question] MGC redundant row warning
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 252
- Forks
- 96
- PR merge metrics
- No merged PRs in 30d
Description
When I run KSample.test() using MGC, I get this warning. Is there any hint on what this implies (Edit: I just saw https://github.com/neurodata/hyppo/issues/125. Still a more informative warning would be much appreciated)? I.e. is it something serious such as an indication that some assumption on which the algorithm is based is violated? Also: Isn't y constructed in a way, that will always trigger that warning?
Thanks for your time!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the warning at hyppo/independence/mgc.py line 232 and the context of KSample.test(). Review issue #125 for the existing explanation and determine whether the way y is constructed commonly triggers the warning. Done means the warning or accompanying documentation clearly explains its implication and expected conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100