{"sections":[{"heading":"Prepare the example","steps":["Copy the complete supplied DFF example inputs to a writable working directory, including the circuit, verification specification and TOML configuration.","Run the saved circuit in JoSIM-Pro first and inspect its diagnostics and outputs.","Make a working copy of the supplied 2.9 DFF configuration named DFF_verify.toml and set its top-level mode to \"verify\". The checked 2.9 review-build example defaults to \"optimize\", which starts a different, potentially long task. Keep the intended circuit/specification references.","Run optimum-cli DFF_verify.toml. The Windows 2.9.0 review-build check printed Verify SUCCESSFUL. Confirm nominal verification before choosing margin, yield or optimize.","Open generated CSV/TSV data or an optimised circuit in the GUI when inspection is needed."]},{"heading":"Check path and solver assumptions","paragraphs":["Relative verify.circuit and verify.file paths are anchored to the TOML file. The circuit's includes follow the simulator's own input rules.","The maintained Optimum manual requires fixed-step PHASE analysis with BDF integration; verification relies on uniformly sampled data. Simulation-backed verification still requires a valid JoSIM-Pro licence and License Manager."]},{"heading":"Verify the actual result","paragraphs":["A configuration inspection is not a completed simulation. VAL-004 retains the earlier DFF nominal verification. The complete resistor-study guides now record separate current-source margin, yield and optimisation checks; those do not establish DFF margins or a full GUI workflow."]},{"heading":"Choose the applicable run route","paragraphs":["The maintained current 2.9 GUI has Run > Optimum studies and typed native study/adoption support. This starting answer retains its checked CLI route. Complete Windows GUI task/cancel/adoption interaction and final-package checks remain separate; the manual still contains a legacy CLI-only handoff paragraph, tracked as KB-DOC-003."]}],"canonical_url":"https://www.sun-magnetics.com/knowledge-base/optimum-first-verification","url":"/knowledge-base/optimum-first-verification","known_issues":[{"disposition":"supported_path","id":"KB-DOC-003","title":"Optimum reference retains conflicting route and tolerance descriptions","public_notice":"Use the guide's explicitly checked CLI or typed-API route and quantity-specific acceptance controls. The bounded resistor reference does not qualify every verification method or native GUI route.","claim_scope":"Only the affected claim and recorded build/input; not whole-guide or final-release acceptance"}],"search_record":{"execution":true,"relatedProducts":[],"version_tags":["JoSIM-Pro 2.9 target"],"text":"Start Optimum with a verified nominal circuit Use the CLI for verification and margin analysis, then inspect generated results in the GUI. Keep the TOML configuration and referenced inputs together. Optimum 2.9.0 release target; review-build/source evidence Get started first Optimum run default optimize start verify nominal verification Prepare the example Copy the complete supplied DFF example inputs to a writable working directory, including the circuit, verification specification and TOML configuration. Run the saved circuit in JoSIM-Pro first and inspect its diagnostics and outputs. Make a working copy of the supplied 2.9 DFF configuration named DFF_verify.toml and set its top-level mode to \"verify\". The checked 2.9 review-build example defaults to \"optimize\", which starts a different, potentially long task. Keep the intended circuit/specification references. Run optimum-cli DFF_verify.toml. The Windows 2.9.0 review-build check printed Verify SUCCESSFUL. Confirm nominal verification before choosing margin, yield or optimize. Open generated CSV/TSV data or an optimised circuit in the GUI when inspection is needed.  Check path and solver assumptions Relative verify.circuit and verify.file paths are anchored to the TOML file. The circuit's includes follow the simulator's own input rules. The maintained Optimum manual requires fixed-step PHASE analysis with BDF integration; verification relies on uniformly sampled data. Simulation-backed verification still requires a valid JoSIM-Pro licence and License Manager.  Verify the actual result A configuration inspection is not a completed simulation. VAL-004 retains the earlier DFF nominal verification. The complete resistor-study guides now record separate current-source margin, yield and optimisation checks; those do not establish DFF margins or a full GUI workflow.  Choose the applicable run route The maintained current 2.9 GUI has Run > Optimum studies and typed native study/adoption support. This starting answer retains its checked CLI route. Complete Windows GUI task/cancel/adoption interaction and final-package checks remain separate; the manual still contains a legacy CLI-only handoff paragraph, tracked as KB-DOC-003. ","id":"optimum-first-verification","keywords":"first Optimum run default optimize start verify nominal verification","kind":"Get started","title":"Start Optimum with a verified nominal circuit","product":"Optimum"},"version":"2.9.0 release target; review-build/source evidence","id":"optimum-first-verification","related":["/knowledge-base/optimum-margin-criteria","/knowledge-base/josim-first-jtl","/knowledge-base/josim-missing-include","/knowledge-base/optimum-margin-workflow","/knowledge-base/optimum-yield-workflow","/knowledge-base/optimum-optimize-workflow","/knowledge-base/optimum-agent-receipts"],"downloads":[],"publication_status":"published","numerical_output":null,"provenance":{"execution_checks":[{"scope":"Nominal CLI verification only","result":"passed","articles":["optimum-first-verification"],"version":"Optimum from JoSIM-Pro 2.9.0 Windows review build; release target","id":"VAL-004","records":["optimum-dff-verify"],"limit":"Nominal verification checked on the 2.9 review build. Margin/yield/optimisation and final release-package checks remain pending.","observed":{"message":"Verify SUCCESSFUL","working_copy_mode":"verify"}}],"figure_evidence":[],"review_notes":["Support history informed this draft. Current-source guidance has been checked; a fresh walkthrough on the intended distributed release and product-owner review remain pending.","Maintained source now also documents Run > Optimum Verify... through the native API. This article retains the CLI starting path; GUI Verify and its final-package availability require separate review and execution.","The changed Optimum source was reviewed individually on 3 November. Its current GUI introduction and legacy handoff paragraph conflict; the CLI scope and pending GUI checks remain explicit."],"scope":"Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.","verification_requirements":{"gui_method":"not-required-for-this-answer","status":"review-incomplete","illustrations":"not-required-for-this-answer","required":["technical-review","release-applicability","execution","numerical-interpretation"],"legacy_walkthrough_field":"pending retained; not evidence of a complete scenario"},"sources":[{"id":"support:SUP-018","section":"Generalised editorial finding; outcome qualification retained"},{"id":"josim-pro:docs/manual_source/sections/optimum.tex","section":"First workflow; installed DFF example; input resolution; simulation contract"},{"id":"validation:windows-cli-20261102","section":"VAL-004; scope and limits recorded"},{"id":"owner:technical-review-20261102","section":"JoSIM-Pro 2.9 chosen as the public starting path; release availability must be checked before publication"}]},"title":"Start Optimum™ with a verified nominal circuit","type":"Get started","markdown_url":"/_functions/kbResource?path=markdown%2Foptimum-first-verification.md","summary":"Use the CLI for verification and margin analysis, then inspect generated results in the GUI. Keep the TOML configuration and referenced inputs together.","product":"Optimum"}