Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Lane 2 · kotlin-core] Precision/Recall/F1 — Averaging enum + internal ConfusionMatrixAccumulator

Abierto
  • ¿Algo no está bien?
#1,226 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
kotlin
Área
machine-learning

Línea de trabajo

First read Accuracy.kt, the helpers from #1225, and the contract decisions in #1224; this issue is blocked on both. Implement the public Averaging enum and the internal accumulator and reducer in sk.ainet.lang.nn.metrics, then test the reducer’s modes and zero-division case. Run ./gradlew :skainet-lang:skainet-lang-core:apiDump; done means the API dump adds Averaging only and the fixture produces the specified counts.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

coding size:s skill:kotlin-core sub-issue training

Sub-issue of #1222 (Precision, Recall and F1Score metrics).

Lane: 2 · Kotlin core
Skill needed: Kotlin; read Accuracy.kt and the helpers from #1225 first.
Size: s (~3–4 h)
Blocked by: #1225 (helpers) and the contract decisions from #1224 (zero-division, macro class set, binary mode).

What to do

  1. Add public enum class Averaging { BINARY, MACRO, MICRO } in
    sk.ainet.lang.nn.metrics (own file, KDoc on each value — this is public API).
    Semantics per #1224; the working definitions are:
    • BINARY — report class 1 (the positive class) only; requires ≤ 2 classes;
    • MACRO — unweighted mean of the per-class value over the class set decided in #1224;
    • MICRO — pool TP / FP / FN over all classes, then apply the formula once.
  2. Add internal class ConfusionMatrixAccumulator(dim: Int = -1, threshold: Float? = null)
    with
    • fun <T : DType, V> update(predictions: Tensor<T, V>, targets: Tensor<out DType, *>)
      — walks every sample via the #1225 helper and increments per-class tp / fp / fn
      (Long counters keyed by class index; a wrong prediction is one FP for the predicted
      class and one FN for the target class);
    • fun counts(): Map<Int, ClassCounts> (a small internal data class ClassCounts(tp, fp, fn));
    • fun reset().
  3. Add internal fun reduce(counts, averaging, perClass: (tp: Long, fp: Long, fn: Long) -> Double): Double
    implementing the three averaging modes and the zero-division convention from #1224
    in one place, so Precision, Recall and F1Score each contribute only a formula.
  4. Tests: the accumulator is internal to skainet-lang-core, and the metric tests live
    in skainet-backend-cpu (they need DirectCpuExecutionContext to build tensors). Two
    options — pick one and say which in the PR:
    • test it through Precision / Recall in #1227 / #1228 (then this PR ships
      with a reduce() unit test only, which needs no tensors), or
    • put an accumulator test in skainet-lang-core's commonTest, building tensors with
      DenseTensorDataFactory().fromFloatArray(...) + SimpleTensor(...) the way
      OperationExecutor.createTensor does.
  5. ./gradlew :skainet-lang:skainet-lang-core:apiDump — the dump gains Averaging and
    nothing else.

Acceptance

  • Averaging public, documented, in the API dump
  • ConfusionMatrixAccumulator + reduce() internal, no public surface
  • reduce() tested for macro / micro / binary and the zero-division case
  • Reference fixture from #1224 (pred [2,0,1,2], target [2,1,1,0]) yields counts
    {0: (0,1,1), 1: (1,0,1), 2: (1,1,0)} as (tp, fp, fn)

Notes

Don't build Precision / Recall / F1Score here even though it's tempting — they are
separate good first issues (#1227, #1228, #1229) precisely so three people can each
ship one small PR against this accumulator.

Lenguaje dominante
Kotlin
Estrellas
52
Forks
15
Merge medio
1 d 15 h
PR fusionados (30 d)
36

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SKaiNET-developers/SKaiNET

Todos los issues de SKaiNET-developers/SKaiNET

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.