Skip to content

Improved automatic/default meshing for RF #2636

Open
@yuanshen-flexcompute

Description

@yuanshen-flexcompute

Current issue:

The default mesh (or lack thereof) for RF often does not give good results. From my experience so far, here are some common causes:

  • Metallic structures are not adequately resolved. The solution is to manually add layer refinement. It would be good if this could be automated in some way.

    • A sub-issue: layer refinement does not currently work for 2D metallic structures (zero thickness). It would be great if we allow layer refinement spec to work with zero thickness in such scenarios (corner/bounds snapping/refinement)
  • For subwavelength simulations, the min_steps_per_sim_size setting is more appropriate than the default min_steps_per_wvl. The best number for that setting is not 100% clear to me yet -- whether it's case-by-case dependent on geometry, or whether we can find a happy number that works for most cases.

  • A longer term goal is automatic mesh refinement (in the style of HFSS). This could be a custom study type, e.g. modeler.run_mesh_refinement(). The idea is to iteratively refine the mesh until some figure(s) of merit (usually S-parameter) converges.

Discussion:

The goal of creating this issue is to start the conversation on how we can better set up meshing for RF, in order to lessen the burden on users. Some questions on my mind:

  • Where are we implementing this? Front end? API level? Applets?
  • What does the implementation look like? Default settings for API functions? Custom auto-called "mesh setup" functions in the RF module? Others?
  • Transparency and versatility are important -- the user should be able to see what is added by default, and easily modify it if they wish.

Happy to hear everyone's opinions.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions