-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Let some kwargs vary with k_ideal in WilkinsonTicks #2892
base: master
Are you sure you want to change the base?
Conversation
Specifically, `k_min = k_ideal - 4`, `k_max = k_ideal + 4`. Users can still override this as necessary.
With -4 you could go to 1, 0, or even negative, all of which are bad. Maybe a better heuristic would be +- 30% or so, with an absolute minimum of 2 because only then can you even tell what the limits are. So |
Co-authored-by: Julius Krumbiegel < julius.krumbiegel@gmail.com>
Compile Times benchmarkNote, that these numbers may fluctuate on the CI servers, so take them with a grain of salt. All benchmark results are based on the mean time and negative percent mean faster than the base branch. Note, that GLMakie + WGLMakie run on an emulated GPU, so the runtime benchmark is much slower. Results are from running: using_time = @ctime using Backend
# Compile time
create_time = @ctime fig = scatter(1:4; color=1:4, colormap=:turbo, markersize=20, visible=true)
display_time = @ctime Makie.colorbuffer(display(fig))
# Runtime
create_time = @benchmark fig = scatter(1:4; color=1:4, colormap=:turbo, markersize=20, visible=true)
display_time = @benchmark Makie.colorbuffer(display(fig))
|
Thanks! |
@jkrumbiegel can we make this mergeable? I think it would be nice to have it easier to construct the WilkinsonTicks |
Description
Specifically,
k_min = min(2, round(Int, k_ideal * .7))
,k_max = min(2, round(Int, k_ideal * 1.3))
. Users can still override this as necessary.Type of change
Arguably a bug fix in the UX for WilkinsonTicks.
Checklist
cc @Datseris