How close is
the number?
We typed 48 meals the way you would and sent each one through the same request the app makes, three times over. Every log was scored against USDA. Each figure below says how many logs it counts and which way it misses.
100 − |logged − USDA| ÷ USDA, averaged over 144 logs.
The “close enough” number. One dot per log; a miss counts as outside.
Mean signed error. Slightly low; an average accuracy would hide which way.
Items matched to a USDA record. The rest are the model’s estimate.
A single whole food mostly tests whether the lookup finds its USDA record, so those score high. Plates, dishes and vague amounts are where the score means something. Read those rows first.
Easy where the record exists.
Hardest first. Bias shows which way a category misses: blue logs low, orange logs high.
One dot per meal.
Logged calories, mean of three tries, against the USDA key. On the line is exact; the band is ±20%. 39 of 48 meals average inside it.
Same message, three answers.
Each message sent three times, unchanged. The ten least repeatable, widest first. This needs no answer key: the range is the app disagreeing with itself.
When it’s wrong, can you fix it?
Every total opens into the rows that make it. So the real test is whether the rows add up, and whether correcting one row repairs a wrong total.
The other log recorded nothing, so it has no rows to open.
Knowing the answer. Checking only the biggest row, the way you would without one, repairs 24.
Every row, with its rows.
Each log shows what it was built from, so you can see why it landed where it did.
Showing 48 of 48 meals. Tries are three separate sends of the same message. Accuracy is the mean of the three.
What this can and can’t say.
- Each message goes through the Log screen’s production request and the production food lookup, the same path a member’s meal takes.
- The key is USDA FoodData Central, built per component from named records and portions.
- Vague amounts (“some rice”) are keyed to the FDA reference amount customarily consumed, and pass on a ×1.5 band. 20 of 24 land inside it.
- Thresholds (±20%, ×1.5) were fixed before any run. No shared food cache is read or written.
- Photos. This is typed text only. Photo logging is measured on weighed meals, separately.
- Your meals. Every message was written by us; none come from a member’s log.
- Restaurant dishes outside the key. The lookup queries USDA, so whole foods partly test the lookup itself.