Skip to content
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

Overlay blend mode #4700

Closed
njsmith opened this issue Jul 15, 2015 · 5 comments
Closed

Overlay blend mode #4700

njsmith opened this issue Jul 15, 2015 · 5 comments
Assignees
Milestone

Comments

@njsmith
Copy link

njsmith commented Jul 15, 2015

No time to put together a PR just now (I need to check out of this hotel!) but while skimming colors.py I just noticed:

        blend_mode : {'hsv', 'overlay', 'soft'} or callable, optional
            The type of blending used to combine the colormapped data values
            with the illumination intensity.  For backwards compatibility, this
            defaults to "hsv". Note that for most topographic surfaces,
            "overlay" or "soft" appear more visually realistic. If a

Sounds like a good candidate for a 2.0 change to me. AFAIK the HSV space is never the best option for pretty much anything :-).

@WeatherGod
Copy link
Member

We would need to make that controlable via rcparams for 1.5.

On Wed, Jul 15, 2015 at 11:59 AM, Nathaniel J. Smith <
notifications@github.com> wrote:

No time to put together a PR just now (I need to check out of this hotel!)
but while skimming colors.py I just noticed:

    blend_mode : {'hsv', 'overlay', 'soft'} or callable, optional
        The type of blending used to combine the colormapped data values
        with the illumination intensity.  For backwards compatibility, this
        defaults to "hsv". Note that for most topographic surfaces,
        "overlay" or "soft" appear more visually realistic. If a

Sounds like a good candidate for a 2.0 change to me. AFAIK the HSV space
is never the best option for pretty much anything :-).


Reply to this email directly or view it on GitHub
#4700.

@tacaswell tacaswell added this to the Color overhaul milestone Jul 15, 2015
@jenshnielsen
Copy link
Member

The new overlay modes were AFAIK introduced by @joferkington but are yet not in a release. Usually we wait a bit before chancing the default. It we change this we should make it an rcparam for 1.5 and add a warning that the default will change.

@WeatherGod
Copy link
Member

We don't even really need a warning. It would be a part of the 2.0 style
changes. We just need to make sure we get the rcparam in for 1.5 so that
there is no new code for 2.0, just config changes.

On Wed, Jul 15, 2015 at 7:15 PM, Jens Hedegaard Nielsen <
notifications@github.com> wrote:

The new overlay modes were AFAIK introduced by @joferkington
https://github.com/joferkington but are yet not in a release. Usually
we wait a bit before chancing the default. It we change this we should make
it an rcparam for 1.5 and add a warning that the default will change.


Reply to this email directly or view it on GitHub
#4700 (comment)
.

@mdboom mdboom modified the milestones: Color overhaul, next major release (2.0) Oct 8, 2015
@mdboom mdboom self-assigned this Nov 9, 2015
@mdboom
Copy link
Member

mdboom commented Nov 9, 2015

Which of 'overlay' or 'soft' would be the best default?

@joferkington
Copy link
Contributor

"overlay" is a better default than "soft", i.m.o.

I've never seen a surface where overlay blending the hillshade looks terribly bad. Sometimes it's less than ideal, but it's never awful. By contrast, soft light blending hillshades can yield a result that's almost unnoticeable in many cases.

From a purely qualitative standpoint, "soft" blending (which is Pegtop soft light blending, by the way) provides a very subtle hillshade effect. It's too subtle for "smooth" surfaces. "overlay" essentially gives more contrast to the hillshade effect.

Just my $0.02, at any rate.

mdboom added a commit to mdboom/matplotlib that referenced this issue Nov 17, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Nov 23, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Nov 23, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Nov 25, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Nov 27, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Nov 27, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Dec 14, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Dec 14, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Dec 14, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Dec 17, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Dec 31, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Dec 31, 2015
mdboom added a commit to mdboom/matplotlib that referenced this issue Jan 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants