w1n5t0n/memlnaut-nisps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
memlnaut-nisps/codegen/package.json

20 lines
475 B
JSON
Raw Normal View History

Add codegen tool: schemas -> C++ headers + TS modules bun-runnable TypeScript script (codegen/generate.ts) that: - Validates each schemas/modes/*.json against the meta-schema via ajv (Draft 2020-12). - Cross-checks params.length == ml.output_size and ml.input_channels.length == ml.input_size. - Emits constexpr C++ data into nisps/modes/generated/ (one schema_types.hpp + one <mode_id>_schema.hpp per mode). Uses std::string_view + std::array; no std::vector, no heap, .f suffixed float literals (perf contract §3.3). - Emits TS modules into playground/src/modes/generated/ (one types.ts + one <mode_id>_schema.ts + index.ts barrel). - Idempotent: re-running yields byte-identical output. - Exits non-zero on schema validation failure. Reference templates live in codegen/templates/ (not consumed at codegen time -- for human reviewers). Golden test (codegen/tests/golden_test.ts) snapshots paf_synth_schema.{hpp,ts} and verifies regeneration matches the golden + that a second run is idempotent. Until stream 1 lands nisps/core/math.hpp, schema_types.hpp ships its own minimal Curve enum with a TODO marker pointing at the eventual include.
2026-04-29 14:29:08 +02:00
{
"name": "memlnaut-codegen",
"version": "0.1.0",
"private": true,
"description": "Codegen for MEMLNaut mode schemas (JSON -> C++ + TypeScript).",
"type": "module",
"scripts": {
"generate": "bun run generate.ts",
feat: curve truth, DriverConfig, real telemetry, engine benchmark Four items from one workflow, committed together because their build and CI wiring genuinely interleaves — nisps/CMakeLists.txt, run-all-tests.sh and ci.yml each carry hunks from two of them, and the stage renumbering (1/5 -> 1/6) touches every line. Splitting would produce commits that do not build, which is worse than a commit that does four things and says so. S26 part 2 — the curve declaration now matches reality. params[].curve stays the mode-wide DEFAULT; a voice_spaces entry may now be {name, curve_overrides} declaring only the slots where THAT voice space deviates. The 6 modes with one voice space are byte-identical. The values were derived MECHANICALLY by a new codegen/curve-audit.ts that models the four idioms a p[N]*p[N] regex misses (alias form, memlcelium's implicit-counter sq() lambda, loop-generated indices, smooth_params_), inlines helpers, and RAISES rather than guessing when it cannot reduce an expression. A drift gate cross-checks 1179 (voice space x param) slots against engine source on every run and was proved to fail loudly on three drift classes. Application stays in the engine: nisps/engines, nisps/pipeline and nisps/core are untouched, generated output is pure insertion (755 insertions, 0 deletions), and the rebuilt nisps.wasm was byte-identical. S4 / 7.2 — firmware reads the active mode's driver config at mode start, and mic/line is real. My brief assumed the engine owns this; the code disagreed and the code was right. sound_analysis_midi's EngineT is NoOpEngine — the mic lives on a separately-composed AnalysisEngine member — so engine-level wiring would have compiled, passed every gate, and left the one mic mode on line input. Hence a mode-level seam defaulting to engine().driver_config(). Separately, DriverConfig's defaults (line_level 0, output_volume 1.0) had drifted from memllib's actual 3/0.8 because nothing had ever read them; wiring them as-is would have made every silent mode louder and its line input maximally insensitive — a behaviour change disguised as plumbing. Now pinned by a test. Also: GetSysClockSpeed() panic()s on unsupported sample rates and runs on the first line of setup(), so sample_rate needed a fallback ahead of clock setup. CI's firmware env list gains soundanalysismidi — it is the only mic variant and nothing else compiles that path. Plan 5e — telemetry is real. A loss_history C-API entry across the full 5-layer chain lets the browser read the per-iteration loss the core already records. The audit named one fabrication site; there were two — wasm-iml.ts's synchronous train() published lossHistory: [loss] as well. A third, ctx.loss, was not merely dead but actively synthetic (fallbacks of prev * 0.82 and a literal 0.5, rendered by nothing) and is deleted. The firmware buffer stays untouched, per the L25 call. EngineApi.lossHistory() reads spine state rather than the MLP handle, because trainAsync() fits on the worker's mirror net and the handle would give a subtly-wrong second answer. Plan 5f — engine throughput is measurable. One source compiled twice (CMake natively, emcc for WASM) so the targets compare directly and no WASM export is added. Sequencers are driven into a working state, and every row prints its own working-state evidence so a number produced by an idle engine is visible rather than plausible. Reports, never asserts: a wall-clock threshold on shared hardware is meaningless or flaky, same call as the firmware size job. ALIGNMENT: the telemetry defect is deleted (built, not deferred); the performance defect is rewritten to what is actually left — these are HOST numbers, and nothing measures the RP2350 at 150 MHz, which is the target the mission's constraint is about. Q4 (memllib ownership) and Q5 (legacy feedback modes) are closed. Corrections to my own earlier claims, both found by agents contradicting the brief: manifold/ONBOARDING.md was NOT "now accurate" — its primitives list still named five deleted primitives and cited a seededGradient() that does not exist. And the parity harness misses the sequencer engines because it runs 128 frames while their sequencers evaluate every 400-500 samples, NOT because all-params-0.5 fails to trigger them (it does trigger: 0.5 maps to ratio 2, firing three times per bar). The fix is a longer window, not different params. Gates: run-all-tests.sh ALL GREEN — 4/4 ctest, parity PASS, lint clean, curve drift 1179 slots ok, 39 e2e (was 33). Firmware: 5 envs built including the mic variant.
2026-07-21 22:02:23 +02:00
"test": "bun run tests/golden_test.ts && bun run tests/curve_drift_test.ts"
Add codegen tool: schemas -> C++ headers + TS modules bun-runnable TypeScript script (codegen/generate.ts) that: - Validates each schemas/modes/*.json against the meta-schema via ajv (Draft 2020-12). - Cross-checks params.length == ml.output_size and ml.input_channels.length == ml.input_size. - Emits constexpr C++ data into nisps/modes/generated/ (one schema_types.hpp + one <mode_id>_schema.hpp per mode). Uses std::string_view + std::array; no std::vector, no heap, .f suffixed float literals (perf contract §3.3). - Emits TS modules into playground/src/modes/generated/ (one types.ts + one <mode_id>_schema.ts + index.ts barrel). - Idempotent: re-running yields byte-identical output. - Exits non-zero on schema validation failure. Reference templates live in codegen/templates/ (not consumed at codegen time -- for human reviewers). Golden test (codegen/tests/golden_test.ts) snapshots paf_synth_schema.{hpp,ts} and verifies regeneration matches the golden + that a second run is idempotent. Until stream 1 lands nisps/core/math.hpp, schema_types.hpp ships its own minimal Curve enum with a TODO marker pointing at the eventual include.
2026-04-29 14:29:08 +02:00
},
"dependencies": {
"ajv": "^8.17.1",
"ajv-formats": "^3.0.1"
},
"devDependencies": {
"typescript": "^5.6.3",
"@types/node": "^22.9.0"
}
}
Reference in a new issue Copy permalink