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
BUG: Fix problem with --color_by #306
Conversation
When nothing was passed in to --color_by, the default behaviour was to keep all the columns in the mapping file. This was inconsistent with the documented behavior, to remove unique columns, which has now been corrected. See the comments in this patch. Fixes biocore#271
The test build for this pull request can be found here: http://emperor.colorado.edu/pull_306/make_emperor/ |
Using the mice tutorial --add_unique_columns doesn't work as expected, it |
Conflicts: ChangeLog.md
Thanks for catching that, I'm working on this right now. |
If we requested the unique columns to be kept, then only the SampleID would be retained, which was in turn useless. This has been fixed.
Should be fixed ... waiting for the tests to pass. |
Now using or not --add_unique_columns gives the same output. |
If you didn't pass anything with -b you would get all the categories, whilst if you passed --add_unique_columns you would get only SampleID. This has been fixed for good. 🐛
This time it should be fixed for good. |
Finally!!! |
BUG: Fix problem with --color_by
Thanks for reviewing @antgonza. On (Sep-24-14| 7:48), Antonio Gonzalez wrote:
|
When a category was passed in with the --color_by flag and the values in the
mapping file were unique, this category was removed; this problem has now been
fixed a new test case was added and a note in the ChangeLog.md was re-added.
See #271