# Find the current extraction results and recognise stale output Start with the IXI Results page and current Output Log, then open the associated numerical files through Artifacts. A file left in the output directory may belong to an earlier run. ## Compatibility 8 beta/preview Published guidance with release-applicability limits. Confirm package applicability before following this guide. **KB-GUI-006 · verified workaround**: Save work and close other saved tabs before exit when the intended Studio project must return as active. The checked single-tab restart does not repair multi-tab selection. **KB-GUI-008 · verified workaround**: After a source edit, save the intended inputs, choose Run again and verify the new result. An earlier Completed label may still refer to the previous generation. ## Before starting Use InductEx® 8 with the matching Studio/Core installation. Keep a writable working copy of the complete project and its dependencies. Source-derived steps still require execution review on the intended package. ## Steps 1. Open Results after the run and read completion, final Core stage, elapsed time and warning/error counts. 2. Inspect Raw output and the Output Log. For this GUI route the numerical summary is held in memory; read its headings and units there. Keep missing design values distinct from zero. 3. Use Artifacts to inspect files actually produced by the current run, or open the current solver_out.txt through File > Open. This GUI microstrip run did not produce sol.txt; that filename belongs to other output routes and may be absent or stale. 4. Keep the IXI, dependencies, log, settings, applicable solver artifacts and an explicit record of the current numerical values together. ## Check the result The output belongs to the intended successful run. Failed, cancelled and stale states remain distinct. Read mesh-quality and singular-value information. A result display or a single run does not establish convergence. ## What happens after reopening Studio In the checked candidate, a separate process restored the saved project but did not restore its in-memory run summary. Results was empty while the previous solver files remained on disk. That is not a new failed or successful extraction. Run the intended saved project again for a new GUI result. Identify retained files by their own run record. Opening an old file does not reconstruct a current GUI completion. The restart check used one remaining saved tab because normal multi-tab exit changed the active selection in this candidate. Save your work and close other tabs before exiting when restoring a particular active project matters; final-release behaviour still requires verification. ![Studio Results is empty after a separate-process restart; Raw output and Open output folder are disabled.](https://static.wixstatic.com/media/31de30_f34729837fef47358972f20fef8e204b~mv2.png) A new process has no current in-memory result. Earlier solver artifacts still exist; they are not displayed as a fresh completion. ## If the problem remains If files are absent or ambiguous, inspect the current Output Log and output directory. Retain exact diagnostics, project identity and settings. Do not treat a Results page change or reopening an old file as a new calculation. ## After editing, rerunning or stopping In the checked candidate a saved change from strip_length 100 to 120 left the old Completed label visible until another run. Run again was available. Use it after saving, wait for the new verdict and inspect the values for the intended source. The label alone is insufficient evidence of source/result correspondence (KB-GUI-008). A normal Stop request produced a Cancelled receipt that still contained an L1 row in raw output. Numbers alone therefore do not establish a completed solve. Read Cancelled as the verdict, retain its diagnostic context and run again when the intended inputs are ready. The checked retry completed and reproduced the baseline. A new process restored the corrected saved source and Raw IXI page using the single-tab workaround. Its Results view was initially empty; retained artifacts on disk did not become a new completion. A deliberate rerun then produced the baseline again. ![Current native raw output gives the 100 micrometre strip L1 as 3.89648e-12 H against the 3.9e-12 H design value.](https://static.wixstatic.com/media/31de30_fd644d62c24744dda9ce716d07b93b42~mv2.png) Actual native raw-output L1 table from a completed run. Keep its units, verdict and source identity together. ![The actual native Results status row reads Cancelled following the production Stop action.](https://static.wixstatic.com/media/31de30_a14e4e358d9f4b9499464ed35a9c01a6~mv2.png) The actual Stop result says Cancelled. Its raw output retained a numerical row in this example; that row is not an accepted completed solve. ## Sources and verification details Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate. - VAL-015: InductEx current-source Windows Studio candidate with Core 8.0.1; scenario executable is unversioned. Production GUI controls and normal licensed engine dispatch; current raw result, missing-process correction, GDS PNG export and separate-process restart using a single-tab workaround Bounded native scenario on a frozen source candidate. OS picker input, a clean numerical-results screenshot, mesh refinement, cancellation and final-package acceptance remain unverified. Multi-tab exit selection is held by KB-GUI-006. Computer Use capture remains unresolved. - VAL-023: Frozen Windows Studio source candidate with normal Core 8.0.1 dispatch, 3 November 2026; not a final distributed package. Normal production source edits/Undo/Redo/Save, licensed baseline/length/unit runs, port failure and correction, Stop/retry and a separate-process single-tab restart/rerun. File/directory selection used predetermined paths at the production dialog boundary Eighteen independent checks cover these stated routes. The prior Completed label after a saved source edit remains KB-GUI-008; stale-state acceptance is not passed. A Cancelled receipt retained an L1 row and is not accepted as a completed solve. Physical pickers, complete GUI article, final distributed package, other platforms, physical accuracy and mesh convergence remain pending. KB-GUI-006 single-tab restart workaround remains separate. - studio-empty-results-after-restart: Windows Studio current-source native scenario, 3 November 2026. Illustrates the recorded candidate state. Full GUI article acceptance, numerical refinement and final distributed-package applicability remain pending. - studio-inline-current-inductance: Frozen Windows Studio source candidate, actual native workflow, 3 November 2026. This image shows the stated recorded control/result only. The retained Completed-after-edit observation remains open; a Cancelled receipt is not accepted numerical success. Complete GUI article and final-package checks remain pending. - studio-cancelled-result-status: Frozen Windows Studio source candidate, actual native workflow, 3 November 2026. This image shows the stated recorded control/result only. The retained Completed-after-edit observation remains open; a Cancelled receipt is not accepted numerical success. Complete GUI article and final-package checks remain pending. - inductex:docs/manual/studio_results.tex: Read the run result; Keep a calculation record - inductex:docs/manual/studio_projects.tex: Artifacts and dependencies - validation:studio-native-windows-20261103: VAL-015; current GUI result storage, real licensed extraction/recovery and bounded restart checks - validation:studio-inputs-native-windows-20261103: VAL-023; actual native edits, numerical runs, port recovery, Stop/retry and separate-process single-tab restart; provenance limitation retained - VAL-015 checks current GUI Raw output, a real solver artifact and empty Results after a separate-process restart. It does not qualify cancellation, every artifact route, numerical convergence or the final distributed package. - VAL-023 adds eighteen independent native checks. The saved-source completion label is an open provenance observation (KB-GUI-008); the actual Cancelled verdict is kept distinct from retained numerical rows. Original input bytes were restored. ## Related guides - [My example results differ from numbers in an older manual](/knowledge-base/inductex-example-result-differences) - [Interpret InductEx® process status and printed diagnostic codes](/knowledge-base/inductex-exit-codes) - [Prepare a useful support report without exposing a licence or private design](/knowledge-base/support-effective-report) - [Results still says Completed after I edit an IXI file](/knowledge-base/inductex-completed-after-edit)