New CI Nightly Windows Builds

[thliebig]

Hello all,

based on the CI work started by @biergaizi and with some help from Claude Code I was able to get CI building nightly builds for Windows.
I would ask all the Windows users to test it out such that I can find any remaining issues with the process.
The nightly builds can be downloaded here: Nightly Builds for Windows
Please test all executable, running some tutorials with the Matlab interface and installing the python wheels and the python tutorials. If you feel extra adventurous, you can try building the python interface for a different python version using the source tree but linking against the nightly binaries.

In short, any feedback is welcome.

Some documentation can be found here:
Install on Windows
Python Install Windows

[VolkerMuehlhaus]

I had an issue installing the Python 3.13 wheel.

OpenEMS unpacked to d:\openEMS
CSXCAD wheel installed properly using
pip install D:\openEMS\python\csxcad-0.6.3.post1.dev118+g21a098fa4-cp313-cp313-win_amd64.whl

openEMS wheel installation failed, see below:

(openems) C:\Users\volker>pip install D:\openEMS\python\openems-0.0.36.post1.dev161+g8cc9660a8-cp313-cp313-win_amd64.whl
Processing d:\openems\python\openems-0.0.36.post1.dev161+g8cc9660a8-cp313-cp313-win_amd64.whl
Requirement already satisfied: numpy in d:\venv\openems\lib\site-packages (from openems==0.0.36.post1.dev161+g8cc9660a8) (2.3.3)
Requirement already satisfied: h5py in d:\venv\openems\lib\site-packages (from openems==0.0.36.post1.dev161+g8cc9660a8) (3.14.0)
Processing d:\a\openems-project\openems-project\csxcad\python (from openems==0.0.36.post1.dev161+g8cc9660a8)
ERROR: Could not install packages due to an OSError: [Errno 2] No such file or directory: 'D:\\a\\openEMS-Project\\openEMS-Project\\CSXCAD\\python'

I stopped testing here, because all my tests would require functional Python interface.

In general, it would be nice to have some documentation on installating the Python interface for Windows. The Installation link just guides to the Linux setup, so new users might struggle here.

[thliebig]

Hello @VolkerMuehlhaus thanks for the feedback, Claude already found the cause and I will make an update soon 😏
Can you maybe confirm that all executable will run and not fail with some missing *.dll. e.g. maybe load some *.xml with AppCSXCAD and check if all looks and feels okay. This also contains a major update to latest vtk, Qt, hdf5 etc.
Thanks

[VolkerMuehlhaus]

Can you maybe confirm that all executable will run and not fail with some missing *.dll. e.g. maybe load some *.xml with AppCSXCAD and check if all looks and feels okay.

Hi Thorsten @thliebig

I opened some models in AppCSXCAD and everthing looked fine, no issues. I also started a simulation from existing XML, no issues. Looks good to me!

[VolkerMuehlhaus]

I need to mention that I didn't install or try the Matlab interface. Hopefully someone else can have a look.

[thliebig]

There is a new nightly build, same link, v0.0.36-162. Hopefully fixed python wheels + install readme

[VolkerMuehlhaus]

Still puzzled by the (new?) requirement to have CSXCAD_INSTALL_PATH, I looked at the old installation instructions which indeed tell users to set OPENEMS_INSTALL_PATH. Nothing else mentioned.

https://docs.openems.de/python/install.html#python-windows-install

For best compatibility with existing setups, I wonder if it would make sense to evaluate OPENEMS_INSTALL_PATH if CSXCAD_INSTALL_PATH is not set? What do you think @thliebig ?

[thliebig]

Yes this was done on purpose, see this commit
I guess we need to update the instructions then?

[thliebig]

The short answer is, CSXCAD is an independent CAD library. openEMS uses it but should not impose any requirements on it. Thus if anything, openEMS could try to read CSXCAD_INSTALL_PATH, but I think it should be okay to just set both path?

[VolkerMuehlhaus]

but I think it should be okay to just set both path?

You are the software owner, so it's your decision. I just wanted to point out that existing installation done according to previous documentation will break.

My personal preference would be to NOT break compatibility with existing installations and existing 3rd party instructions, unless there is a really urgent need to change this. If you would fall back to using OPENEMS_INSTALL_PATH when CSXCAD_INSTALL_PATH is missing, it would work instead of failing. If you prefer ignoring OPENEMS_INSTALL_PATH , the error message could indicate that CSXCAD_INSTALL_PATH might be missing.

[thliebig]

Well the documentation surely needs to be updated, but needing newer installation steps/instructions is not really breaking compatibility.