openEMS.de

seems like OS path problem. Avoid national characters, long file location strings. something like C:\project\prj1\ is a good choice.

don't forget to change the active directory in Octave/Matlab when executing.

As I mentioned it, yes. And I did not find anything useful there; it just calls the binary program, and I don't know what's inside.

Harminv does not have any user-oriented documentation, except a basic explanation that it is cooler than FFT. Actually, I could not find technical documentation either.

up

I use it in Windows... But I would try these solver parameters first: --engine=multithreaded %engine using compressed operator + sse vector extensions + MPI + multithreading --numThreads=<n> %Force use n threads for multithreaded engine --dump-statistics %dump simulation statistics to 'openEMS_run_s...

I did not see your example yet... just for comparison, I was simulating pulse scattering (not RCS, we were interested in energy leak paths) from large objects in a space like 3x5x2 meters at 10-20 GHz band. It was fitting in 32 Gb with proper optimization of mesh; but I was cutting on resolution in ...

If you really want details, try googling for radiating boundary conditions. The simpler paper on MUR: https://people.engineering.olemiss.edu/~yakovlev/Yakovlev_Publications/Yakovlev_paper_27.pdf The harder paper on all the methods: https://www.e-fermat.org/files/articles/154db8c5adee49.pdf But if yo...

I did not get the reason yet, but I see a flaw in your model: MUR conditions should be placed far away from the model, especially from leaking sides. (Y direction). MUR is a condition for normal far field ONLY. Oblique or evanescent wave hitting MUR will cause problems. Try at least quarterwave, or ...

It appears, harminv is binary compiled, which makes sense when talking about performance.
But I could not get a relation of harminv amplitudes to corresponding components of FFT from voltage.
How can I bring one o another in order to pinpoint the resonant peaks on the spectrum?

1000000000 it is crazy large. looks like a precision problem when timesteps are very small. timestep is 4.28692e-013 stoptime is 1e-7 there should be only 233267 timesteps, but I already got 789965 steps today. is something wrong here? stoptime=1e-7; FDTD = InitFDTD('CoordSystem', 0, 'MaxTime', stop...

I mean, I can extract, but it is very hard feeding the time data to paraview. If it is inside, it is accepted automatically for every "frame" as exact time.