Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use left-stitched instead of patched columns for target clusters #139

Merged
merged 6 commits into from
Aug 2, 2024

Conversation

yoid2000
Copy link
Contributor

@yoid2000 yoid2000 commented Jul 22, 2024

Closes #138

The idea here is to retain any (small) correlation between non-feature columns and the target column.

By left-stitching, in doing so we don't compromise the relationship between the target columns and the feature columns.

@yoid2000 yoid2000 requested a review from edongashi July 22, 2024 12:44
@yoid2000 yoid2000 self-assigned this Jul 22, 2024
@yoid2000
Copy link
Contributor Author

@edon if you time to look at this it would be great. If not that is fine too. Very small changes (all you need to care about is solver.py and test_solver.py. The rest is cleaning up a file I didn't mean to get pushed, my_debugger.py.)

@yoid2000 yoid2000 merged commit 9258648 into main Aug 2, 2024
4 checks passed
@yoid2000 yoid2000 deleted the left-stitch-instead-of-patch branch August 2, 2024 13:47
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.

Do stitching instead of patching for targeted clusters
1 participant