Skip to content

[minor] sizes as area in square points #1099

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

Open
akhmerov opened this issue Aug 17, 2012 · 6 comments
Open

[minor] sizes as area in square points #1099

akhmerov opened this issue Aug 17, 2012 · 6 comments
Labels
API: changes Documentation keep Items to be ignored by the “Stale” Github Action New feature

Comments

@akhmerov
Copy link
Contributor

The docstring for various sizes arguments states that size is given as symbol area in square points. Checking with matplotlib.Collections code, this argument doesn't actually calculate the symbol area, but instead is a squared scale factor. This might lead to a wrong interpretation especially if irregularly-shaped symbols are used, but it also not correct for circles. On a more general basis, is it not easier to use linear scale factor as an argument, instead of its square? I just don't see applications where the latter is more useful than the former.

@efiring
Copy link
Member

efiring commented Aug 17, 2012

I agree. It arose historically from matching Matlab's behavior in scatter(), so the only way to get away from it is to provide an alternative kwarg and encourage its use. I would guess that the original Matlab motivation for using area was the idea that visual size of a blob scales with area, not diameter. For example, if symbol size represents population of a city, it is reasonable to have area of the symbol be proportional to population. From the standpoint of a plotting library, however, I think it is much better to let the user do the squaring when desired, and to use linear dimensions in the plotting command.

@tacaswell tacaswell modified the milestones: v2.0, v1.5.x Nov 26, 2014
@tacaswell tacaswell modified the milestones: unassigned, 2.0 (style change major release) Mar 21, 2016
@efiring
Copy link
Member

efiring commented Mar 21, 2016

If we decide to move forward on this, the solution is likely to be an alternative kwarg that specifies size based on a simple linear metric. There is also the possibility of allowing a norm function, but I think this would be overkill--more complexity than real-world applications can justify.

@github-actions
Copy link

github-actions bot commented Oct 9, 2023

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Oct 9, 2023
@akhmerov
Copy link
Contributor Author

I think this is still a valid issue, and the arguments above apply to the same extent as they did before.

@github-actions github-actions bot removed the status: inactive Marked by the “Stale” Github Action label Oct 13, 2023
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Oct 14, 2024
@jklymak jklymak added keep Items to be ignored by the “Stale” Github Action and removed status: inactive Marked by the “Stale” Github Action labels Oct 14, 2024
@jklymak
Copy link
Member

jklymak commented Oct 14, 2024

Put the keep label on, it necessarily because I think we should do anything about this, but it is definitely still the behaviour

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API: changes Documentation keep Items to be ignored by the “Stale” Github Action New feature
Projects
None yet
Development

No branches or pull requests

5 participants