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
Sorting the ticks and labels separately runs into a lot of issues particularly when node timings are the same (ARGweaver, SLiM). I need to think of a more consistent way of sending this information into JavaScript.
The text was updated successfully, but these errors were encountered:
Relating to tskit-dev/tutorials#264 and particularly when y_axis_scale="time" or y_axis_scale="log_time", I think it's better to just have evenly spaced ticks rather than one per node. This will also solve this bug as it'll be more consistent. Maybe by default have evenly spaced ticks and give users the ability to control either the number of ticks or modify the ticks list directly.
There was often a lot of overlap in tick labels when using `y_axis_scale="time"` or `y_axis_scale="log_time"` as the node timings were so close together. This now limits evenly spaces the tick marks for those scales, while keeping 0 and the max_time. This should avoid the issues mentioned in #8
Sorting the ticks and labels separately runs into a lot of issues particularly when node timings are the same (ARGweaver, SLiM). I need to think of a more consistent way of sending this information into JavaScript.
The text was updated successfully, but these errors were encountered: