add operating-point simulation result schema#646
Draft
ShiboSoftwareDev wants to merge 3 commits into
Draft
Conversation
This was referenced Jul 14, 2026
ShiboSoftwareDev
force-pushed
the
agent/operating-point-simulation
branch
from
July 14, 2026 17:58
932e3f0 to
60aa4f6
Compare
This was referenced Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
any_circuit_elementand generated documentationWhy
tscircuit already names
spice_dc_operating_pointas an experiment type, but Circuit JSON had no result representation for the single-point values and no structured way to distinguish convergence failures from generic engine errors.Validation
bun test(261 passed)bun run buildbun run lint:zodbun run check-snake-caseStack and merge order
.opnetlist generation: Generate DC operating-point SPICE analyses circuit-json-to-spice#50