All rules

A runtime longer than the battery capacity divided by the consumption

capacity-runtime-mismatchon by defaultJapanese / English

A runtime longer than the battery capacity divided by its consumption

Example

Flagged
| Item | Specification | | --- | --- | | Battery capacity | 50 Wh | | Power consumption | 10 W | | Runtime | 8 hours |
What chaff prints
5:13 50 Wh at 10 W lasts 5 hours, but the runtime is given as 8 hours
Fixed
| Item | Specification | | --- | --- | | Battery capacity | 50 Wh | | Power consumption | 10 W | | Runtime | 5 hours |
What chaff prints
no finding

How to fix

Check that the capacity, the consumption and the runtime are values of the same condition, and correct the one that is not.

Why it matters

When a spec states "Capacity 5000 mAh, current draw 500 mA, runtime 15 hours", 5000 mAh at 500 mA lasts 10 hours, so 15 hours cannot be reached. It happens when the consumption or the runtime is replaced with the value of another condition or another model. A real runtime is normally shorter than the division because of conversion losses, so a shorter one is not reported. Only a runtime above the division by more than one step of its last written digit (1 hour for "15 hours") is reported; when any of the three is marked "about" or "up to", that margin is doubled.

What it does not flag

Only a capacity, a consumption and a runtime written as table rows (item name and value) or "item name: value" lines, in the same table or the lines of the same section, are read; a wider table is one device per column. mAh is divided only by mA and Wh only by W; mAh is never divided by W, since whether the voltage is the nominal or the operating one cannot be told. A maximum consumption ("max" in the item name, a "Max" column) is not used, and a standby consumption pairs only with a standby time. With two or more consumptions and runtimes, only those with the same condition in brackets ("(50% volume)") are paired. A range ("8-10 hours", "300-500 mA") is compared at the end that favours the writer (the shorter runtime, the smaller consumption, the larger capacity). A value bounded on one side ("at least", "under") and values in running sentences are not read.

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: capacity-runtime-mismatch — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax capacity-runtime-mismatch --why "reason"
Turn it off for the team (chaff.yaml)
rules: capacity-runtime-mismatch: off
Technical details
Layer
L3
Status
stable
Severity
warning
Languages
Japanese and English
Suited to
business, technical, blog, legal, docs, academic, literature, speech

Levels

Set a level for this rule under rules in chaff.yaml. With nothing set, it runs at the level its genre gives it (see By genre below).

normalwarning
relaxedinfo

This rule has no limit to count to. A level sets how a finding is marked: relaxed keeps the finding and marks it a step lower.

By genre

Runs by default in
technical/spec, technical/readme, blog/tech, blog/essay, blog/owned-media, business/proposal, business/report, business/email, business/press-release, business/meeting-notes, legal/contract, legal/statute, legal/judgment, legal/patent, docs/manual, docs/faq, docs/glossary, academic/paper, literature/fiction, literature/essay, literature/poetry, literature/play, speech/address, speech/transcript

Genres

Message

{capacity} at {consumption} lasts {expected} hours, but the runtime is given as {runtime}

This page is built from the rule's definition file:packages/chaff/rules/capacity-runtime-mismatch.yaml