Did you try the latest github version of openEMS?
Which vtk version is installed?
Search found 1506 matches
- Sun 15 May 2022, 09:03
- Forum: Install
- Topic: Problem with qt version while installing
- Replies: 2
- Views: 21
- Sat 07 May 2022, 22:02
- Forum: Usage
- Topic: NaN in source after ~350 time steps
- Replies: 3
- Views: 180
Re: NaN in source after ~350 time steps
I can only imagine that the simulation got unstable... Do you use PML? Also make sure your time signal is band limited and your mesh is not to coarse for the highest frequencies...
- Sat 07 May 2022, 22:00
- Forum: Usage
- Topic: Energy goes to infinity
- Replies: 2
- Views: 231
Re: Energy goes to infinity
The only thing that can really get unstable is the pml if reactive near fields hit it...
And a pml_8 is 8 cells thick. It looks like in z-direction it is way to close ...
And a pml_8 is 8 cells thick. It looks like in z-direction it is way to close ...
- Sat 07 May 2022, 21:58
- Forum: Usage
- Topic: Automatic meshing?
- Replies: 2
- Views: 190
Re: Automatic meshing?
I think the DetectEdges can do the third rule?
But in any case, why not define all necessary mesh positions in your script and only run smooth mesh over it?
What I usually do is create an object and the required mesh for it side by side...
But in any case, why not define all necessary mesh positions in your script and only run smooth mesh over it?
What I usually do is create an object and the required mesh for it side by side...
- Sun 03 Apr 2022, 11:47
- Forum: Usage
- Topic: Where can I find the minimum spatial step used in openEMS?
- Replies: 4
- Views: 754
Re: Where can I find the minimum spatial step used in openEMS?
A mesh must always be defined. But in the script you mention the simulation is setup by the external function/script "Patch_Antenna_Array.m".
Look out for the mesh definiton "DefineRectGrid" which is always the final step with the finished mesh definition...
regards
Thorsten
Look out for the mesh definiton "DefineRectGrid" which is always the final step with the finished mesh definition...
regards
Thorsten
- Sun 03 Apr 2022, 10:06
- Forum: Install
- Topic: Problem with CSXCAD and python interface
- Replies: 4
- Views: 1107
Re: Problem with CSXCAD and python interface
I want to reiterate, if you just want to use openEMS, I recomment using the premade scripts from github: git clone --recursive https://github.com/thliebig/openEMS-Project.git cd openEMS-Project ./update_openEMS.sh ~/opt/openEMS --python And I recommend not to install/use as root. Only if you really ...
- Sun 03 Apr 2022, 10:04
- Forum: Install
- Topic: Problem with CSXCAD and python interface
- Replies: 4
- Views: 1107
Re: Problem with CSXCAD and python interface
I just noticed, did you build the CSXCAD python interface?? You need to build and install *both* the CSXCAD and openEMS python interfaces...
- Sun 03 Apr 2022, 10:02
- Forum: Install
- Topic: Problem with CSXCAD and python interface
- Replies: 4
- Views: 1107
Re: Problem with CSXCAD and python interface
Hi, did you try to just follow the instructions on github? https://github.com/thliebig/openEMS-Project#readme In any case for each "module" you can create a file called "localConfig.cmake" (next to the main CMakeLists.txt with e.g. the following content (for openEMS). SET(WITH_MPI 0) SET(FPARSER_ROO...
- Sun 03 Apr 2022, 09:51
- Forum: Usage
- Topic: Where can I find the minimum spatial step used in openEMS?
- Replies: 4
- Views: 754
Re: Where can I find the minimum spatial step used in openEMS?
Just do in your Octave script min(diff(mesh.x)) ?
- Sun 03 Apr 2022, 09:50
- Forum: Usage
- Topic: Lumped element port with excite produces error
- Replies: 2
- Views: 645
Re: Lumped element port with excite produces error
Yes meshing is the most important step. Any error here and you only get garbage... As for your second comment. Yes the absorbing boundaries are more computational expensive. But 500 times sounds very excessive, maybe you domain was very very small and thus the extra space for the pml and such slowed...