-
Notifications
You must be signed in to change notification settings - Fork 73
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement 3D EPR simulations in Elmer
Implement a new solution type `ElmerEPR3DSolution` which: - Keeps the original (dielectric) layers in Elmer instead of grouping them by material. - This enables the use of partition regions in Elmer 3D simulations - Support for use of tls sheet interfaces in Elmer (`tls_sheet_approximation`) - Result energies for tls sheets are saved in normal and tangential components with prefixes `Ez` and `Exy` - Correction based on thickness and permittivity can be done in post-processing with `produce_epr_table` - Solution type does not produce capacitance matrix but only energies - Add a simulation script `tls_waveguide_sim_elmer` showcasing the new solution type To enable new solution type, some other changes were also needed - Add a new keyword `detach_tls_sheets_from_body` in `Simulation` to control whether tls_layers are shifted from the metal by `tls_layer_thickness` - Implement custom Elmer Solver module for saving the energies on the 2d tls sheets - As a temporary solution the module is automatically compiled at runtime when needed. - Compiling at runtime only supported in Linux or WSL - Gmsh mesh is generation refactored to enable using partition regions - When using the new solution type Gmsh writes signals and grounds as 3D bodies instead of 2D boundaries and does not write ports Bugfixes and minor unrelated changes: - bugfix: warnings from simulation export (stderr stream) is propagated correctly when usig `kqc sim` - Energies written in project results also for `ElmerCapacitanceSolution` when using `integrate_energies=True`
- Loading branch information
Tuomas Myllari
committed
Jun 5, 2024
1 parent
ad33d0f
commit c0a4215
Showing
11 changed files
with
848 additions
and
120 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.