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

dynamically set map deme radii #280

Open
jameshadfield opened this issue Mar 16, 2017 · 9 comments
Open

dynamically set map deme radii #280

jameshadfield opened this issue Mar 16, 2017 · 9 comments
Labels
proposal Proposals that warrant further discussion

Comments

@jameshadfield
Copy link
Member

would prevent cases such as this:
image

@trvrb
Copy link
Member

trvrb commented Jul 7, 2017

Possibly addressed by changes in #330? We should revisit and see if working as intended.

@jameshadfield jameshadfield added the revisit sometime Useful to address but no bandwidth at the moment label Jul 7, 2017
@jameshadfield jameshadfield added bug Something isn't working high priority proposal Proposals that warrant further discussion and removed revisit sometime Useful to address but no bandwidth at the moment labels Oct 30, 2018
@jameshadfield
Copy link
Member Author

Doing this for all the different use cases seems difficult to do perfectly, but relatively easy to make vast improvements over the current situation (right now it's hardcoded so only works for a small range of tip values).

We could also expose a user selector to tweak this as desired, e.g:
image

@tsibley
Copy link
Member

tsibley commented Oct 30, 2018

What if we define a scaled set of maximum deme radii based on the current map zoom level, assign the largest demes to the zoom level max radii, and scale the rest of the smaller demes based on that?

@jameshadfield
Copy link
Member Author

This would be a relatively easy first step and would probably be a big improvement.

@trvrb
Copy link
Member

trvrb commented Mar 11, 2019

I think that PR #712 + a dynamically set max zoom (to be ~2 levels past initial zoom set by fitBounds) will fully resolve this. Initial sizing all works well, only looks bad when zoomed too far out. I think reasonable to add in a maxZoom and maxBounds to appropriately bound these more narrow datasets.

@jcw349
Copy link

jcw349 commented Oct 22, 2020

Doing this for all the different use cases seems difficult to do perfectly, but relatively easy to make vast improvements over the current situation (right now it's hardcoded so only works for a small range of tip values).

We could also expose a user selector to tweak this as desired, e.g:
image

Are there plans to implement this still? I think it will help visualize local cases. As of now, when we hover our mouse over small demes, the mouse misses the circle and nothing happens.

@trvrb trvrb added low priority and removed high priority bug Something isn't working labels Jan 21, 2021
@trvrb
Copy link
Member

trvrb commented Jan 21, 2021

I'll leave this open, but it hasn't seemed a major issue to me. If others disagree, please chime in.

@emmahodcroft
Copy link
Member

I wouldn't say it's disabling, but it can definitely still be annoying sometimes. For example, on focal S:N501 builds, UK circle just about swallows rest of map. For a figure I made recently, I had to run locally and adjust deme sizes in auspice just to get something semi-reasonable-looking. That's a bit of a special case, but it might be nice if we could allow users to somehow scale how radical the difference between demes are, for cases where difference may be really extreme. However, not urgent.

@trvrb
Copy link
Member

trvrb commented Jan 22, 2021

Thanks Emma. Just bumped to "moderate priority".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Proposals that warrant further discussion
Projects
No open projects
Development

No branches or pull requests

5 participants