You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenDSS 13Bus example fails to compile on Linux (IEEELineCodes.DSS vs .dss) #129
The bundled OpenDSS/13Bus/IEEE13Nodeckt.dss redirects to IEEELineCodes.dss (line 46), but the file in the folder is named IEEELineCodes.DSS. On a case-sensitive filesystem the redirect fails and the circuit loads with no buses.
Steps (powermcp 0.4.0, Linux):
compile_opendss_file on 13Bus/IEEE13Nodeckt.dss returns success.
solve_snapshot returns converged: false, and get_results_summary_records shows all zeros (0 buses, 9 elements).
Running the same file through py-dss-interface directly prints Redirect File: ".../IEEELineCodes.dss" Not Found.
Renaming IEEELineCodes.DSS to IEEELineCodes.dss fixes it: the feeder converges in 3 control iterations with min/max voltages of 0.961 and 1.056 pu.
Two small improvements would help: rename the file in the repo, and have compile_opendss_file report failed redirects instead of returning success: true.
Thanks for the report. The casing part is fixed in #136 (merged): both 13-bus masters now redirect IEEELineCodes.DSS, matching the file. A new test checks every redirect/compile/BusCoords target in the shipped .dss files by exact name, so a mismatch like this fails CI on any platform.
The second suggestion is still open: compile_opendss_file should report a failed Redirect instead of returning success: true. @PauloRadatz@samtalki, could you help with this one? We can't run OpenDSS on Linux here, and I'd rather not guess at the engine's error channel.
After dss_tools.configuration.compile_dss(...), where does a failed Redirect show up reliably? Is it in the string dss.text("Compile [...]") returns (the Redirect File: ... Not Found. message), or in an error code/description on py_dss_interface? Or is it better to check a property after compiling, such as the bus or element count?
Does circuit_readiness() already capture this, or could it?
Which py_dss_toolkit version added configuration.circuit_readiness()? On an arm64 Mac, uv resolves the opendss extra (py_dss_toolkit, unpinned) to 0.7.0, which doesn't have it. The extra probably needs a version floor.
Activity
qian-harvard commentedon Oct 22, 2026
Thanks for the report. The casing part is fixed in #136 (merged): both 13-bus masters now
redirect IEEELineCodes.DSS, matching the file. A new test checks every redirect/compile/BusCoords target in the shipped.dssfiles by exact name, so a mismatch like this fails CI on any platform.The second suggestion is still open:
compile_opendss_fileshould report a failedRedirectinstead of returningsuccess: true. @PauloRadatz @samtalki, could you help with this one? We can't run OpenDSS on Linux here, and I'd rather not guess at the engine's error channel.dss_tools.configuration.compile_dss(...), where does a failedRedirectshow up reliably? Is it in the stringdss.text("Compile [...]")returns (theRedirect File: ... Not Found.message), or in an error code/description onpy_dss_interface? Or is it better to check a property after compiling, such as the bus or element count?circuit_readiness()already capture this, or could it?py_dss_toolkitversion addedconfiguration.circuit_readiness()? On an arm64 Mac, uv resolves theopendssextra (py_dss_toolkit, unpinned) to 0.7.0, which doesn't have it. The extra probably needs a version floor.