FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

[Bug]: barplot does not show anything when x or bottom start and end with NaN · Issue #23687 · matplotlib/matplotlib · GitHub

Repository navigation

[Bug]: barplot does not show anything when x or bottom start and end with NaN #23687

Closed

Description

Bug summary

I am not sure if this is a bug or an optimization, but in most cases it is fine to plot bars of arrays containing NaN (only the NaN values are not displayed, the rest is ok).

Here I found that when the x array or the bottom array have NaNs at the extremities, no bar is displayed.

(barh has the same behavior).

Code for reproduction

import numpy as np, matplotlib as mpl, matplotlib.pyplot as plt

barx = np.arange(3, dtype=float)
barheights = np.array([0.5, 1.5, 2.0])
barstarts=np.array([0.77]*3)

barx[[0,2]] = np.NaN
# alternatively:
#barstarts[[0,2]] = np.NaN

fig, ax = plt.subplots()

ax.bar(barx, barheights, bottom=barstarts)
# Not ok, nothing shown!

# Same behavior with ax.barh:
ax.barh(barx, barheights, left=barstarts)

# However, the behavior is correct when NaN only affect the 'heights' argument:

fig, ax = plt.subplots()
ax.bar(np.arange(3), np.array([np.NaN, 1, np.NaN]), bottom=np.array([0.2, 0.3, 0.4]))
# OK, one bar is displayed.

Actual outcome

zero bar displayed

Expected outcome

Non-NaN elements should be shown

Additional information

No response

Operating system

Ubuntu 20.04.3

Matplotlib Version

3.5.3

Matplotlib Backend

TkAgg, pdf

Python version

3.8.10

Jupyter version

ipython

Installation

pip

Activity

  1. added this to the v3.7.0 milestone on Aug 26, 2022
  2. tacaswell commented on Aug 26, 2022

    Member

    I can reproduce this, but do not understand it yet.

  3. tacaswell commented on Aug 26, 2022

    Member

    In 7c4b000 / #12903 we added some logic to make sure that width would work with interesting units, notable time deltas and and datetime data.

    To do this we effective add the width to the first element of the x data, run it through the conversion machinery, and then subtract off the already converted value of the first data point to convert the "width" in (possibly unitful) user data into our internal version of it. However, if the first point in nan, then the width is poisoned to also be nan which means that when we make the Rectangles the x positions are nan which then (correctly) does not render anything.

  4. jklymak commented on Aug 26, 2022

    Member

    I guess we should be using the new safe_first_element excluding NaNs?

  5. tacaswell commented on Aug 26, 2022

    Member

    The new one only drops None, but I just finished adapting it to work with nan as well. PR shortly....

  6. added a commit that references this issue on Aug 26, 2022
    cfb27b3
  7. modified the milestones: v3.7.0, v3.6.1 on Sep 19, 2022
  8. added a commit that references this issue on Dec 19, 2022
    4e79d8d
  9. added 2 commits that reference this issue on Apr 19, 2026
    4a2faf8
    de50020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL