Skip to main content

geti-runtime-running-live-inference

Run and operate live inference in the Geti application pipeline. Use when a user wants to start, monitor, stop, or recover source -> model -> sink runtime execution, verify production readiness, or troubleshoot live pipeline behavior such as stalls, dropped outputs, and latency regressions.

소스 정보

저장소
open-edge-platform/geti
최근 소스 활동
2026년 8월 25일 09:29
감지된 SKILL.md 언어
영어
스타
1,352
포크
480

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
geti-runtime-running-live-inference
description
Run and operate live inference in the Geti application pipeline. Use when a user wants to start, monitor, stop, or recover source -> model -> sink runtime execution, verify production readiness, or troubleshoot live pipeline behavior such as stalls, dropped outputs, and latency regressions.
# Geti Runtime: Running Live Inference Use this skill for operational control of live inference in Geti. This skill is for runtime execution and monitoring, not code changes. ## When to Use - User asks how to start or stop live inference for a configured pipeline. - User needs runbook-style checks for runtime health and correctness. - User reports stalls, dropped outputs, or latency spikes during live execution. - User needs incident-style recovery steps with minimal disruption. ## Scope - In scope: runtime start and stop flow, status monitoring, health verification, rollback and recovery. - Out of scope: backend implementation changes and model retraining. ## Procedure 1. Pre-flight checks. - Confirm pipeline configuration is complete (source, model, sink). - Confirm model is loaded and selected. - Confirm endpoints for source and sink are reachable. 2. Start live inference. - Enable runtime execution through the application pipeline workflow. - Capture execution identifiers and current status. 3. Monitor execution. - Check the pipeline status (Idle vs Running). - Verify frames are rendered with predictions, inference output is generated as per sink configuration. - Record key runtime metrics if available (throughput & latency). 4. Validate output quality. - Spot-check predictions against known scenes or samples. - Confirm class distribution and confidence values are reasonable. 5. Handle degradation. - If source degrades: reconnect or switch to a known-good source. - If model output degrades: verify loaded model version and thresholds. - If sink fails: apply fallback sink.
GitHub에서 보기