基本ガイド
F1 Score and F-Beta
F1 combines precision and recall through their harmonic mean, rewarding a classifier only when both are reasonably strong.
このページでは3 分で読めます
概要
F-beta uses a parameter to put more weight on recall or precision for a stated task. These scores depend on the chosen positive class, threshold and averaging method and do not summarize every cost or fairness concern.
ディープダイブ
Precision asks what share of predicted positive cases are truly positive; recall asks what share of actual positive cases were found. F1 combines them as the harmonic mean, 2 × precision × recall divided by their sum when that denominator is nonzero. The harmonic mean falls when one component is low, so a classifier cannot earn a high F1 merely by excelling at one side. The score is useful for comparing systems with the same task definition, but it does not tell a team which kind of mistake matters more. Consider invented counts of eight true positives, two false positives and eight false negatives. Precision is 8/(8+2) = 0.8 and recall is 8/(8+8) = 0.5. F1 is 2 × 0.8 × 0.5/(0.8+0.5), about 0.615. The equivalent count formula is 2TP/(2TP+FP+FN), or 16/26. Report the counts as well as the score so readers understand what happened. F-beta generalizes F1. When beta is greater than one, recall carries more weight; when beta is less than one, precision does. F2 may suit a screening workflow where missing a relevant case is more costly than sending another case for review, but the choice needs an operational justification. It does not eliminate the need to inspect false positives, capacity limits or subgroup outcomes. A threshold change can trade precision against recall and therefore alter F-beta even if the underlying score model is unchanged. For multiple classes, macro averaging computes the per-class result and then gives each class equal weight. Micro averaging pools true positives, false positives and false negatives across classes before computing the score. These answer different questions when class frequencies vary. State the positive label and averaging rule explicitly. An F1 number says nothing directly about probability calibration, economic cost, or whether a small subgroup is being missed. Evaluate those separately, and use a held-out dataset that represents the decisions the model will face.
戦略的影響
より明確な判決
これは、明確な技術的主張とマーケティング言語を区別するのに役立ちます。
費用と予算
お金や時間を費やす前に、実装に関するより良い質問をすることができます。
チームとワークフロー
共通の理解を持ったチームは、製品、ポリシー、学習に関する意思決定をより適切に行うことができます。
The Future of F1 Score and F-Beta
As AI evaluations cover more classes and deployment settings, a single F1 number will become less adequate for decision making. Teams may use F-beta to encode a documented preference for recall or precision, but a beta value is still a simplification of real costs. Better reports should show the counts, averaging rule, operating threshold and uncertainty together. Changing populations can alter precision even if recall stays stable, so metrics need refresh after deployment. Future dashboards may make tradeoffs easier to explore, but the choice of who bears each error remains a policy and product decision that no formula can settle automatically.
現実世界の実装
A screening team reports F2 when missing relevant cases is costlier than reviewing an extra false alert, while still showing both precision and recall.
An analyst computes F1 from eight true positives, two false positives and eight false negatives in a constructed example.
A multiclass evaluator reports macro F1 to show how uncommon classes perform instead of presenting only an overall average.
A product team compares metrics at several decision thresholds and verifies that the chosen setting fits review capacity and error costs.
リスクとガードレール
チームが異なれば、同じ用語の使用方法も異なる可能性があるため、範囲を早めに定義してください。
ベンチマークは好調に見えても、実際のパフォーマンスにはばらつきがある場合があります。
データの品質と評価計画を無視すると、多くの場合、脆弱な結果が生じます。
実装ロードマップ
必要な結果を平易な言葉で定義することから始めます。
テストする前に、成功指標と失敗条件を 1 つ選択します。
洗練されたデモセットではなく、代表的なデータを使用して小規模なパイロットを実行します。
Document where F1 Score and F-Beta helps and where simpler methods are better.
探検を続けましょう
Free newsletter
Get the daily AI briefing
Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.
One email each weekday. Unsubscribe in one click. We never sell or share your address.
Test yourself
Take the F1 Score and F-Beta quiz
Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.
Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation
よくある質問
What is F1 Score and F-Beta?
F1 combines precision and recall through their harmonic mean, rewarding a classifier only when both are reasonably strong. F-beta uses a parameter to put more weight on recall or precision for a stated task. These scores depend on the chosen positive class, threshold and averaging method and do not summarize every cost or fairness concern.
How does F1 combine precision and recall?
F1 is 2PR/(P+R), the harmonic mean of precision and recall when defined.
In the guide's constructed 8 TP, 2 FP and 8 FN example, what is F1 approximately?
The count formula gives F1 = 2TP/(2TP+FP+FN) = 16/26 ≈ 0.615.
When beta is greater than one in F-beta, which component receives more weight?
F-beta with beta greater than one emphasizes recall relative to precision, without removing precision.
A task values avoiding false alerts more than catching every positive case. Which beta direction can reflect that priority?
A beta between zero and one weights precision more heavily, though actual task costs still need review.
What does macro F1 do across multiple classes?
Macro averaging gives equal weight to each class's F1, making minority-class behavior more visible than a prevalence-weighted summary.
学び続ける
関連ガイド
このトピックのために選ばれたその他のガイド