Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Ground truth: decide on gradient validation (currently fully unimplemented)

Offen
  • Stimmt etwas nicht?
#986 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
kotlin, python
Bereich
machine-learning, testing

Rechercherichtung

Start by reading gt/pytorch/io/writer.py, GroundTruthLoader.kt, GroundTruthValidator.validateGradientsInternal, CONTRACT.md, and TESTING.md to understand what is implemented and documented. Decide whether gradient validation should be implemented on both sides or explicitly de-scoped; done means the chosen path is made consistent across code and documentation, including removing misleading unused API surface if de-scoped.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

assessment question sub-issue

Sub-issue of #984.

Despite the "gradienttracer" name, no gradient is ever actually checked today.
ToleranceConfig.GRADIENT, GroundTruthTestCase.expectedGradients, and grad_*-tensor
parsing all exist on the Kotlin side (GroundTruthLoader.kt,
GroundTruthValidator.validateGradientsInternal) — but store_experiment_as_gguf
(gradienttracer's gt/pytorch/io/writer.py) never calls .backward() or writes any
grad_* tensor. validateGradientsInternal is explicitly a placeholder (// TODO: Implement actual gradient computation via tape) that always reports failure if ever
invoked with real data.

Decision needed

  • Implement it: add .backward() + grad_* tensor serialization to
    store_experiment_as_gguf (every @Executable input already has requires_grad=True
    set, so the gradient is available, just not captured), and implement SKaiNET-side
    backward-pass execution in GroundTruthValidator.validateGradientsInternal to actually
    compare against it. This is real, nontrivial work on both sides — SKaiNET's own
    autodiff/backward execution path needs to be driveable from
    skainet-test-groundtruth, which it currently isn't.
  • Explicitly de-scope it: if gradient validation isn't a near-term priority, say so
    in CONTRACT.md and TESTING.md (which currently reads as if this already works),
    and consider whether the dead expectedGradients/ToleranceConfig.GRADIENT/
    validateGradients parameter surface should be removed rather than left as
    looks-implemented-but-isn't.

Either answer is fine — the point of this issue is picking one, since right now the code
reads as "supported" when it silently isn't.

Vorherrschende Sprache
Kotlin
Sterne
52
Forks
15
Ø Merge
1 T. 50 Min.
Gemergte PRs (30 T.)
73

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus SKaiNET-developers/SKaiNET

Alle Issues in SKaiNET-developers/SKaiNET

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.