Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Lane 3 · js] Precision/Recall/F1 — JS/Wasm target parity check

Open Beginner friendly
  • Is something wrong?
#1,232 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
javascript, kotlin, node.js, wasm
Domain
machine-learning, testing

Research direction

This is a smoke check, not new code: after #1229 (F1Score) is on develop, run ./gradlew :skainet-backends:skainet-backend-cpu:jsTest --tests "sk.ainet.exec.metrics.*" and the matching wasmJsTest (Karma browser; wasmWasiNodeTest exists too). Confirm sk.ainet.exec.metrics.* pass and match JVM bit-for-bit on Double/Long counters. Done means posting target, toolchain, pass/fail, and wall-clock on #1222, or opening a linked bug if a task or expect/actual gap appears.

Written by the indexing model from the issue text.

Description

coding good first issue platform size:xs skill:js sub-issue

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

Lane: 3 · Platform verification · JS / Wasm
Skill needed: Kotlin/JS & Kotlin/Wasm (Node.js, a headless browser via Karma) build tooling — running a Kotlin Multiplatform module's tests on this target. No tensor-internals or metrics knowledge required. The code under test is pure commonMain Kotlin over Double counters; this is a smoke check, not new implementation.
Size: xs (~30–60 min)
Blocked by: #1229 (F1Score merged to develop), or check out its branch early.

What to do

  1. ./gradlew :skainet-backends:skainet-backend-cpu:jsTest --tests "sk.ainet.exec.metrics.*"
  2. ./gradlew :skainet-backends:skainet-backend-cpu:wasmJsTest --tests "sk.ainet.exec.metrics.*"
    (browser via Karma; wasmWasiNodeTest also exists for the WASI target).

Then, in every case:

  • Confirm the metric tests (sk.ainet.exec.metrics.*) pass and the values match the JVM run
    bit-for-bit — pure Long counting and Double division, so any drift is itself a finding.
  • Report on #1222: target, toolchain versions, pass/fail, wall-clock, anything
    target-specific you hit (an expect/actual gap, a disabled test source set, a task
    that doesn't exist).

Acceptance

  • Result posted on #1222 with the exact Gradle task(s) run
  • If something is wrong, a separate bug issue opened and linked — don't block the
    parent on investigating it here

Notes

JS numbers are IEEE doubles, so Double results must match JVM exactly; Long counters
are emulated on JS — an overflow-free smoke test, but worth confirming a batch of a few
thousand samples still counts correctly.

Dominant language
Kotlin
Stars
52
Forks
15
Avg merge
1d 15h
Merged PRs (30d)
36

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SKaiNET-developers/SKaiNET

All issues in SKaiNET-developers/SKaiNET

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.