2.9.0 release target; source-documentation evidence
Package applicability is under review; follow the stated version and platform limits.
Before starting
Use the intended 2.9 release and its matching manual. These steps are derived from maintained source documentation; availability in the final distributed package must be checked.
Steps
- Confirm the intended executable/version and working licence before running a copied example.
- Keep .include and other model dependencies with the circuit, then run the command from its working folder.
- Use -o results.csv for an explicit CSV destination. Without an output target, documented routing is .FILE or STDOUT; a bare -o selects out.csv.
- Inspect runtime diagnostics, output columns, expected traces and time coverage. Do not choose an input/include/model file as a destination.
Documented example
josim-pro-cli -v
josim-pro-cli -o results.csv JTL_Example.cirCheck the result
The output belongs to the current intended run and contains the requested traces. Record units, sample/time coverage and completion state.
The documented default is PHASE+BDF with variable-step off; deliberate overrides and netlist options must be recorded for reproducibility.
If the problem remains
For a launch failure check the actual executable path. For missing includes, repair the dependency path before retrying. For a rejected output alias, choose a new destination.
Choose the analysis-specific result type
The worked array/output example here is transient and uses seconds. OP results are scalars, DC uses its swept source values and volts or amperes as the horizontal axis, and AC retains complex values against frequency in hertz. Use the dedicated static/DC and AC guides for those output contracts. Match values to their declared axis metadata before processing or plotting them.
Sources and verification details
Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.
VAL-012 · JoSIM®-Pro 2.9.0 Windows review runtime; CPython 3.13.11 and NumPy 2.5.4 in an isolated environment
Packaged JTL through Python Input/Matrix/Simulation, raw and named arrays, formatted output axis and CSV writer; the same current CLI produced exactly matching parsed CSV
Execution, finite data, shape/time coverage and same-engine interface agreement. No independent physical reference, convergence, GUI, other interpreter/platform or final-release qualification.
- josim-pro:docs/manual_source/sections/usage.tex · Command structure; Default behavior; Quick command patterns
- owner:technical-review-20261102 · Owner selected 2.9 as the publication target; final package checks remain required
- validation:windows-workflows-20261103 · VAL-011/VAL-012; exact route, runtime and evidence limits
- josim-pro:docs/manual_source/sections/syntax.tex · Static operating point, Circuit DC sweeps and Small-signal AC result/axis contracts; separate from the transient recipe
- VAL-012 ran the packaged JTL through the current CLI and compared its parsed CSV with the Python output. This is bounded execution evidence, not a GUI or numerical-accuracy acceptance.