agentleFS
open-edge-platformopen-edge-platform/geti/skills/getitune/getitune-running-inference/SKILL.md

getitune-running-inference

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

Run inference and evaluation with a getitune model (the Geti training library). Use when a user wants to call `engine.predict()` / `engine.test()` or `getitune predict` / `getitune test`, run inference with a PyTorch checkpoint versus an exported OpenVINO IR (`.xml`) or ONNX (`.onnx`) model, or understand how `OVEngine` loads deployed models via ModelAPI. Covers PyTorch, OpenVINO, and ONNX inference backends.

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

2 rules. About 0 are common, 0 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    Run everything from libraries/getitune/.

    line 13
  2. Very specific:

    Pick the model surface: Use a model name/checkpoint for PyTorch inference, or an exported .xml/.onnx for deployed inference.

    line 49

≈ “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

Running inference with getitune

getitune runs inference through engine.predict() (per-item predictions) and engine.test() (metrics on the test subset). The same calls work whether the engine holds a PyTorch model or an exported OpenVINO/ONNX model — the backend is selected from what you pass to model=.

Run everything from libraries/getitune/.

PyTorch inference (trained model)

from getitune.engine import create_engine

engine = create_engine(
    model="efficientnet_b0",
    data="/path/to/dataset",
)
test_metrics = engine.test()      # metrics on the test subset
predictions = engine.predict()    # predictions on the test subset

OpenVINO / ONNX inference (exported model)

from getitune.engine import create_engine

# OpenVINO IR — pass the .xml
ov_engine = create_engine(model="/path/to/exported_model.xml", data="/path/to/dataset")
ov_engine.test()
ov_engine.predict()

# ONNX — pass the .onnx
onnx_engine = create_engine(model="/path/to/exported_model.onnx", data="/path/to/dataset")
onnx_engine.test()
onnx_engine.predict()

Passing an .xml or .onnx path builds an OVEngine, which loads the model via ModelAPI.

Workflow

  1. Pick the model surface. Use a model name/checkpoint for PyTorch inference, or an exported .xml/.onnx for deployed inference.
    • Done when: create_engine(...) returns the expected engine type.
  2. Point data= at a dataset with a test subset (see getitune-preparing-datasets).
    • Done when: engine.test() runs without a data/format error.
  3. Run test() for metrics or predict() for per-item outputs.
    • Done when: metrics are produced, or predictions are returned for each item.
  4. Compare backends when validating an export. PyTorch vs OpenVINO/ONNX metrics should closely match (small numeric drift is expected).
    • Done when: exported-model metrics are within tolerance of the PyTorch model.

CLI

# from libraries/getitune/
getitune predict --data_root /path/to/dataset --model efficientnet_b0
getitune test    --data_root /path/to/dataset --model /path/to/exported_model.xml

Related skills

  • getitune-exporting-a-model — produce the .xml/.onnx used here.
  • getitune-optimizing-a-model — run inference with an INT8 quantized model.
  • getitune-preparing-datasets — the data= half of inference.

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.