openEMS.de

I assume you mean the hdf5 field dumps? The openEMS read functions contain a TD signal with the exact timesteps that were saved. This is of course very important if you want to transform from TD to FD. Have a close look here: https://github.com/thliebig/openEMS/blob/master/matlab/ReadHDF5FieldData.m...

Energy that continuously increases usually means that the PML have gone unstable. The PML are usually the only element that is not inherently stable.
You may try to move them further away and/or make sure the mesh inside of them is homogeneous and in good shape.

Well yeah, Octave from snap won't work I guess.

I have updated the readme on github, let me know if this are really all required packages...

regards
Thorsten

I'm not sure what you are doing but the packages seem to be wrong! On Ubuntu 18.04 it should be sudo apt-get install build-essential cmake git libhdf5-dev libvtk7-dev libboost-all-dev libcgal-dev libtinyxml-dev qtbase5-dev libvtk7-qt-dev I hope I did not miss any important package... regards Thorsten

Hm, no openEMS can use any vtk version. I use 8.2 here. Try Qt5 packages and the latest vtk. It should work fine. I really have to update the required packages for a later Ubuntu. The problem is that I do not use Ubuntu anymore and thus I'm not really up to date and what packages should be used. reg...

Hm, I never had any issues with tiny_xml so far, even on cutting edge distros like Manjaro...
I will have a closer look...

Hi, openEMS is licensed under the GPL . More infos here . But this license only applies to the software itself. Only if you want to include openEMS (the software) into your own software product you have to oblige to the GPL license. Any output, data, idea or results obtained with openEMS, is your ow...

It is all defined here: https://github.com/thliebig/CSXCAD/blob ... Parser.cpp

If I read my already eight year old code correctly it should be "y0" and "y2".
The reason for y is that this is the name in "math.h". Don't ask me why...

I can only recommend to never use the same priority twice. Unless you are 100% sure they do not touch. STL is a bit tricky as it is unclear what happens if the STL surface is not closed or in others ways not healthy. Make sure the STL is closed, manifold and so on. Then add the STL as metal and noth...

Well maybe I have to be more precise. Intersecting e.g. a lumped port somewhere in the middle is not a good idea. Of course you need to connect the ends with metal signal lines which need to intersect or touch the port.
Just look at all the tutorials and examples on how it should be done.