-
Notifications
You must be signed in to change notification settings - Fork 68
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
Fixes doubled colors in legend and reduces label count #1895
Conversation
@chaosphere2112 when you add a test could you please reopen this again? |
… rounding to labels
@chaosphere2112 can you resolve the merge conflicts? |
@aashish24 Yeah; there's another bug that I ran into that I'm running down right now. I'll get an update for this by EOD. |
Sure, thanks. |
@aashish24 I ran into a few more issues, I'll clean this up in the morning. |
…abels from being drawn
…n, eliminated "guess_precision"
Here's where this PR stands currently on CDASH. So this is starting to get a little bit out of hand. I've done some major improvements to some of the baselines (test_vcs_boxfill_zero and test_vcs_boxfill_lev1_lev2 are notably better), but then there's... debatable movement on others (test_vcs_boxfill_lev1_lev2_ext1 is a good example of one that isn't bad, but it's certainly not better than it was). I think I fixed a bug in test_vcs_issue_960 (it looks like the last label was missing from the legend, for some reason). How do people feel about less "pretty" numbers for some scales? I can try and be a little smarter about reverting to the old method (vcs.mkscale), but my first attempt at doing so made |
@chaosphere2112 less pretty numbers you meant they are decimans now? I like the new legend but I think it would be great to have an option to clamp to round numbers since those are easy to read but in some cases you may not want that. |
@aashish24 The users still have the ability to use round numbers; if they don't specify |
@aashish24 @doutriaux1 Alright, this is ready. I fixed the off-by-one errors, so now the same output should be generated for the same input, plus improvements (like a missing level, and lining up the last level, and other goodies). |
@aashish24 ping |
thanks @chaosphere2112 will look into it today. |
low_end = numpy.ma.log10(low_end) | ||
high_end = numpy.ma.log10(high_end) | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chaosphere2112 nitpick, do we need this many empty lines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, I'll remove the extra one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @chaosphere2112
LGTM 👍 |
@chaosphere2112 don't forget to delete branch after merging |
@doutriaux1 Sorry, got excited and merged when I was going to bed 😄 |
you mean you actually take time to sleep! 😜 |
Fixes the issues outlined in #1894; still need to add a test.