Downsample performance profiles #17
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The AppVeyor failure seems to be related to a problem in Plots? |
|
It's the pesky JuliaPlots/Plots.jl#968. Thanks for this! I'll have a close look asap. |
|
I've merged this manually, thanks for the contribution, and sorry for the delay. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables a simple downsampling of data points along the x-axis for performance profiles. This also gets rid of the first vertical line at
x=1, which goes fromy=1/nptoperf_prof(1)I have run performance profiles on 18 000 problems, with six solvers. So the number of data points plotted gets extraordinarily large, and in particular impractical when plotting to PGF.
I don't know whether this is useful for anybody else, but putting up a PR just in case.