Fix behaviours of no/unknown units

Open
#6,997 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
data

Research direction

The issue names no files or tests; begin by locating the unit-handling code and reviewing the comments referenced in the report. Check the existing behaviour for unknown and no-unit values across combinations and derivations. Done means every stated combination and derivation produces 'unknown' where required.

Written by the indexing model from the issue text.

Description

Feature: cfpint

Behaviours were already questioned in these comments

We should override where necessary to ensure that behaviour makes sense.

  • both "unknown" + "no-unit" units should give 'unknown' in all combinations and derivations
Dominant language
Python
Stars
724
Forks
317
Avg merge
3d 20h
Merged PRs (30d)
9

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 SciTools/iris

All issues in SciTools/iris

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.