sequence-base 0.4.19__tar.gz → 0.4.20__tar.gz

{sequence_base-0.4.19 → sequence_base-0.4.20}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sequence-base
-Version: 0.4.19
+Version: 0.4.20
 Summary: Shared foundation for the Sequences platform — wire contract, correlation, error taxonomy, constants. Used by the robot SDK, gateway, and container harness.
 Project-URL: Changelog, https://generalsequences.com/docs/changelog/
 Requires-Python: >=3.10

{sequence_base-0.4.19 → sequence_base-0.4.20}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "sequence-base"
-version = "0.4.19"
+version = "0.4.20"
 description = "Shared foundation for the Sequences platform — wire contract, correlation, error taxonomy, constants. Used by the robot SDK, gateway, and container harness."
 requires-python = ">=3.10"
 dependencies = ["pydantic>=2.0"]

sequence_base-0.4.20/sequence_base/constants/cards.py

@@ -0,0 +1,16 @@
+"""The cards a benchmark machine may run on, defined once here: the SDK refuses any other before a benchmark registers
+(and `seq validate` offline, so the list is a constant, not a read), the gateway at registration and at an eval, and
+the harness at the machine it starts - one list where each kept its own.
+
+
+Both cards have RT cores, video encoders, EGL and Vulkan, so a benchmark only picks cheaper or faster; one that names a
+card simulates on it (registration checks). CPU physics is the author's explicit choice, gpu="cpu": CPU machines, one
+environment per core
+.
+"""
+
+BENCHMARK_GPUS = ("L4", "RTX-PRO-6000")
+
+DEFAULT_BENCHMARK_GPU = "L4"
+
+BENCHMARK_CPU = "cpu"

{sequence_base-0.4.19 → sequence_base-0.4.20}/sequence_base/contract/benchmarks.py

@@ -224,6 +224,7 @@ class BenchmarkRegisterRequest(BaseModel):
 
 
 
+
     gpu: str | None = Field(default=None, max_length=32)
 
     envs: int | None = Field(default=None, ge=1, le=MAX_ENVS)

{sequence_base-0.4.19 → sequence_base-0.4.20}/sequence_base/contract/eval.py

@@ -1,6 +1,6 @@
 """
-Contract 5 (run half) — `POST /v1/eval`, its response, and the `GET /v1/eval/{id}` report, plus the adapter
-lossless/lossy classification wire types.
+Contract 5 (run half) — `POST /v1/eval`, its response, and the `GET /v1/eval/{id}` report. (The adapter's
+lossless/lossy classification types went in contract 0.5.12: an adapter is no longer classified.)
 
 Two response shapes, deliberately distinguishable (goal 12): a real run returns eval_id / gpus_granted /
 estimate; `dry_run=true` returns ONLY an estimate — no id to GET, no built-machine artifacts. The report