Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why does the mesh not cover the entire polygon? #242

Open
Zwlzzm opened this issue Jul 9, 2021 · 2 comments
Open

Why does the mesh not cover the entire polygon? #242

Zwlzzm opened this issue Jul 9, 2021 · 2 comments

Comments

@Zwlzzm
Copy link

Zwlzzm commented Jul 9, 2021

Hi,
In function "Component: FDTD simulation for S-Parameters, create Compact Model" of sipeic ebeam pdk,
why does the mesh not cover the entire polygon, but only a small part? Are there any considerations for this?

lumapi.evalScript(_globals.FDTD, " \
  newproject; closeall; \
  addfdtd; set('x min',%s); set('x max',%s); set('y min',%s); set('y max',%s); set('z span',%s);\
  set('force symmetric z mesh', 1); set('mesh accuracy',1); \
  set('x min bc','Metal'); set('x max bc','Metal'); \
  set('y min bc','Metal'); set('y max bc','Metal'); \
  set('z min bc','%s'); set('z max bc','%s'); \
  setglobalsource('wavelength start',%s); setglobalsource('wavelength stop', %s); \
  setglobalmonitor('frequency points',%s); set('simulation time', %s/c+1500e-15); \
  addmesh; set('override x mesh',0); set('override y mesh',0); set('override z mesh',1); set('z span', 0); set('dz', %s); set('z', %s); \
  ?'FDTD solver with mesh override added'; " % ( FDTDxmin,FDTDxmax,FDTDymin,FDTDymax,FDTDzspan, \
     Z_symmetry, FDTD_settings['Initial_Z-Boundary-Conditions'], \
     wavelength_start,wavelength_stop, \
     FDTD_settings['frequency_points_monitor'], sim_time, \
     FDTD_settings['thickness_Si']/4, FDTD_settings['thickness_Si']/2) )

I see there are some sentence, are this becauses of convergence testing?

definitions:
z: thickness direction
z=0: centre of the waveguides, so we can use symmetric mesh in z
which will be better for convergence testing as the mesh won't move

@lukasc-ubc
Copy link
Member

The simulation mesh covers the entire volume ("addfdtd").

It is the mesh override that you are concerned with ("addmesh"). This one is configured to have higher resolution in the thickness direction only.

Being careful with the mesh is important when doing convergence testing, otherwise a changing mesh will give you slight different results.

@Zwlzzm
Copy link
Author

Zwlzzm commented Jul 9, 2021

@lukasc-ubc

Thank you very much for your respond.
You mean, the mesh override is only assigned to z direction. But I see there are still value in x span and y span of mesh overrided. Does those value don't take effect and are assigned randomly?

In addition, I would like to ask about this mesh, z=si_thickness/2,dz=si_thickness/4, is it good enough for most of convergence test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants