-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
(feature) Specify layer(s) that ggMarginal uses #144
Comments
Could you please post some usecases/examples of how you see this working? |
I'm making a phase plot using a ribbon annotation to separate areas with qualitatively different outcomes. I want to plot the marginal density of the scatter points, but the data for the annotation ribbon appear to be driving the behavior of the marginal density plots. Load packages, make data:
Perhaps one could add an argument |
This code does work for me. I tried both the CRAN and the latest GitHub versions.
|
Hello, is it possible to add axis to marginal plots created with ggMarginal () ? |
I think you're talking about the same thing as #64 |
Exactly, @daattali. I am a reviewer on a paper and it's a pity that the proportions of the density plots are not display to get, in a quick glance, all the info needed to interpret the figure. On the other hand, I'm building up a figure using a bubble plot (latitude and longitude points) over a map (shapefile). I'm using several geom_line(), geom_path(), geom_polygon() layers in a ggplot2 mode. Then the ggMarginal() takes the info of all latitude and longitud points showed in the figure, including the borders of the shapefiles which are build up based on points with a latitude and longitude values...is there any way to make the ggMarginal() function take the latitude and longitud points of the elements georeferenciated in the map but not those belonging to the borders of the countries? thanks for a great package |
This feature would allow the user to specify which layer of the ggplot is used to make the marginal plots. It would be a more controlled middle ground between the original behavior addressed in issue #67 and the current behavior (using all layers).
The text was updated successfully, but these errors were encountered: