Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.
Python calibrationclassificationdecision-modelhuggingfacejevmodernbertmultilingualnlppythonpytorchroutingtyped-decisionszero-shot
test(ts): stop pinning the port's own [] temperature fallback
Aashishb41c73a71860
diff --git a/laya-ts/tests/temperature-loading.test.ts b/laya-ts/tests/temperature-loading.test.tsindex 3d7b246b..855dedb0 100644--- a/laya-ts/tests/temperature-loading.test.ts+++ b/laya-ts/tests/temperature-loading.test.ts@@ -65,11 +65,10 @@ describe("checkpoint temperature loading", () => {expect(warnings).toHaveLength(1);expect(warnings[0]).toContain("temperature[0]");}- // An empty list is the port's own case, not a divergence to fix here: JS's `Number([])` is 0,- // so `clampTemperature` bounds it to TEMP_MIN where Python's `float([])` raises and falls back- // to 1.0. Either way the entry is named, which is what this loop is about.+ // A list is named too, and only the naming is asserted: `Number([])` is 0 so the port bounds it+ // to TEMP_MIN while Python's `float([])` raises and falls back to 1.0. Which of the two the+ // clamp installs is a separate question from whether the loader says anything about it.const empty = loadWith([[] as any, 2.0, 3.0]);- expect(empty.agent.temperature).toEqual([0.5, 2.0, 3.0]);expect(empty.warnings).toHaveLength(1);expect(empty.warnings[0]).toContain("temperature[0]");});