Skip to content

feat: add sustained scenario labels#79

Merged
hyeokjun32 merged 1 commit into
mainfrom
feat/sustained-scenario-labels
May 21, 2026
Merged

feat: add sustained scenario labels#79
hyeokjun32 merged 1 commit into
mainfrom
feat/sustained-scenario-labels

Conversation

@hyeokjun32
Copy link
Copy Markdown
Contributor

Summary

  • Added human-readable scenario identity fields to sustained Orchestrator reports.
  • Preserved the existing scenario_mode contract while adding scenario_label, scenario_category, and scenario_description.
  • Documented labels for normal, overload, sustained_high_load, and device_local modes.

Validation

  • PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest tests/test_multi_workload_sustained.py -q -p no:cacheprovider
  • PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest tests/test_config.py -q -p no:cacheprovider
  • PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src .venv/bin/python -m inferedge_orchestrator run-multi-workload-sustained --config configs/agent_multi_workload_sustained_local.json --output /tmp/orchestrator_scenario_label_test.json --frames 8
  • PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src .venv/bin/python -m inferedge_orchestrator run-multi-workload-sustained --config configs/agent_multi_workload_sustained_device_local.json --output /tmp/orchestrator_scenario_label_device_test.json --frames 8
  • PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest -q -p no:cacheprovider
  • git diff --check

Notes

  • This is a backward-compatible metadata addition for run registry readability.
  • It does not change scheduling behavior, queue policy, or source evidence contracts.

@hyeokjun32 hyeokjun32 merged commit a34ce26 into main May 21, 2026
1 check passed
@hyeokjun32 hyeokjun32 deleted the feat/sustained-scenario-labels branch May 21, 2026 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant