The ANDES server loads cases by file path and ANDES itself reads MATPOWER .m and PSS/E .raw natively, so it gains nothing from the powerio JSON transport for those. The remaining gap is the formats ANDES cannot read: PowerWorld .aux, PowerModels JSON, egret JSON.
With save_case on the powerio server (#28), the workflow already exists without any ANDES change:
save_case(to="matpower", out_path="case.m", path="case.aux")
run_power_flow(file_path="case.m") # ANDES server
Options, in order of effort: (a) document that two-step recipe in the README conversion section (one sentence already landed in #28); (b) add a load_case_from_any(file_path, source_format=None) bridge to ANDES/andes_mcp.py that converts via powerio and stages a .m temp file, like the Egret bridge. Given (a) covers the need, closing this as docs-only is reasonable unless demand appears for (b).
🤖 Generated with Claude Code
The ANDES server loads cases by file path and ANDES itself reads MATPOWER
.mand PSS/E.rawnatively, so it gains nothing from the powerio JSON transport for those. The remaining gap is the formats ANDES cannot read: PowerWorld.aux, PowerModels JSON, egret JSON.With
save_caseon the powerio server (#28), the workflow already exists without any ANDES change:Options, in order of effort: (a) document that two-step recipe in the README conversion section (one sentence already landed in #28); (b) add a
load_case_from_any(file_path, source_format=None)bridge toANDES/andes_mcp.pythat converts via powerio and stages a.mtemp file, like the Egret bridge. Given (a) covers the need, closing this as docs-only is reasonable unless demand appears for (b).🤖 Generated with Claude Code