Skip to content

F4 — Lanes, Native AOT CLI, NuGet packages, release docs #9

Description

@kkokosa

Packaging and throughput work once the engine is stable.

Deliverables

  • Lanes on CPU: batched independent trials (same checkpoint, different seeds/inputs) sharing the CSR sweep — the 30-trial sugar experiment in < 1 min wall on the 8-core laptop.
  • Native AOT build of dotfly (the CLI currently opts out because of Spectre.Console.Cli reflection); libraries are already IsAotCompatible.
  • NuGet packages for DotFly.Core, DotFly.Data, DotFly.Cpu, DotFly.Engine, DotFly.Adapters.Onnx, DotFly.Adapters.MLNet (MinVer versioning is in place), with a release workflow.
  • Docs: API reference completeness pass (every public member documented), a "first simulation in 5 minutes" page, published with each release.

Acceptance: dotnet add package DotFly.Engine works; dotfly runs as a single native executable; the sugar experiment target above is met.

Context: PLAN.md §11 (F4).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA roadmap feature (PLAN.md §11)performanceBackends, throughput, packaging

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions