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

broken correspondence between method labels on the x-axis and the actual values used #5

Open
sergeyplis opened this issue Apr 7, 2015 · 5 comments

Comments

@sergeyplis
Copy link
Owner

In experiments with the latest polyssifier we've noticed that the mean accuracy values saved in files are different from the bar heights in the generated figure. After looking through the code I conclude that the values in the filenames are correct. It remains unclear why the labels get reordered.
Looks like a bug to me, either in polyssifier or seaborn/polyssifier connection

@rdevon
Copy link
Collaborator

rdevon commented Apr 7, 2015

Are the labels reordered or just incorrect? Can you provide some instructions to reproduce? Thanks

sergeyplis added a commit that referenced this issue Apr 7, 2015
@alvarouc
Copy link
Contributor

alvarouc commented Jun 5, 2015

I get the same error. You can observe this by reading the saved results and those in the plot. They are different.
I will also look into this but for now only trust the saved results.

@sergeyplis
Copy link
Owner Author

I thought we've fixed it. You're using the latest version, right? And your
seaborn is 0.6 and above?
On Jun 5, 2015 3:49 PM, "Alvaro Ulloa" [email protected] wrote:

I get the same error. You can observe this by reading the saved results
and those in the plot. They are different.
I will also look into this but for now only trust the saved results.


Reply to this email directly or view it on GitHub
#5 (comment).

@alvarouc
Copy link
Contributor

alvarouc commented Jun 6, 2015

How do I get seaborn 0.6? Is it the one at github?
the latest I see on the webpage is 0.5.1

@alvarouc
Copy link
Contributor

alvarouc commented Jun 6, 2015

You were right, installing the dev version of seaborn solves the problem. So it is a seaborn bug.

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

No branches or pull requests

3 participants