Il prossimoProssima guida
Metriche di valutazione ROUGE e BLEU
Tecnico
GUIDA TECNICA
Ranking metrics evaluate the order of items rather than only whether individual labels are correct.
Precision@k, recall@k, MAP, MRR and normalized discounted cumulative gain emphasize different aspects, so metric choice should match the ranking task and its relevance judgments.
Ranking systems order candidates for a user or query. Evaluation should reflect where relevant results appear and how relevance is defined. Precision at k is the fraction of the top k results judged relevant. Recall at k is the fraction of all relevant candidates retrieved in the top k. Precision emphasizes the quality of the displayed set; recall emphasizes how much of the relevant set was found. Average precision summarizes precision at ranks where relevant items occur, and mean average precision (MAP) averages that value across queries. Mean reciprocal rank (MRR) uses the reciprocal of the rank of the first relevant result and averages across queries. MRR is useful when finding one good result quickly is the priority, but it largely ignores the quality of later ranks. Discounted cumulative gain (DCG) supports graded relevance. A gain function assigns larger value to more relevant items, while a logarithmic discount reduces credit for items lower in the list. Normalized DCG divides a ranking's DCG by the ideal DCG for that query, giving a score typically between zero and one when definitions align. This normalization makes values more comparable across queries with different relevance distributions, but aggregation choices still matter. Suppose a query has one highly relevant item and another mildly relevant item. Placing the highly relevant result first yields more DCG than placing it second. NDCG captures both graded relevance and rank position. It does not establish whether the relevance labels are unbiased or whether the candidate-generation process omitted useful items. Metrics can change with cutoff k, gain formula and label threshold. Report these choices and evaluate across the same query set. Offline metrics also do not fully capture user satisfaction, diversity, freshness, exposure bias or long-term outcomes. Use them alongside online experiments or human review when appropriate, while avoiding claims that a higher score alone proves a better user experience.
Le decisioni relative all'architettura determinano prestazioni e costi operativi per anni.
La formazione tecnica aiuta i team a scegliere lo stack giusto, non solo quello più nuovo.
Migliori scelte ingegneristiche riducono gli incidenti legati all’affidabilità nella produzione.
Ranking reports can improve by displaying top-k metrics, relevance definitions and per-query distributions rather than one aggregate number. Teams should choose MAP, MRR or NDCG based on whether the task values all relevant results, the first useful result or graded quality throughout the list. They should audit relevance judgments and candidate exposure, since metrics cannot reward items never retrieved for evaluation. Human satisfaction and diversity checks can complement offline scores. As ranking objectives evolve, preserve consistent historical definitions so trend comparisons remain meaningful.
A search result list has five items and two are relevant. Precision@5 is 2/5, while recall@5 depends on how many relevant items exist in the full candidate set.
A user has three relevant items, and a system retrieves two within the top five. Recall@5 is 2/3 even though precision@5 is 2/5; the measures answer different questions.
For graded relevance, DCG rewards highly relevant items more when they appear near the top, using a gain and a logarithmic rank discount. NDCG divides by the ideal DCG for the same query to normalize the scale.
A recommendation team reports MRR when the first relevant result matters most and NDCG when multiple items and graded relevance across the list matter.
L'ottimizzazione di un benchmark può nascondere debolezze di sistema più ampie.
I costi delle infrastrutture e della manutenzione sono spesso sottostimati.
Le lacune in termini di sicurezza e osservabilità possono aumentare man mano che i sistemi diventano più complessi.
Definire obiettivi di latenza, qualità e costi prima dell'implementazione.
Benchmark in condizioni di carico e dati realistiche.
Monitoraggio dello strumento per errori, deriva e impatto sull'utente.
Preparare percorsi di rollback e risposta agli incidenti prima della scalabilità.
Free newsletter
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
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
Ranking metrics evaluate the order of items rather than only whether individual labels are correct. Precision@k, recall@k, MAP, MRR and normalized discounted cumulative gain emphasize different aspects, so metric choice should match the ranking task and its relevance judgments.
Precision@k divides relevant results in the top k by k, so it is 2/5.
Recall divides retrieved relevant items by the total relevant set: 2/3.
MRR averages the reciprocal rank of the first relevant result.
NDCG compares the observed order with an ideal ordering for the same query.
MRR is driven by the first relevant rank and is useful when an early useful result matters.
Continua a imparare
Altre guide selezionate per questo argomento
Il prossimoProssima guida
Metriche di valutazione ROUGE e BLEU
Tecnico