食物の成分表示に改善が必要
# Livityへの改善要望
## 対象データ
**料理**：アオサ・カボチャ・卵の味噌汁（自家製、Livityでの栄養計算結果）
| 項目 | 表示値 |
|---|---|
| タンパク質 | 10g |
| 炭水化物 | 13g |
| －糖質 | 5g |
| －食物繊維 | 1g |
| 脂質 | 6g |
| ナトリウム | 871mg |
| 水分 | 180ml |
## 問題点
炭水化物の内訳として糖質と食物繊維が表示されていますが、両者を合計しても炭水化物の値と一致しません。
- 糖質5g ＋ 食物繊維1g ＝ 6g
- 表示されている炭水化物：13g
- **差：7g**
「炭水化物＝糖質＋食物繊維」は栄養成分の定義そのものであり、家庭料理のAI栄養計算であっても本来常に成立すべき関係です。この等式が崩れているということは、糖質・食物繊維・炭水化物のいずれか（または複数）の算出ロジックに誤りがあることを示しています。
## 補足情報（原因の手がかり）
食材のうちアオサは食物繊維含有量が非常に高い食品です（日本食品標準成分表等の情報源によれば、素干し100gあたり約29〜44g）。味噌汁に使う分量はごく少量（2〜3g程度）ですが、それでも1g弱の食物繊維に相当し、そこにカボチャ由来の食物繊維（生100gあたり約2.8g）が加わります。
このため、表示されている「食物繊維1g」はやや過小評価されている可能性があります。ただし、仮に食物繊維を実態に近い2〜4g程度に補正しても、13g（炭水化物）－5g（糖質）＝8gという差はまだ埋まりません。したがって、食物繊維の集計漏れだけでなく、炭水化物または糖質の算出ロジック自体にも問題がある可能性があります。
## 要望事項
1. 炭水化物・糖質・食物繊維の内訳が、複数食材から構成されるレシピにおいても正しく積算され、「炭水化物＝糖質＋食物繊維」の等式が常に成立するよう、計算ロジックをご確認ください。
2. 可能であれば、上記の等式を出力前に自動チェックする内部検証（サニティチェック）機構の導入をご検討ください。
3. 本件が既知の不具合であるか、あるいは特定の食材（海藻類など食物繊維が突出して多い食品）の組み合わせで発生しやすい問題であるか、可能な範囲でご教示いただけますと幸いです。
---
# Improvement Request for Livity
## Data in Question
**Dish**: Homemade miso soup with aosa (sea lettuce), kabocha (pumpkin), and egg — nutrition figures as calculated by Livity
| Item | Displayed Value |
|---|---|
| Protein | 10g |
| Carbohydrates | 13g |
| – Sugars/Net carbs (糖質) | 5g |
| – Dietary fiber | 1g |
| Fat | 6g |
| Sodium | 871mg |
| Water | 180ml |
## Issue
The breakdown of carbohydrates into sugars (糖質) and dietary fiber does not sum to the total carbohydrate value shown.
- Sugars 5g + Dietary fiber 1g = 6g
- Displayed total carbohydrates: 13g
- **Discrepancy: 7g**
The relationship "Total carbohydrates = Sugars (糖質) + Dietary fiber" is a compositional definition of the nutrient category itself, not merely a food-labeling convention — it should hold true regardless of whether the item is a packaged product or an AI-calculated home-cooked recipe. The fact that this identity does not hold indicates a calculation error somewhere in how carbohydrates, sugars, and/or fiber are derived.
## Supporting Detail (Possible Root Cause)
Aosa (dried sea lettuce) is an exceptionally fiber-dense ingredient — Japanese food composition data sources put it at roughly 29–44g of dietary fiber per 100g. Even at the small quantity typically used in miso soup (around 2–3g), this alone would contribute close to 1g of fiber, before accounting for the additional fiber contributed by kabocha (roughly 2.8g per 100g fresh).
This suggests the displayed "1g" of dietary fiber may be undercounted. However, even correcting fiber upward to a more realistic 2–4g still leaves a gap of roughly 8g between total carbohydrates (13g) and sugars (5g). This implies the issue is not limited to under-aggregated fiber, and may also involve an error in how total carbohydrates or sugars are calculated.
## Requested Actions
1. Please review the calculation logic to ensure that, for multi-ingredient recipes, the carbohydrate/sugar/fiber breakdown is aggregated correctly so that "Total carbohydrates = Sugars + Dietary fiber" always holds.
2. Consider adding an internal sanity check that validates this identity before displaying results to users.
3. If possible, please let us know whether this is a known issue, or whether it tends to occur specifically with ingredient combinations involving very fiber-dense items such as seaweed.
## 対象データ
**料理**：アオサ・カボチャ・卵の味噌汁（自家製、Livityでの栄養計算結果）
| 項目 | 表示値 |
|---|---|
| タンパク質 | 10g |
| 炭水化物 | 13g |
| －糖質 | 5g |
| －食物繊維 | 1g |
| 脂質 | 6g |
| ナトリウム | 871mg |
| 水分 | 180ml |
## 問題点
炭水化物の内訳として糖質と食物繊維が表示されていますが、両者を合計しても炭水化物の値と一致しません。
- 糖質5g ＋ 食物繊維1g ＝ 6g
- 表示されている炭水化物：13g
- **差：7g**
「炭水化物＝糖質＋食物繊維」は栄養成分の定義そのものであり、家庭料理のAI栄養計算であっても本来常に成立すべき関係です。この等式が崩れているということは、糖質・食物繊維・炭水化物のいずれか（または複数）の算出ロジックに誤りがあることを示しています。
## 補足情報（原因の手がかり）
食材のうちアオサは食物繊維含有量が非常に高い食品です（日本食品標準成分表等の情報源によれば、素干し100gあたり約29〜44g）。味噌汁に使う分量はごく少量（2〜3g程度）ですが、それでも1g弱の食物繊維に相当し、そこにカボチャ由来の食物繊維（生100gあたり約2.8g）が加わります。
このため、表示されている「食物繊維1g」はやや過小評価されている可能性があります。ただし、仮に食物繊維を実態に近い2〜4g程度に補正しても、13g（炭水化物）－5g（糖質）＝8gという差はまだ埋まりません。したがって、食物繊維の集計漏れだけでなく、炭水化物または糖質の算出ロジック自体にも問題がある可能性があります。
## 要望事項
1. 炭水化物・糖質・食物繊維の内訳が、複数食材から構成されるレシピにおいても正しく積算され、「炭水化物＝糖質＋食物繊維」の等式が常に成立するよう、計算ロジックをご確認ください。
2. 可能であれば、上記の等式を出力前に自動チェックする内部検証（サニティチェック）機構の導入をご検討ください。
3. 本件が既知の不具合であるか、あるいは特定の食材（海藻類など食物繊維が突出して多い食品）の組み合わせで発生しやすい問題であるか、可能な範囲でご教示いただけますと幸いです。
---
# Improvement Request for Livity
## Data in Question
**Dish**: Homemade miso soup with aosa (sea lettuce), kabocha (pumpkin), and egg — nutrition figures as calculated by Livity
| Item | Displayed Value |
|---|---|
| Protein | 10g |
| Carbohydrates | 13g |
| – Sugars/Net carbs (糖質) | 5g |
| – Dietary fiber | 1g |
| Fat | 6g |
| Sodium | 871mg |
| Water | 180ml |
## Issue
The breakdown of carbohydrates into sugars (糖質) and dietary fiber does not sum to the total carbohydrate value shown.
- Sugars 5g + Dietary fiber 1g = 6g
- Displayed total carbohydrates: 13g
- **Discrepancy: 7g**
The relationship "Total carbohydrates = Sugars (糖質) + Dietary fiber" is a compositional definition of the nutrient category itself, not merely a food-labeling convention — it should hold true regardless of whether the item is a packaged product or an AI-calculated home-cooked recipe. The fact that this identity does not hold indicates a calculation error somewhere in how carbohydrates, sugars, and/or fiber are derived.
## Supporting Detail (Possible Root Cause)
Aosa (dried sea lettuce) is an exceptionally fiber-dense ingredient — Japanese food composition data sources put it at roughly 29–44g of dietary fiber per 100g. Even at the small quantity typically used in miso soup (around 2–3g), this alone would contribute close to 1g of fiber, before accounting for the additional fiber contributed by kabocha (roughly 2.8g per 100g fresh).
This suggests the displayed "1g" of dietary fiber may be undercounted. However, even correcting fiber upward to a more realistic 2–4g still leaves a gap of roughly 8g between total carbohydrates (13g) and sugars (5g). This implies the issue is not limited to under-aggregated fiber, and may also involve an error in how total carbohydrates or sugars are calculated.
## Requested Actions
1. Please review the calculation logic to ensure that, for multi-ingredient recipes, the carbohydrate/sugar/fiber breakdown is aggregated correctly so that "Total carbohydrates = Sugars + Dietary fiber" always holds.
2. Consider adding an internal sanity check that validates this identity before displaying results to users.
3. If possible, please let us know whether this is a known issue, or whether it tends to occur specifically with ingredient combinations involving very fiber-dense items such as seaweed.
Show more
Top
Bin mit meinem Oura Ring umgestiegen auf die Livity App. Ist moderner gestaltet, Oura Ring perfekt integriert - zeigt mir alle notwendigen Daten, hilfreiche Grafiken und Tipps. Könnte an der ein oder anderen Stelle etwas snappier/flüssiger reagieren, Design an sich aber 10/10.
Insights Galore
This is such a great program. It takes all the stats the Apple Watch tracks and provides a clean interface that lets me understand exactly what is happening. The recovery from previous activity is invaluable for my training and planning.
Makes Apple Health Data Cooler!
I was looking a buying an expensive fitness band to collect a bunch of metrics that I want to track but I hesitated because the bands are expensive and I already own an Apple Watch. I know the watch collects mostly the same stuff so getting a band was really just to be able to use the associated app to get better insights into my health than what Apple provides in Apple Health.
The problem is Apple Health doesn’t do much with the data the watch collects unlike most fitness band apps. While looking into fitness bands to fill the gap I came across a YouTube video suggesting trying this app out first and sure enough it makes the Apple Health data so much more useful! It’s so good that I don’t need to buy a fitness band at all because this app presents the data from the Apple Watch I already own for so well!
It figures out my recovery time, it calculates my metabolic age, it even tracks food plus a whole bunch of other stuff! And it presents it all in this cool cyberpunkish look! The best part is you can turn off the AI assistant once and it doesn’t seem to bug you ever again which is great.
The problem is Apple Health doesn’t do much with the data the watch collects unlike most fitness band apps. While looking into fitness bands to fill the gap I came across a YouTube video suggesting trying this app out first and sure enough it makes the Apple Health data so much more useful! It’s so good that I don’t need to buy a fitness band at all because this app presents the data from the Apple Watch I already own for so well!
It figures out my recovery time, it calculates my metabolic age, it even tracks food plus a whole bunch of other stuff! And it presents it all in this cool cyberpunkish look! The best part is you can turn off the AI assistant once and it doesn’t seem to bug you ever again which is great.
Show more
Bien mais trop lent
Les données fournies par l’application sont top. Par contre niveau optimisation c’est une catastrophe. L’actualisation des données est beaucoup trop longue et j’ai l’impression que le téléphone chauffe pas mal quand ça actualise (iPhone 15)
