ReferenceVersion 0.4.1
Troubleshoot BioSTEAM / QSDsan MCP
Resolve runtime, convergence, TEA, impact-factor, async-job, and recovery problems.
The server fails to import
Run health_check from the same Python environment used by the MCP client. Confirm that BioSTEAM, ThermoSTEAM, QSDsan, and the server package are installed there.
The process does not converge
Treat convergence as a process-model problem first. Review the thermodynamic package, stream specifications, recycle loops, unit parameters, and operating conditions before running uncertainty or optimization.
TEA or foreground impact results look wrong
- For TEA, check scale, capacity, equipment sizing, operating hours, product stream, cost basis, and financial assumptions.
- For foreground impacts, check characterization-factor units, flow basis, operating hours, geography, temporal basis, and whether the intended background impacts are represented.
A long uncertainty or optimization run times out
Use run_uncertainty_async or optimize_async and poll the returned job_id.
A recovered result is refused after restart
Version 0.4.1 checks the persisted runtime fingerprint before rebuilding a process handle. If the BioSTEAM, ThermoSTEAM, or QSDsan versions changed, rebuild the study under the new environment instead of forcing recovery.