cuopt-server-common
cuOpt REST server — what it does and how requests flow. Domain concepts; no deploy or client code.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- cuopt-server-common
- license
- Apache-2.0
- version
- 26.08.00
- metadata
- { "tags": [ "cuopt", "server", "rest-api", "concepts" ], "author": "NVIDIA cuOpt Team" }
- description
- cuOpt REST server — what it does and how requests flow. Domain concepts; no deploy or client code.
02 资源文件 4
- 参考文档BENCHMARK.md4.0 KB
- 参考文档evals/evals.json943 B
- 参考文档skill-card.md3.5 KB
- 其他skill.oms.sig4.5 KB
03 SKILL.md 正文
cuOpt Server (common)
Domain concepts for the cuOpt REST server. No deploy commands or client code here.
What the server does
- Accepts optimization requests (routing, LP, MILP) over HTTP.
- Returns a request ID; solution is obtained by polling with that ID.
- Does not support QP via REST.
Problem types supported
| Problem type | Supported |
|---|---|
| Routing | ✓ |
| LP | ✓ |
| MILP | ✓ |
| QP | ✗ |
Request flow (conceptual)
- Client sends problem data in the required schema (matrices, tasks, fleet, solver config).
- Server returns a
reqId. - Client polls the solution endpoint with
reqIduntil the job completes. - Response contains status and, on success, solution (routes, objective, primal values, etc.).
Required questions (deployment and usage)
Ask these if not already clear:
- Problem type — Routing or LP/MILP? (QP not available.)
- Deployment — Local, Docker, Kubernetes, or cloud?
- Client — Which language or tool will call the API (e.g. Python, curl, another service)?
Key endpoints (conceptual)
- Health check.
- Submit request (POST).
- Get solution by request ID (GET).
- OpenAPI spec (e.g. for payload format).
04 同仓库更多 Skills
vss-summarize-video
Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.
vss-setup-video-analytics-api
Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.
vss-setup-behavior-analytics
Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.
vss-search-archive
Use this skill to run top-level VSS fusion search on archived video, or to ingest video files / RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).
vss-query-analytics
Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.
vss-manage-video-io-storage
Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add/delete sensors and streams). Not for VLM inference or search.