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

strange Ex behaviour at domain edge #149

Closed
tsikd opened this issue Feb 22, 2021 · 3 comments
Closed

strange Ex behaviour at domain edge #149

tsikd opened this issue Feb 22, 2021 · 3 comments

Comments

@tsikd
Copy link

tsikd commented Feb 22, 2021

Hi,
please see attached input.deck and idl visualization .pro file. Ex seems to drop to zero near the right domain edge. i.e. print,data.ex(*,5)
50000.000 50000.000 50000.000 50000.000 50000.000
50000.000 50000.000 50000.000 50000.000 0.0000000

even at t=0 Ex last point is zero. Seems like bug-type behaviour. Can you replicate this?
input.deck.txt
snm.pro.txt

@TomGoffrey
Copy link
Contributor

I think this is working as intended. The zero-value element ex(nx,*) is the element of the normal component at that boundary, which is set to zero for the boundary conditions you specify.

@tsikd
Copy link
Author

tsikd commented Feb 23, 2021

If your comment is true then because bc_x_min and bc_x_max are the same ex(0,*) would be zero but it is 50000. seems odd behaviour isn't it?

@TomGoffrey
Copy link
Contributor

EPOCH uses a staggered grid. In 2D Ex is defined at x-face of the cell. For ten cells you have 11 interfaces, Ex(0:10). The boundary values Ex(0) and Ex(10) are set to zero. The SDF file contains 10 values (1:10), so you only see one zero point.

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