# Plot and export S-Parameter traces from Studio Use the S-Parameters view for the intended response, select traces and a frequency band, then export PNG for a figure or CSV for complex numerical samples. ## Compatibility 8 beta/preview Published guidance with release-applicability limits. Confirm package applicability before following this guide. ## Before starting Use InductEx® 8 with a matching Studio/Core runtime and a complete writable calculation. The current-source Windows sampled-response route has scoped native checks; the final distributed package and physical export dialogs remain pending. ## Steps 1. Open the S-Parameters response associated with the intended successful run, or deliberately open the intended response JSON. 2. Read whether the response is a rational model or sampled data. Select the traces and visible frequency band needed for the comparison. 3. Use Export PNG for the visible chart and legend, or Export CSV for the selected traces over the visible band. 4. Record the response source, frequency band and selected traces beside the exported file. ![Studio S11 magnitude in dB against GHz after a thirteen-frequency extraction, with the sampled-response status.](https://static.wixstatic.com/media/31de30_5c5175cee9b54f86a645fdfd434dc156~mv2.png) The actual native sampled-response view exposes trace selection, display quantity, CSV and PNG export. The numerical writer and chart controls were checked separately from physical Save-dialog input. ## Check the result CSV columns are trace,f_Hz,re,im,valid. Frequency is in Hz and the real/imaginary parts are exported directly. Sampled responses use solved points and complex interpolation. Zooming or increasing plot density cannot recover an unsolved narrow feature. Adaptive traces may have different frequency grids. ## Keep display and numerical data separate The native CSV writer preserved the current Core complex values in four- and thirteen-point S11 results and the corrected 2:1/S21 selection. Selecting linear magnitude instead of dB left CSV bytes unchanged. PNG exports produced valid native chart images. A zoomed sampled export can include interpolated boundary coordinates. In the checked view, eleven interior points plus two interpolated boundaries still produced thirteen rows; Reset restored the original CSV bytes. The underlying Core result stayed unchanged. Read the solved-data provenance rather than inferring new solves from row count. For a complete worked frequency-grid example, use the related refinement guide. Direct native writer calls do not establish physical Save, invalid-destination retry or Cancel behaviour. ## If the problem remains If no appropriate response is loaded, check successful-run association and open the intended JSON explicitly. Do not use an old or ambiguous model as a new extraction result. An Invalid trace S99 diagnostic on a two-port response is corrected by selecting S11, S21 or 2:1 and Apply traces. The checked correction exported S21; the previous curve can remain visible while the selector is invalid. ![Studio rejects S99 with an inline invalid-trace diagnostic and suggests S21 or 2:1 while retaining the previous plot.](https://static.wixstatic.com/media/31de30_c1180b4fb95649f3a50a76497c632c53~mv2.png) An invalid trace leaves an inline diagnostic and the previous curve; correct the selector before accepting the intended export. ## Sources and verification details Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate. - VAL-033: Frozen unversioned Windows Studio candidate with Core 8.0.1 and TTH 1.1.50. Frozen Windows Studio/Core candidate: normal licensed 4/13-point EMQS runs, saved source edit with Undo/Redo, native sampled JSON open, S11/2:1 selectors, invalid-trace recovery, display quantity, zoom/reset and direct native CSV/PNG writers. Physical pickers, Save/cancel/retry and final package remain unqualified This teaching line does not establish physical calibration or universal mesh/frequency/fit convergence. Native export writers were called directly; physical Save dialogs, retry/cancel, other platforms and final packages remain pending. - studio-sparameter-refined: Windows Studio current-source native scenario, 3 November 2026. Illustrates the recorded sampled teaching line. No rational-fit accuracy, physical calibration, complete GUI article or final-package qualification. - studio-sparameter-invalid-trace: Windows Studio current-source native scenario, 3 November 2026. Illustrates the recorded sampled teaching line. No rational-fit accuracy, physical calibration, complete GUI article or final-package qualification. - inductex:docs/manual/studio_results.tex: S-Parameter plots - validation:sparameter-frequency-windows-20261103: VAL-033; actual sampled-response native opens, trace control/recovery, zoom/reset and direct CSV/PNG writer checks - Nineteen independent native checks on the recorded current-source Windows candidate. Normal licensed runs supply current Core sampled data; physical export-dialog, rational-model and final-package checks remain pending. ## Related guides - [Find the current extraction results and recognise stale output](/knowledge-base/inductex-read-results) - [Check mesh convergence when a run is slow or results change](/knowledge-base/inductex-mesh-convergence) - [Refine S-Parameter frequencies and distinguish solved data from plot detail](/knowledge-base/inductex-frequency-refinement) - [Hand off an already fitted line model from external network data](/knowledge-base/sparameter-model-handoff)