openEMS.de

Hi,

I have not read everything again, but yes it is very typical that there is usually more than one way to do/setup something in EM simulations...

Ideally we would make the stripline port more flexible to allow for asymmetrical geometry...

regards
Thorsten

All the stacked spheres get the same priority. But for objects that intersect and have the same priorities it is undefined which material will "win". Make sure the smaller spheres get higher priorities such that they "cutout" the larger ones.

regards
Thorsten

No there is no real specification. Just run examples/tutorials the usual way and look out for the *.xml files...

Yes I was talking about a dynamic link (aka dll).

The alternative would be to write an xml file like it is created by the Octave interface and run openEMS on that.
It would create all required files, but again the post-processing is only done in python or Octave

The interface is operating system independent and I have build and tested the python interface for windows. But building it from source is a difficult task on windows. But that would be true if you want to link against it too as you will need to build openEMS and all its dependencies with the same c...

Hi, yes and no. Yes the python interface for example uses the openEMS/CSXCAD C++ API directly and you could do the same. It should have all you need to construct all the base primitives and properties and fully control the simulation. And no because a lot is done in the higher level languages like O...

I don't think there should be much of a difference between Ubuntu and Mint (which is based on Ubuntu). Maybe an error on the octaverc file or such... But yes I believe using a "snap version" of Octave is not a good idea as it sandboxes the tool. Thus calling external software like openEMS will give ...

Well good to hear, I have not checked what Octave I was using on my Ubuntu VM, but on my main system (Manjaro Linux) I am using Octave 6.4 without issues as well... But my suspicion now is that Octave (6.4 on Ubuntu?) somehow mangles the library paths and therefore openEMS cannot find it's libraries...

No this looks all like for me and means everything on the openEMS side looks good... The question know is how do you run a simulation and why is it not working for you? This is what my ".octaverc" looks like: openEMS_root = '~/opt/openEMS/share/' disp(['adding openEMS+CSXCAD path' openEMS_root]) add...

What you can also do is an
It should show all libraries used and that none should be missing...
For example my openEMS does not depend on libmpi_cxx.so40 or any other mpi library.