Plotly does not produce bar chart data when there is missing data

[bikegeek]

Describe the Problem

First observed in METviewer. When attempting to generate a bar chart using Python (via plotly), no bars are present. However, when using the R-script code, the following plot is observed:

Expected Behavior

Using the following (remove the additional .txt extension from the files before using):
custom_bar.yaml.txt
plot_20230313_212614.xml.txt
plot_20230313_212614.data.txt

Create a bar plot:

Environment

Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop) all
2. OS: (e.g. RedHat Linux, MacOS) All OS
3. Software version number(s) METplotpy v 2.0.0 beta1

To Reproduce

Describe the steps to reproduce the behavior:
Clone the develop branch of METplotpy
copy the custom_bar.yaml.txt and plot_20230313_212614.data.txt to the METplotpy/metplotpy/plots/bar directory

Remove the .txt extension
Run the following:
python bar.py custom_bar.yaml

You will generate this plot:

Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Organization level Project for support of the current coordinated release
• Select Repository level Project for development toward the next official release or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Bugfix Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of main_<Version>.
  Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
• Fix the bug and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into main_<Version>.
  Pull request: bugfix <Issue Number> main_<Version> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issues
  Select: Organization level software support Project for the current coordinated release
  Select: Milestone as the next bugfix version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Complete the steps above to fix the bug on the develop branch.
  Branch name: bugfix_<Issue Number>_develop_<Description>
  Pull request: bugfix <Issue Number> develop <Description>
  Select: Reviewer(s) and Development issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Close this issue.