You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quite commonly there will be branches from phylotree that are just out of frame and fall alongside the x or y axis. This obscures the axis labels and generally looks messy.
This has been a minor issue since the beginning when zooming the tree with situations like:
All the branch lines obscure my reading of the y axis and I can't see that the lower set of red tips have a value of 0 for logistic growth rate.
Description
I'd like plotting here to work like most plotting libraries where "ink" outside of the axes frame is hidden. Ie I'd like white in the dashed boxes with axes on top:
Possible solution
I'd assume that this could be accomplished either by:
Doing something like SVG <clipPath> to clip out things out of frame
Simply drawing a white background behind the axes elements
I'd assume that (2) would be the easier strategy.
The text was updated successfully, but these errors were encountered:
Context
Quite commonly there will be branches from phylotree that are just out of frame and fall alongside the x or y axis. This obscures the axis labels and generally looks messy.
This has been a minor issue since the beginning when zooming the tree with situations like:
However, scatterplot view really exposes this issue further. See for example this view from
https://dev.nextstrain.org/staging/ncov/global-with-dfreq?f_clade_membership=20J/501Y.V3&l=scatter&label=clade:20J/501Y.V3&scatterY=logistic_growth
All the branch lines obscure my reading of the y axis and I can't see that the lower set of red tips have a value of 0 for logistic growth rate.
Description
I'd like plotting here to work like most plotting libraries where "ink" outside of the axes frame is hidden. Ie I'd like white in the dashed boxes with axes on top:
Possible solution
I'd assume that this could be accomplished either by:
<clipPath>
to clip out things out of frameI'd assume that (2) would be the easier strategy.
The text was updated successfully, but these errors were encountered: