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
Specifying a locator object via a kwarg to contourf results in levels coming from a call to tick_values, which bypasses the view_limits calculation. This means that setting the 'symmetric =True' kwarg in a MaxNLocator passed to contourf has no effect. One way to fix this would be to revert 354d133, which removed the use of a dummy axis in contourf. Another way would be to use the symmetric setting in tick_values itself. A third would be to allow the Locator.__call__ method to take vmin, vmax arguments, avoiding the need to explicitly create a dummy axis and set its limits.
My inclination is to do the quick fix--revert 354d133--in v2.x, and then switch to something like the third option for 2.1 or later.
The text was updated successfully, but these errors were encountered:
A likely use case is contouring fields such as a velocity
component, where one wants to use a diverging colormap
centered on zero.
Closesmatplotlib#7271.
NelleV
changed the title
BUG: symmetric kwarg in locator is not honored by contourf
[MRG+1] BUG: symmetric kwarg in locator is not honored by contourf
Oct 17, 2016
NelleV
changed the title
[MRG+1] BUG: symmetric kwarg in locator is not honored by contourf
BUG: symmetric kwarg in locator is not honored by contourf
Oct 17, 2016
Specifying a locator object via a kwarg to contourf results in levels coming from a call to
tick_values
, which bypasses theview_limits
calculation. This means that setting the 'symmetric =True' kwarg in a MaxNLocator passed to contourf has no effect. One way to fix this would be to revert 354d133, which removed the use of a dummy axis in contourf. Another way would be to use the symmetric setting in tick_values itself. A third would be to allow theLocator.__call__
method to take vmin, vmax arguments, avoiding the need to explicitly create a dummy axis and set its limits.My inclination is to do the quick fix--revert 354d133--in v2.x, and then switch to something like the third option for 2.1 or later.
The text was updated successfully, but these errors were encountered: