agentleFS
open-edge-platformopen-edge-platform/geti/skills/getitune/getitune-exporting-a-model/SKILL.md

getitune-exporting-a-model

Skill1.4k starsChanged 17 days agoApache-2.0View on GitHub

Export a trained getitune model (the Geti training library) to a deployable format. Use when a user wants to run `engine.export(...)` or `getitune export`, choose between OpenVINO IR and ONNX, set FP32 vs FP16 precision with `ExportFormat` / `Precision`, or understand where exported artifacts are written and how they load back for inference. Covers the export/load contract between training and OpenVINO/ONNX inference.

2 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about open-edge-platform/geti

The biggest 5 of 24 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 24

Talked about on GitHub, Hacker News and Bluesky (24 times).

On GitHub · 21

16 more on GitHub

On Hacker News · 2

On Bluesky · 1

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After training, export a model to a deployable format with engine.export(...) (Python API) or getitune export (CLI).

    line 8
  2. Very specific:

    Run everything from libraries/getitune/.

    line 14
  3. Very specific:

    Choose format and precision: Default is FP32 OpenVINO IR.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Exporting a model with getitune

After training, export a model to a deployable format with engine.export(...) (Python API) or getitune export (CLI). getitune exports to OpenVINO IR (default) or ONNX, each at FP32 (default) or FP16 precision. Exported artifacts load back for inference via the OpenVINO/ONNX path (see the getitune-running-inference skill).

Run everything from libraries/getitune/.

Python API workflow

from getitune.engine import create_engine
from getitune.types import ExportFormat, Precision

engine = create_engine(
    model="efficientnet_b0",
    data="/path/to/dataset",
    work_dir="./my_workspace",
)
engine.train(max_epochs=50)

# FP32 OpenVINO IR (default) -> returns the .xml path
ov_ir_path = engine.export()

# FP32 ONNX
onnx_path = engine.export(export_format=ExportFormat.ONNX)

# FP16 ONNX (same pattern works for OpenVINO IR)
onnx_fp16 = engine.export(export_format=ExportFormat.ONNX, export_precision=Precision.FP16)
  1. Train or load a model into the engine first (export operates on the engine's current model).
    • Done when: engine.test() produces sensible metrics before you export.
  2. Choose format and precision. Default is FP32 OpenVINO IR. Use export_format=ExportFormat.ONNX for ONNX; export_precision=Precision.FP16 to halve size for supported hardware. Both enums live in getitune.types.
    • Done when: engine.export(...) returns a path to the written artifact.
  3. Confirm the artifact exists under work_dir (.xml + .bin for OpenVINO IR, .onnx for ONNX).
    • Done when: the returned path exists on disk.
  4. Validate parity by loading the exported model back and running engine.test() — accuracy should closely match the trained model (small FP16 drift is expected). See getitune-running-inference.
    • Done when: exported-model metrics are within tolerance of the trained model.

CLI workflow

# from libraries/getitune/
getitune export --data_root /path/to/dataset --model efficientnet_b0
# use --help -v for export-format / precision flags

Export/load contract

  • Each model implements forward_for_tracing(...) under libraries/getitune/src/getitune/backend/lightning/models/<task>/; that is what defines the exported graph. If you change model I/O, keep this method in sync or export parity breaks.
  • Exported OpenVINO IR / ONNX models are loaded for inference through the OpenVINO backend (OVEngine) using ModelAPI.
  • Each task also ships an openvino_model.yaml recipe for loading a pre-exported IR model directly.

Verify

# from libraries/getitune/
just lint
just test-unit -- -k export        # when you touched export/tracing code

Related skills

  • getitune-training-a-model — produce the checkpoint to export.
  • getitune-running-inference — load and validate the exported model.
  • getitune-optimizing-a-model — quantize an exported OpenVINO model to INT8.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.