Open mawc2019 opened 10 months ago
Take a look at this FAQ, particularly the third paragraph and the accompanying image. Try removing the k_point
from the Simulation
object constructor.
That FAQ does not seem to answer the issue.
the permittivity should be 4 everywhere
In the above example, there is only one material with epsilon=4
.
If k_point is changed to False, the flaw in permittivity will become different.
Setting k_point
to False
is equivalent to removing it from Simulation
. The flaw in permittivity becomes different but still exists.
Basically, it's an issue of what we should do right at the edge of the computational cell. Probably we should do subpixel averaging differently in that case. There is also some averaging with Yee grid points beyond the cell.
The simplest solution is to make the object a little bigger than the cell.
Sometimes the permittivity in simulation is different from what the user should expect. An example is as follows, where the permittivity should be 4 everywhere, but the value given by
The script is as follows.
sim.get_epsilon()
is different at the lateral boundaries.The flaw remains no matter
eps_averaging=True
orFalse
. Ifk_point
is changed toFalse
, the flaw in permittivity will become different.