{"sections":[{"heading":"Check the complete verdict","paragraphs":["A zero process exit or finite current file is insufficient when the solver reports conflicting status. Retain the current log, settings, mesh and output together. Check the actual executable/version and make sure the files were generated by this run. Do not relabel a failed summary as success or discard the current sign to make a comparison look correct.","In the reproduced GMRES case, TTH says Solved while the reported relative error is near one. Treat that combination as a conflicting diagnostic result; the finite source current alone does not resolve it."]},{"heading":"Recognise the bounded 1.1.50 reproduction","table":{"columns":["Method","Observed on the supplied DC conductor"],"rows":[["DIRECT","Exit 0 and a finite approximately -5 A source-current row, but the console says CONVERGENCE FAILED."],["GMRES","Exit 0 and a finite approximately -5 A row, with console Solved but a reported relative-error real component close to 1 despite the requested 10^-9 limits."],["FGMRES","A separate generation reports Solved with finite small error and agrees with the independent 0.2-ohm conductor reference."]],"wrap":true}},{"heading":"Use the checked recovery with its limits","paragraphs":["KB-TTH-001 records this observation on the exact Windows TTH 1.1.50 bundled with the recorded InductEx 8.0.1 payload. Its root cause is not established because the maintained TTH implementation is not available in this review. The result does not establish that every DIRECT or GMRES calculation is wrong, nor that a matching finite current overrides a failure.","For the supplied teaching project, restore the bar.json FGMRES settings from the related guide and choose a new result directory. The provided client rejects both conflicting routes and retains failed receipts/logs. The FGMRES route also passes independent current, source-scaling, length and simple refinement checks. For another model, keep its own numerical and physical validation requirements; do not substitute a general solver-method recommendation for evidence.","The separate EQS convergence-summary issue KB-EQS-001 remains under its numerical-presentation hold. This MQS/DC reproduction neither resolves nor broadens that held EQS result."]},{"heading":"Collect evidence for a support investigation","steps":["Record the exact TTH executable/version, platform and solver settings. Keep a complete nonconfidential reproducer rather than only a screenshot of the last line.","Retain the process exit, full current-generation solver log and named numerical files. Compare status and reported errors before deciding what can be accepted.","When a small model has an independent analytical reference, include the equation, dimensions, units and signed comparison. Separate numerical agreement from the conflicting diagnostic output.","Review all files before sending them privately to support. The supplied teaching download is safe to start from; generated runtime settings/logs can contain local and licence-status information."]}],"canonical_url":"https://www.sun-magnetics.com/knowledge-base/tetrahenry-conflicting-status","url":"/knowledge-base/tetrahenry-conflicting-status","known_issues":[{"disposition":"hold","id":"KB-EQS-001","title":"EQS run prints unusable GMRES summary values","public_notice":"Parallel-plate numerical reference values and convergence-summary statistics remain withheld. Setup guidance is available; no accepted numerical success criterion is presented until reporting and convergence are reviewed.","claim_scope":"Only the affected claim and recorded build/input; not whole-guide or final-release acceptance"},{"disposition":"verified_workaround","id":"KB-TTH-001","title":"conflicting DC solver summaries on the bundled TTH 1.1.50","public_notice":"Use the checked FGMRES route for this complete DC teaching input and require diagnostics plus the independent reference. Reject the conflicting DIRECT/GMRES summaries; this is not a universal solver-method recommendation.","claim_scope":"Only the affected claim and recorded build/input; not whole-guide or final-release acceptance"}],"search_record":{"execution":true,"relatedProducts":["InductEx"],"version_tags":["TetraHenry 1.1.40 manual","InductEx 8 preview"],"text":"TetraHenry writes a result but reports conflicting convergence status Check the process verdict, current-generation output, diagnostic fields and an independent reference together. Conflicting DIRECT/GMRES summaries are tracked on one TTH 1.1.50 DC example. TetraHenry TTH 1.1.50 bundled with Windows InductEx 8.0.1; manual 1.1.40 used as a bounded reference Troubleshooting KB-TTH-001 CONVERGENCE FAILED TTH Solved error DIRECT GMRES FGMRES exit zero finite current conflicting summary Check the complete verdict A zero process exit or finite current file is insufficient when the solver reports conflicting status. Retain the current log, settings, mesh and output together. Check the actual executable/version and make sure the files were generated by this run. Do not relabel a failed summary as success or discard the current sign to make a comparison look correct. In the reproduced GMRES case, TTH says Solved while the reported relative error is near one. Treat that combination as a conflicting diagnostic result; the finite source current alone does not resolve it.  Recognise the bounded 1.1.50 reproduction  Method Observed on the supplied DC conductor DIRECT Exit 0 and a finite approximately -5 A source-current row, but the console says CONVERGENCE FAILED. GMRES Exit 0 and a finite approximately -5 A row, with console Solved but a reported relative-error real component close to 1 despite the requested 10^-9 limits. FGMRES A separate generation reports Solved with finite small error and agrees with the independent 0.2-ohm conductor reference. Use the checked recovery with its limits KB-TTH-001 records this observation on the exact Windows TTH 1.1.50 bundled with the recorded InductEx 8.0.1 payload. Its root cause is not established because the maintained TTH implementation is not available in this review. The result does not establish that every DIRECT or GMRES calculation is wrong, nor that a matching finite current overrides a failure. For the supplied teaching project, restore the bar.json FGMRES settings from the related guide and choose a new result directory. The provided client rejects both conflicting routes and retains failed receipts/logs. The FGMRES route also passes independent current, source-scaling, length and simple refinement checks. For another model, keep its own numerical and physical validation requirements; do not substitute a general solver-method recommendation for evidence. The separate EQS convergence-summary issue KB-EQS-001 remains under its numerical-presentation hold. This MQS/DC reproduction neither resolves nor broadens that held EQS result.  Collect evidence for a support investigation Record the exact TTH executable/version, platform and solver settings. Keep a complete nonconfidential reproducer rather than only a screenshot of the last line. Retain the process exit, full current-generation solver log and named numerical files. Compare status and reported errors before deciding what can be accepted. When a small model has an independent analytical reference, include the equation, dimensions, units and signed comparison. Separate numerical agreement from the conflicting diagnostic output. Review all files before sending them privately to support. The supplied teaching download is safe to start from; generated runtime settings/logs can contain local and licence-status information. ","id":"tetrahenry-conflicting-status","keywords":"KB-TTH-001 CONVERGENCE FAILED TTH Solved error DIRECT GMRES FGMRES exit zero finite current conflicting summary","kind":"Troubleshooting","title":"TetraHenry writes a result but reports conflicting convergence status","product":"TetraHenry"},"version":"TTH 1.1.50 bundled with Windows InductEx 8.0.1; manual 1.1.40 used as a bounded reference","id":"tetrahenry-conflicting-status","related":["/knowledge-base/tetrahenry-complete-run","/knowledge-base/support-effective-report"],"downloads":[],"publication_status":"published","numerical_output":null,"provenance":{"execution_checks":[{"routes":["python-cli"],"scope":"31 Windows checks on the InductEx 8.0.1 catalog-bundled TTH 1.1.50: complete hand-written modified FastHenry/JSON MQS/DC conductor, independent bulk-resistance/voltage/length/refinement comparisons, separate generations, paths, real failures/recovery and conflicting DIRECT/GMRES summaries. No standalone installer, GUI, other-platform or general physical/convergence qualification","result":"passed","articles":["tetrahenry-complete-run","tetrahenry-conflicting-status"],"purpose":"standalone-tth-mqs-dc-reference-and-recovery","version":"Windows InductEx 8.0.1 catalog-bundled TTH 1.1.50 / CPython 3.13.11","id":"VAL-036","records":["31 independent execution/artifact/identity checks","Three complete teaching files preserved","Actual solver failures and corrected new generations","Issued licence unchanged and never copied","Eight real browser-download checks pass using the exact article/README PowerShell command"],"limit":"The 1.1.40 manual describes the input vocabulary used here; it is not asserted to be the exact manual for 1.1.50. Maintained TTH source authority and final package/platform acceptance remain open. KB-EQS-001 remains unchanged.","observed":{"refined_source_current_A":[-4.9999999983,0],"double_length_current_A":[-2.499999999,0],"summary_conflicts":{"DIRECT":{"solver_exit":0,"runner_exit":1,"receipt_status":"failed","reported_error_real":0,"failed_summary":true,"solved_summary":false,"source_current_real_A":-4.9999999983},"GMRES":{"solver_exit":0,"runner_exit":1,"receipt_status":"failed","reported_error_real":0.999999999,"failed_summary":false,"solved_summary":true,"source_current_real_A":-4.9999999983}},"reference_resistance_ohm":0.2,"solver_version":"1.1.50","source_current_A":[-4.9999999983,0],"half_voltage_current_A":[-2.4999999991,0]}}],"figure_evidence":[],"review_notes":["The checked executable matches the preserved read-only MSI cabinet member and the recorded archive identity. This is standalone invocation of that bundled runtime, not qualification of a separate TTH installer.","The older manual is a source for the explicitly used format vocabulary. Exact maintained TTH source/manual authority, remaining modes and final package/platform qualification are still open."],"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","recovery","numerical-interpretation"],"legacy_walkthrough_field":"pending retained; no complete article or release acceptance"},"sources":[{"id":"published:tth-manual-1.1.40","section":"Sections 1.2.2–1.7, 1.11.1 and 1.12: modified FastHenry, JSON materials/terminals, output and MQS/DC settings; older reference, not exact 1.1.50 pairing"},{"id":"validation:tth-standalone-windows-20261104","section":"VAL-036; normal standalone 1.1.50 invocation, observed output contract, controlled variations and failure/recovery"}]},"title":"TetraHenry® writes a result but reports conflicting convergence status","type":"Troubleshooting","markdown_url":"/_functions/kbResource?path=markdown%2Ftetrahenry-conflicting-status.md","summary":"Check the process verdict, current-generation output, diagnostic fields and an independent reference together. Conflicting DIRECT/GMRES summaries are tracked on one TTH 1.1.50 DC example.","product":"TetraHenry"}