-
Notifications
You must be signed in to change notification settings - Fork 30
Deprecate use of cluster, metacluster, and mc_name outside of remapping #950
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
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
The example dataset version will be changed to main just before merging in. |
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.
LGTM!
Same, adding the |
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.
Looks good! As long as you made sure both notebooks run without any issues should be good to go.
What is the purpose of this PR?
Closes #846. It's much easier for the user to read
pixel_som_cluster
as opposed tocluster
,pixel_meta_cluster
as opposed tometacluster
, andpixel_meta_cluster_rename
as opposed tomc_name
. We had used these as a result of standards Zak used, but these names should be reverted outside of the remapping process.How did you implement your changes
Any function outside of
metacluster_remap_gui
needs to use the new standard of column naming. When the mapping is saved after a click event ofNew metacluster
happens, the columns get renamed prior to the save.