snowspeeder/roast_command_center
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rebuild printable roast plans and remove machine-based adjustments
Test and deploy / test-and-deploy (push) Successful in 2m28s
Details

Browse Source
This commit is contained in:
snowspeeder committed 2026-09-05 14:56:11 -04:00
1 parent e9f2393c96
commit 824a964f9d
30 files changed
+1721 -908
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

public/js/field-help-content.js
+41 -332
View File
@@ -16,7 +16,7 @@ import {
CHARGE_SETTINGS,
YELLOW_RATIO,
findCultivar,
} from "/shared/reference-data.js";
} from "/shared/reference-data.js?v=__ASSET_VERSION__";
// ---- small DOM builders --------------------------------------------------
@@ -754,60 +754,13 @@ export const HELP_TOPICS = {
const label = input?.closest(".ledger-row")?.querySelector(".l-label");
return label ? [label] : [];
},
render(_plan, unit, profile) {
const pace = profile?.pace;
const paceText =
pace?.source === "learned"
? `Your own account is currently running at ${pace.value.toFixed(2)}× the reference ` +
`pace (learned from ${pace.n} of your logged roasts) — that factor scales your ` +
"whole first-crack line by how fast your roasts have actually run overall. It's a " +
"single blanket ratio across your history, not something that adjusts itself by " +
"batch weight, so this table's specific charge/heat/fan settings are still worth " +
"reading as the reference operator's own notes, not something the learned pace " +
"stands in for."
: "This app now applies a learned per-user pace factor to first crack instead of a " +
"flat added-seconds guess (below, it defaults to 1× until you've logged at least " +
"two roasts with an actual first-crack time). That factor tracks how fast your " +
"machine runs overall — it isn't conditioned on batch weight — so the specific " +
"settings in this table are still the reference operator's own charge/heat/fan " +
"choices, not derived from your machine.";
return frag(
p(
"Batch size was the strongest correlate with first-crack time in the reference " +
"operator's own logged data (r = +0.67): a 226 g batch landed first crack roughly " +
"1:30–2:00 later than 200 g at similar settings — a ~13% weight increase stretching " +
"first crack ~40%, a scaling relationship a flat added-seconds guess can't fully " +
"represent. Field 6.4 below is still that same flat additive guess — you still " +
"enter it by hand for your own batch, and it's now folded into the line that the " +
"learned pace factor scales, so it moves by that factor too. What's new is a " +
"separate learned pace factor (below) that scales your entire first-crack line by " +
"how fast your account's roasts have actually run — but it's one blanket ratio " +
"across your whole history, not a per-batch-weight adjustment, so it doesn't replace " +
"6.4 for batch-to-batch changes.",
),
p(paceText),
buildTable({
cols: [
{ label: "Batch", key: "batch" },
{ label: "Charge probe", num: true, render: (row) => chargeProbeCell(row, unit) },
{ label: "Heat", key: "heat", num: true },
{ label: "Fan", key: "fan", num: true },
{ label: "Observed result", key: "observed" },
],
rows: CHARGE_SETTINGS,
}),
aside({
tag: "Charge temperature is a batch-size function",
text:
"Higher charge for larger batches is how the reference rows keep their timing. If " +
"your turning point lands much past 1:05 at 200 g, you charged cool.",
}),
);
},
},
render() {
return frag(p("Batch size can change roast behavior, but the app never applies machine pace or batch corrections automatically. Field 6.4 is an optional time adjustment you enter from your own observations. Change one variable at a time and compare the cup."));
},
},
"milestones-ror": {
title: "Milestones & the RoR budget — proven numbers, learned or reference",
title: "Milestones & rate of rise — planning references",
targets: [],
place() {
const subheads = [...document.querySelectorAll("#sec-machine .subhead")];
@@ -816,107 +769,15 @@ export const HELP_TOPICS = {
console.warn('field-help: "milestones-ror" fell back to positional lookup — subhead text changed?');
return subheads[0] ? [subheads[0]] : [];
},
render(_plan, unit, profile) {
const t = (c) => convTemp(c, unit);
const d = (c) => convDelta(c, unit);
const u = unitLabel(unit);
const ru = rateUnitLabel(unit);
const milestoneDefs = [
{ label: "Charge", ref: MACHINE.charge, learnedKey: "charge", timeSuffix: "", note: "The probe reading when beans go in, i.e. your preheat. Higher for larger batches." },
{ label: "Turning point", ref: MACHINE.turningPoint, learnedKey: "tp", timeSuffix: ` @ ${MACHINE.turningPoint.medianTime}`, rangeTimeSuffix: ` @ ${MACHINE.turningPoint.rangeTime}`, note: "Falls out of charge temperature and batch mass; you don't set it directly. A TP much past 1:05 at 200 g means you charged cool." },
{ label: "Yellow", ref: MACHINE.yellow, learnedKey: "yellow", timeSuffix: "", note: "Threshold-derived, not observed. Use as a rough guide and start calling it by eye — grassy smell turns to bread, colour goes straw." },
{ label: "First crack", ref: MACHINE.firstCrack, learnedKey: "fc", timeSuffix: "", note: "Tight and reliable in the reference log. Usually the single most trustworthy number here." },
{ label: "Drop (light)", ref: MACHINE.drop, learnedKey: "drop", timeSuffix: "", note: `For darker levels, build the ladder yourself: raise drop ${d(2)}–${d(3)} ${u}, weigh, record — don't extrapolate.` },
];
// Each milestone falls back to the reference band independently — a user might have
// enough of their own First crack readings to trust long before they bother recording
// Turning point, so this isn't a single all-or-nothing learned/reference switch.
const rows = milestoneDefs.map(({ label, ref, learnedKey, timeSuffix, rangeTimeSuffix, note }) => {
const learned = profile?.bands?.[learnedKey];
const useLearned = learned?.source === "learned";
const medianC = useLearned ? learned.medianC : ref.medianC;
const rangeC = useLearned ? learned.rangeC : ref.rangeC;
return {
milestone: useLearned ? `${label} (n=${learned.n})` : label,
median: `${t(medianC)} ${u}${timeSuffix}`,
range: `${t(rangeC[0])}–${t(rangeC[1])} ${u}${rangeTimeSuffix ?? timeSuffix}`,
note,
};
});
const anyLearned = profile?.bandsSource === "learned";
const introText = anyLearned
? "The rows marked (n=…) below are learned from your own logged roasts on this " +
"account; the rest still use the reference operator's original Hottop log until " +
"you've recorded enough actual temperatures of your own. The times and ratios in " +
"this app port between similar drum roasters; the temperatures never do — they're " +
"whichever machine and probe actually produced them."
: "These bands are the reference operator's original 14 Hottop KN-8828B-2K+ roasts — " +
"not yours, unless you're them. They'll start being replaced by your own account's " +
"figures automatically once you log actual temperatures at each milestone. The times " +
"and ratios in this app port between similar drum roasters; the temperatures never do.";
return frag(
p(
`${introText} Reference first crack reads ${t(176)}–${t(187)} ${u}, well below the ` +
`~${t(196)} ${u} a fast, well-immersed probe would show; that doesn't make it wrong, ` +
"it makes it that probe's own.",
),
buildTable({
cols: [
{ label: "Milestone", key: "milestone" },
{ label: "Median", key: "median", num: true },
{ label: "Range", key: "range", num: true },
{ label: "Note", key: "note" },
],
rows,
}),
p(
"For each phase, divide the temperature you must gain by the time you have. A phase " +
"outside its band means the plan is not reachable — change the ledger, not the roaster.",
),
buildTable({
cols: [
{ label: "Phase", key: "phase" },
{ label: `Machine-proven ${ru}`, key: "band", num: true },
],
rows: [
{ phase: "TP → Yellow", band: `${d(MACHINE.ror.tpToYellow[0])}–${d(MACHINE.ror.tpToYellow[1])}` },
{ phase: "Yellow → FC", band: `${d(MACHINE.ror.yellowToFc[0])}–${d(MACHINE.ror.yellowToFc[1])}` },
{ phase: "FC → Drop", band: `${d(MACHINE.ror.fcToDrop[0])}–${d(MACHINE.ror.fcToDrop[1])}` },
],
}),
aside({
tag: "Worked example — Typica, washed, light, 200 g",
text:
"Ledger gives yellow 4:15, first crack 7:30, development 1:30, drop 9:00. Turning " +
`point lands about 0:55 at ${t(85)} ${u}.`,
}),
formula(
`TP→Yellow: (${t(158)} − ${t(85)}) ${u} ÷ 3.33 min ≈ ${preciseRate(73, 3.33, unit)} ${ru}`,
`inside ${d(17)}–${d(25)} ✓`,
),
formula(
`Yellow→FC: (${t(183)} − ${t(158)}) ${u} ÷ 3.25 min ≈ ${preciseRate(25, 3.25, unit)} ${ru}`,
`inside ${d(6)}–${d(10)} ✓`,
),
formula(
`FC→Drop: (${t(190)} − ${t(183)}) ${u} ÷ 1.50 min ≈ ${preciseRate(7, 1.5, unit)} ${ru}`,
`inside ${d(3)}–${d(9)} ✓ — plan is reachable. Checks: drying 47%, Maillard 36%, DTR 17% — all in band.`,
),
h4("Terms"),
glossary([
["Turning point", "the lowest bean-probe reading after charge, where the beans stop cooling the drum and start absorbing heat"],
["Yellow / dry end", "free moisture largely gone, colour green→straw, smell grassy→bread; call it by eye and nose"],
["Maillard", "the browning phase between yellow and first crack — most of the sweetness, body and complexity"],
["First crack", "audible, exothermic; internal pressure ruptures the cell structure"],
["Development", "first crack to drop — the main acidity/sweetness lever and the only phase you can still adjust while roasting"],
["DTR", "development ÷ total roast time"],
["Rate of rise", "how fast bean temperature climbs, °C/min"],
["Exotherm", "around first crack the bean briefly releases its own heat — roughly +1.4 °C/min you did not command"],
["Second crack", "quieter, higher-pitched; dark-roast territory, past everything these numbers are validated for"],
]),
);
},
},
render() {
return frag(
p("Blank temperature fields draw an illustrative curve. Your entered readings take precedence. Roaster selection and historical measurements never adjust the plan."),
p("Preheat setpoint, environmental temperature and bean-probe temperature are different measurements. Record preheat separately. Mark yellow by color and aroma, and first crack by sustained audible cracking."),
p("Aim for controlled progression with declining RoR after its recovery peak. The smooth curve is interpolation, not a physical prediction. Phase-average RoR cannot show every brief crash or flick. Inconsistent entered milestones are flagged without rewriting your targets."),
p("Timing, DTR and turning point alone cannot diagnose cup quality. Evaluate color, aroma, the actual trace and tasting results together.")
);
},
},
actuators: {
title: "Heat & fan — the taper, and what actually moves first crack",
@@ -928,161 +789,28 @@ export const HELP_TOPICS = {
console.warn('field-help: "actuators" fell back to positional lookup — subhead text changed?');
return subheads[1] ? [subheads[1]] : [];
},
render(_plan, unit) {
return frag(
buildTable({
cols: [
{ label: "Point in roast", key: "point" },
{ label: "Heat", key: "heat", num: true },
{ label: "Fan", key: "fan", num: true },
{ label: "Intent", key: "intent" },
],
rows: TAPER_TEMPLATE,
}),
h4("Charge settings by batch"),
buildTable({
cols: [
{ label: "Batch", key: "batch" },
{ label: "Charge probe", num: true, render: (row) => chargeProbeCell(row, unit) },
{ label: "Heat", key: "heat", num: true },
{ label: "Fan", key: "fan", num: true },
{ label: "Observed result", key: "observed" },
],
rows: CHARGE_SETTINGS,
}),
aside({
tag: "The first-cut lever",
text:
"When you make the first heat cut is your main first-crack lever — later cut, earlier " +
"crack. Holding 100% to ~3:00 gave 7:55; cutting at ~1:00 gave 9:00. Steps of 3–5% " +
"beat single large ones, and the machine has roughly a 60-second dead time: what you " +
"change now shows up about a minute from now.",
}),
aside({
tag: "What the reference operator's own logs do NOT tell you",
warn: true,
text:
'"More heat before yellow gives an earlier first crack" does not hold in the reference ' +
"operator's 14-roast log — heat delivered before yellow correlates positively with " +
"first-crack time (r = +0.43) because it's partly a proxy for elapsed time; average " +
"heat rate shows almost none (r = +0.20). The honest correlates there are batch size " +
"(+0.67) and time to yellow (+0.59) — both descriptive, neither causal, and specific " +
"to that one operator's machine. The taper is a starting shape, not a validated " +
"control law: for a real lever on your own machine, vary only the time of the first " +
"heat cut across three batches of the same coffee and see what actually moves.",
}),
h4("Fan, measured causally"),
p(
`On the reference machine, isolated fan steps with the burner held steady gave roughly ` +
`${MACHINE.fanEffectCPerMinPer10Pct} °C/min of RoR per +10% fan — only 5 clean windows ` +
"across 4 roasts, but the one number in this reference set from a controlled " +
"comparison rather than a correlation. Worth re-measuring on your own machine before " +
"trusting it there.",
),
h4("The plant model"),
formula("RoR (°C/min) = 0.0903 × (0.988·H + 0.215·F + 167.0 − BT)"),
formula("H = (RoR ÷ 0.0903 − 0.215·F − 167.0 + BT) ÷ 0.988"),
p("H = heat %, F = fan %, BT = bean temp °C; above 178 °C add ~+1.4 °C/min for the exotherm."),
p(
"Treat it as a sanity check on direction and rough magnitude, not a setpoint calculator: " +
"it carries a ±5 °C band, a 60-second dead time, was fitted on the reference " +
"operator's light roasts of 200–226 g, and its fan term's sign is wrong for planning " +
"(fitted from closed-loop data — use the −1.3 figure instead). Where the equation and " +
"your own logged roasts disagree, believe your logs — this formula is a planning aid " +
"borrowed from someone else's machine, not a law.",
),
);
},
},
render() {
return frag(
p("Enter heat and airflow steps that you can repeat, with the reason for each change. No machine-specific heat/fan percentages or response formula is applied by this planner."),
p("Use your manufacturer's preheat routine and log the setpoint separately from charge BT. Anticipate the machine's response delay and make controlled changes before excessive momentum builds."),
p("Fan changes can affect heat transfer as well as exhaust. Their effect depends on the equipment and airflow path. Do not infer a universal effect from another operator's percentages."),
p("Compare one deliberate change across repeat batches and judge the cup as well as the trace. A correlation in a small roast history is not a validated control law.")
);
},
},
"sanity-checks": {
title: "Sanity checks — what a failure is telling you",
targets: [".checks-card .dock-card-head h2"],
render() {
return frag(
p(
"Two of these are real checks that stand between an arithmetically valid plan and a " +
"roastable one — a fail sends you back to the ledger, never to the machine. The " +
"other two (drying share, Maillard share) are shown for context only; see the aside " +
"below for why.",
),
buildTable({
cols: [
{ label: "Check", key: "check" },
{ label: "Compute", key: "compute" },
{ label: "Should be", key: "should", num: true },
{ label: "What a failure means", key: "meaning" },
],
rows: [
{
check: "Drying share (informational)",
compute: "yellow ÷ drop",
should: `${SANITY_BANDS.drying.lo}–${SANITY_BANDS.drying.hi}%`,
meaning:
"Can't fail independently of DTR (see below) — shown for context. High → " +
"yellow reads late relative to drop; low → yellow reads early.",
},
{
check: "Maillard share (informational)",
compute: "maillard ÷ drop",
should: `${SANITY_BANDS.maillard.lo}–${SANITY_BANDS.maillard.hi}%`,
meaning:
"Same derivation as drying share, so the same caveat applies. Mirrors it: " +
"whichever way drying share leans, this leans the other.",
},
{
check: "Development ratio",
compute: "dev ÷ drop",
should: `${SANITY_BANDS.dtr.lo}–${SANITY_BANDS.dtr.hi}% (light: 12–17)`,
meaning:
"Below 12% → likely under-developed whatever the clock says. Expect sharp, " +
"astringent acidity with no fruit behind it.",
},
{
check: "Development ceiling",
compute: "dev",
should: "< 4:30",
meaning: "Over 4:30 mutes even a dark roast. There is nothing useful on the other side of that line.",
},
],
}),
aside({
tag: "Why drying share and Maillard share stopped being pass/fail",
text:
"Yellow is never entered independently in this app — it's always derived as " +
"0.56 × first crack (see Anchor & profile). That means drying% = 0.56 × (A ÷ D) and " +
"Maillard% = 0.44 × (A ÷ D): both are pure algebra on the DTR check, not separate " +
"measurements. Whenever DTR passes, the arithmetic guarantees drying lands in " +
"44.8–49.3% and Maillard in 35.2–38.7% — comfortably inside both bands, every time. " +
"They used to display green or red checkmarks that implied four independent " +
"validations when only two ever could fail. They're kept here because the " +
"percentages themselves are still useful context — just not a verdict.",
}),
aside({
tag: "Worked check — when modifiers stack",
text:
"Bourbon anaerobic natural, light: anchor 8:45, base 1:30, natural −0:20, anaerobic " +
"−0:10 → development 1:00, DTR 10.3% — below the 12% floor. When stacked modifiers " +
"push you out of band, drop the smaller one rather than overriding the check.",
}),
aside({
tag: "The reference operator's own history runs outside these bands — read before dismissing",
warn: true,
text:
"Across the reference operator's 14 logged roasts the measured shares are drying " +
"65%, Maillard 25%, DTR 10.4% — all outside the bands, all in the same direction. " +
"Drying and Maillard are partly an artifact there: Artisan computes the dry end from " +
"a temperature threshold, not an observed colour change, which inflates drying and " +
"deflates Maillard in exactly this pattern — calling yellow by eye and smell is the " +
"fix, not concluding the roasts were structurally wrong. DTR is not an artifact: both " +
"first crack and drop are marked events. A median development of 1:00 is defensible " +
"for the naturals that dominate that log, but 0:45–0:52 is below the floor for any " +
"roast level; if those particular batches cupped sharp or thin, that's the number " +
"that should have moved.",
}),
);
},
},
render() {
return frag(
p("These checks describe a planning range, not a verdict on roast quality. DTR is development divided by total time; a ratio inside 12–20% does not guarantee good coffee, and one outside it does not prove a failure."),
p("Drying and Maillard shares are informational because the planner derives yellow as 0.56 × first crack. They are not independent measurements."),
p("For light plans, modifier suggestions below 1:15 are raised to 1:15 with a warning. This is a starting heuristic. Enter a direct development target to override it; your choice remains visible even outside the planning range."),
p("Check color, aroma, actual RoR, and tasting results together. Longer development may suit a different roast intent; the 4:30 check is a worksheet review threshold, not a universal physical limit.")
);
},
},
"roast-log": {
title: "At the machine — before charging, and during the roast",
@@ -1119,31 +847,12 @@ export const HELP_TOPICS = {
curve: {
title: "Reading the curve — what good looks like",
targets: [".curve-card .dock-card-head h2"],
render() {
return frag(
p(
"Plot the five milestones — bean temperature against the left axis, rate of rise " +
"against the right. Draw the plan before the roast, overlay what actually happened " +
"afterward, so one chart carries both.",
),
aside({
tag: "What a good curve looks like",
text:
"The bean-temperature line falls to the turning point in the first minute, climbs " +
"steeply out of it, then bends progressively flatter all the way to the drop. There " +
"is no straight segment and no second steepening. If your drawn line needs a kink to " +
"connect two milestones, the milestones are wrong — not the coffee.",
}),
aside({
tag: "The rate-of-rise line",
text:
"Starts near its peak just after the turning point (17–25 °C/min on a similar drum roaster) and " +
"declines steadily to somewhere between 3 and 9 °C/min at the drop. It never touches " +
"zero and never turns back up. Watch the region just after first crack in particular: " +
"the exotherm gives you free heat for a few seconds and then withdraws it, and that " +
"hand-off is where a crash appears.",
}),
);
},
},
render() {
return frag(
p("The graph labels milestone times and Fahrenheit temperatures directly, with drying, Maillard and development durations. An attached reference trace appears dashed on the live chart."),
p("The smooth plan line interpolates your milestones; it is not a predicted sensor trace. Blank temperatures are marked illustrative. Enter actual probe references when you have them."),
p("Aim for controlled progression and declining RoR after the recovery peak. Phase-average RoR alone cannot rule out a brief crash or flick. The graph plots BT, not a separate measured RoR trace.")
);
},
},
};