TinyChain-Inc / TinyChain-Inc/ha-ndarray

[CubeCL][P2.1] Implement reduction kernels and numerical conformance

Open
#44 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Objective

Implement the current reduction/aggregation surface on CubeCL with explicit empty-axis, accumulation, ordering and numerical-tolerance contracts.

Acceptance criteria

  • Inventory identifies every public reduction and its supported dtype/axis behavior.
  • Full, axis, multi-axis if supported, singleton, empty, non-contiguous and large inputs are covered.
  • Accumulator dtype, overflow, NaN and infinity behavior is documented and fixture-tested.
  • Deterministic guarantees are stated; nondeterministic floating ordering uses bounded per-operation tolerances.
  • CPU and designated accelerator results match the host oracle within those contracts.
  • Cold/warm performance and temporary-memory use are recorded.

Parent: #36

Tembo execution contract

automation:
  eligible: true
  executor_profile: tembo
  readiness: blocked
  primary_repository: TinyChain-Inc/ha-ndarray
  base_branch: main
  writable_scope:
    - src/cubecl/reduce/**
    - src/ops.rs
    - tests/conformance/**
    - benches/**
  prerequisites:
    - "#50 designated accelerator validation lane"
    - "#41"
    - "#42"
  concurrency_group: cubecl-reductions
  required_commands:
    - "cargo fmt --all -- --check"
    - "cargo test --no-default-features --features cubecl"
    - "cargo test --all-features"
  evidence:
    cpu_conformance: required
    accelerator_conformance: required-on-designated-runner
    actual_browser: not-required
    benchmark_report: required
    exact_hardware_and_driver_identity: required
  external_actions: none
  draft_pr_only: true
  completion_authority: human
  budget:
    size: large
    max_revisions: 3
    max_wall_minutes: 180

Contributor guide

Open the contributing guide

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.

Research direction

Start with the reduction scope in src/cubecl/reduce/** and src/ops.rs, then inspect tests/conformance/** and benches/**. First check prerequisites #50, #41 and #42, since execution is currently blocked. Done means the listed CPU and designated-accelerator conformance, tolerance and edge-case contracts are covered, required commands pass, and benchmark evidence records cold/warm performance and temporary memory.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
data, performance, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.