-
-
Notifications
You must be signed in to change notification settings - Fork 192
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
Fix Clustergram reordering of row and column indices. #458
Conversation
I wonder why |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💃 Once we figure out what is causing that test to fail. Have you done a fresh npm ci/npm run build/pip install -e .
?
@shammamah must have been that, thanks ;) |
@mkcor Please add a CHANGELOG entry and bump the version! I can publish to npm and PyPI. |
Aww what's wrong with file |
You might have to do a full clean ( |
When I clean up first, I get the same postbuild error ( |
I'll try upating |
Oh dear, I went through https://flaviocopes.com/update-npm-dependencies/ but still getting this |
@mkcor Looking into it now! |
@mkcor We don't want to update our npm packages here (that's why I suggested |
Duh, I've been trying to run |
Sure. We need to update Broader question: Why don't we want to update packages? Originally we set up #377 for this purpose. |
That sounds fine.
We don't want to update npm packages (that don't need to be updated) in this PR, since it only modifies one of the Python components. |
Also, doing a clean install/build from This commit looks like it was the culprit: d2faa89 It seems to have changed the versions of a bunch of packages. Please check out the versions of |
d7c5bb0
to
e43023f
Compare
Right, my install/build at d2faa89 must have been messy.
Thanks for looking into it! I have rebased to remove this commit and all subsequent commits. Then:
I updated the date to today's date in the changelog. Then:
Please review the visual change (Percy), thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking care of this! 💃
Closes #432.
About
This is a hot fix for the Clustergram component, which used to shuffle rows and/or columns (depending on whether clustering would be along rows, columns, or both) after they were reordered (as expected) from clustering (based on scipy's hierarchy submodule).
All the action is taking place at commit 611a1b3 (the rest is minor).
I included a unit test (bda8f08) using the example from the bug report (#432).
Description of changes
Before merging