openEMS.de

I assume you have PML at the start and end? Can you try to make it PEC inside the PML and only finite kappa inside the "normal" domain? Maybe the PML does not behave well with high conductivity. As for -50dB vs -100dB: the mode matching is based on the analytical modes and therefore never matches 10...

Well the command looks fine to me. I assume the file "/opt/include/CSXCAD/ParameterObjects.h" is indeed available?

Hi there, can you try to change the qt.conf file in the openEMS folder? Adding the last line as below?: [Paths] Prefix = ./qt5 Plugins = ./qt5/plugins I'm a bit puzzled why Qt is unable to find it's plugins. Of course newer Octave versions cause this because they have changed/set this environment va...

Hi, the openEMS GUI uses Qt and thus should be wayland capable in theory. Maybe your version was build against a too old version of Qt? But I have not tried it myself yet, maybe vtk and/or openGL is the issue... You should be able to start it on wayland using xwayland by using something like "-platf...

Try to install the latest dev version. 0.0.35 is very old already:
https://github.com/thliebig/openEMS-Pro ... nd-install

The important part is the git clone of the master branch.

I'm actually not sure if there is one. I worked with him closely and he developed/described this method in his PhD thesis. But the thesis is in german and was never published as pdf online. He always wanted to create more publications on this topic but I'm not sure that he ever did. Maybe you can wr...

Oh wow, that's sounds like a task ahead

And thanks about the nix package manager hint. I was unaware of it. And I was unaware of "pyems". Do you know/use this package? It seems to be specialized for PCB as well...

I can totally relate to those considerations. Just out of curiosity, can you tell what larger system you have in mind and you want/need to support Windows and Linux? The python interface currently supports only Linux, but I have a working version for windows if you need it. The problem with C++ is t...

I would honestly recommend to do it the other way round. Start with the Octave or Python interface to understand how a FDTD simulation is setup and how it works. Then have a look what parts the engine itself and thus the C++ part is doing. The Python interface may be good here because it is a direct...

As HexAndFlex already said, it depends on what you want to do. The C++ (and xml) interface is more low level, you can e.g. create/manage all properties and primitives and control the simulation. But only the higher level interfaces (Octave/Python) can create the more complicated concepts/datastructu...