Open Macaron chat to adapt the request below. Review account access and plan conditions before creating a tool.
Scale a portion before comparing a nutrient total
Use a detailed nutrition database when the nutrient question depends on product, preparation and portion. A custom record can make arithmetic visible, but it cannot fill an unknown nutrient value or establish a deficiency. Keep the source amount and portion unit together.
Sample request
"Build a manual nutrition record with food description, source note and only a nutrient goal supplied by my clinician. Keep nutrient amount/unit, reference grams and eaten grams separate. Require reference grams greater than zero and eaten grams at least zero; use amount × eaten grams ÷ reference grams only for complete compatible inputs. Preserve unknown values and incomplete totals; do not assess deficiency."
Suggested fields: Date; food description; amount; unit; supplied goal; known value; source note.
Proposed checks with fictional data:
Illustrative data check: a nutrient amount given per 100 grams must be scaled to the portion actually entered.
Before comparing similarly named entries, fix the food description and preparation state, then the consumed mass. A hypothetical 8 mg per 100 g scales to 4 mg at 50 g only for that same reference entry; swapping in a cooked or branded item changes the source value, not merely the serving multiplier.
Which workflow fits your needs?
| Need | Cronometer | Macaron example |
|---|
| Main purpose | A nutrition database and detailed nutrient tracking | A simpler record with chosen fields |
| What you work with | Food lookup, nutrient analysis and supported integrations | Entered amounts, units and professional-supplied goals |
Macaron does not replace a nutrient database or assess deficiency. Use a qualified dietitian or clinician for medical nutrition goals and avoid sharing identifying health records.