DataContainer.query() missing unit conversion?

Open
#7 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by locating DataContainer.query() and the plotting functions that currently make unit conversion difficult to inspect. Clarify whether original data must remain available while queried results are converted or sliced, and define the expected behavior for subsequent queries and end-user inspection before implementation.

Written by the indexing model from the issue text.

Description

Should DataContainer.query() include unit conversion? Or where will this happen? Ideally, I would like DataContainer to hold the data in its original form and then convert, slice, etc. upon query. Subsequent queries would start from the original data. Ideally, the enduser will be able to also inspect this DataContainer to verify its correctness. Today, that's impossible for some plotting functions and hard to do for others.

Dominant language
Python
Stars
10
Forks
6
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from matplotlib/mpl_data_containers

All issues in matplotlib/mpl_data_containers

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.