-
Notifications
You must be signed in to change notification settings - Fork 13
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
Pixel Current Artefact #68
Comments
Hi @Kyroba, I think this type of artifact happens when the time step is slightly too big, making the numerics slightly unstable. I would try re-running the simulation with |
I varied dt_max from default 0.1 to 0.05, 0.01, 0.001 yet the artefact was still there. Didn't seem to change in size or position at all either. |
Can you try increasing the |
Also, can you paste the results of |
Can you try either The basic problem is that the current density is defined on the edges of the mesh. For plotting, I need to sort of interpolate the current density to evaluate it at the mesh sites rather than edges. This is done by averaging the current density over each edge that's connected to a given mesh site, see below. In certain cases (I think when one or more of the triangles incident to a site is very long/narrow), this average produces artifacts. py-tdgl/tdgl/finite_volume/mesh.py Lines 203 to 243 in b779261
|
That dt_max value did the trick! Your explanation also makes a lot of sense. Thank you! |
So for a rule of thumb, I would say that if you see this type of artifact, look at |
When attempting a nanoSQUID simulation, I noticed a strange current spike stuck in a specific location of the loop. This current spike does not move or react to applied fields. You can see it just below the left weak-link (25mT applied field no bias):
The first thing I went to check was the mesh to see if there is some kind of dislocation:
But it doesn't seem like anything is wrong. Changing mesh parameters moves the artefact around, but I can never get rid of it. I have also iteratively removed each polygon to see if something was causing the issue, and to my surprise, I saw this artefact in a plain square film with no holes. The only way I was able to get rid of it was to use entirely different xi and lambda values.
The text was updated successfully, but these errors were encountered: