-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
FacetGrid.map_dataframe
passes disallowed keyword arguments to pointplot
#3004
Comments
I tried modifying the code to move the ...
g = sns.FacetGrid(df_fs, row="metric", col="learner_name", height=2.5,
aspect=1, margin_titles=True, despine=True, sharex=False,
sharey=False, legend_out=False, palette="Set1")
g = g.map_dataframe(sns.pointplot, x="training_set_size", y="value",
hue="variable", scale=.5, errorbar=None)
... While this code does work, it does not produce accurate results. Here's the plot with the above code with v0.12.0: For comparison, here's the plot as produced by the original code with v0.11.2: |
I figured out how to make this work by following the recommendations that:
Here's the new code: ...
df_fs["variable"] = df_fs["variable"].astype("category")
g = sns.FacetGrid(df_fs, row="metric", col="learner_name",
height=2.5, aspect=1, margin_titles=True,
despine=True, sharex=False,
sharey=False, legend_out=False)
g = g.map_dataframe(sns.pointplot, x="training_set_size",
y="value", hue="variable", scale=.5,
errorbar=None,
palette={"train_score_mean": train_color,
"test_score_mean": test_color})
... This code now produces the same (correct) plot as with v0.11.2. |
We should unbreak this, even if it's discouraged usage. Glad you were able to work out the right thing to do here, but I am a little curious why you didn't opt for |
Indeed, |
Do you have an example? Catplot should basically just be generating the code in your third post. |
Sure! Attached are two plots that are saved in 300 DPI using |
Thanks but I’d need to see the actual code to make sense of the example. |
Ah, sorry. Please take a look at the |
Apologies, that branch was probably merged by the time you got to it. It's now in the main branch. |
I don't see any use of |
Yeah, as I mentioned, I didn't use Here's a gist that shows how I combined the However, I am extremely embarrassed to say that it now works fine 😬! Looking back on it, probably because when I did the test originally, I forgot to include the Apologies for wasting your time on this secondary issue. |
Unbreaks FacetGrid + pointplot (fixes #3004) and is generally useful.
* Add label parameter to pointplot Unbreaks FacetGrid + pointplot (fixes #3004) and is generally useful. * Update default kws in pointplot tests * Update release notes
My code that used to work perfectly fine with 0.11.0 breaks with the new 0.12.0 release. The code creates a FacetGrid and then applies
pointplot()
to each of the cells as follows:The relevant traceback is as follows:
Looking at the code for
FaceGrid.map_dataframe
, it does indeed create alabel
keyword argument which, I guess, causes the failure whenpointplot()
is called. From reading the release notes, it looks like this is because of this itemThat keyword argument is created if
hue
is specified which I am not sure how to get around since I have multiple variables that I want to represent with different colors. If there's another way to achieve this, I'd really appreciate any guidance.The text was updated successfully, but these errors were encountered: