Skip to content

Screening currents near device boundary #120

Description

@ark286

Hi Logan,
I am working with Katja Nowack, and we are trying to use your superscreen package to simulate the diamagnetic response (e.g. susceptibility imaging) of some superconducting devices that we have measured with our scanning SQUID setup. I am having some issues with what I believe is some artifact in the simulation that is somehow related to the meshing. I'll try to outline the issue with a simplified example below.

Starting with the case where everything looks fine, a simple rectangle:

  • I generate a landscape for lambda (x,y), which for the example here is assumed to be uniform
Image
  • I generate create polygons to match the geometry and mesh it using
    device.make_mesh(max_edge_length = 2,preserve_boundary=False,buffer=0)
Image
  • I model the FC current as a simple circle loop
Image
  • The FC current generates a magnetic field at the sample
Image
  • The field from the FC generates screening current in the sample
Image

zooming in

Image
  • The screening currents in the sample produce a magnetic field at the SQUID plane that is threaded through the pickup loop, and we measure the flux
Image
  • I then raster the position of the FC current/pickup loop to simulate a scanning SQUID susceptibility image. Here, I am showing a horizontal line cut through the device.
Image

Barring signal magnitudes, which I am not too concerned with at the moment, this all looks fine. Now if I alter the geometry slightly to begin to include leads for the device, I get some strange behavior.

Using a similar simple example:

-The lambda landscape (uniform in this case) and mesh now look like
Image
Image

  • The FC current and position stays the same, but now the screening currents look like this:
Image

zooming in
Image

Notice the scale of the colorbar here as compared to before. There is now some additional current magnitude measured near the device edge.

  • This results in additional field calculated at the SQUID plane from the screening currents and therefore additional flux through the pickup loop, again notice the scale of the colorbar here.
Image

-If I simulate a similar horizontal linecut of the SQUID moving across the device, I now see an 'overshoot' of the susceptibility near the edges of the device.
Image

This doesn't seem right. The addition of the leads shouldn't change the diamagnetic response of the device far from them.

The overshoot evolves with the horizontal length of the leads. As the leads get shorter, the overshoot tends to decrease and the left and right overshoot become more asymmetric. However, there is some 'turn on' behavior of this overshoot with respect to the leads i.e. if the lead is absent there is no overshoot, but if I make the leads one pixel long, an overshoot appears. My best guess is this has something to do with the meshing and perhaps something to do with the mesh points lying on the boundary i.e. maybe how boundary conditions (current conservation) is implemented?

I have tried a bunch of different things here, but the one thing that seems to remedy the overshoot is adding a buffer to the mesh:
device.make_mesh(max_edge_length = 2,preserve_boundary=False,buffer=10)
Image

The linecut then looks much better, without the overshoot:
Image

However, looking at the current density, there is now current flowing outside of the device boundary (ends at x = 5um) which is not physical.

Image Image

Normally, I would just think the overshoot is some artifact of the simulation, which I still think it is, but we have susceptibility data measured on a device that shows a similar overshoot in the diamagnetic response. I think the overshoot in the data is stemming from some physics going on, but seeing the feature in the superscreen simulations made me think maybe there is a possibility of the overshoot being some SQUID imaging artifact. I realize this is a very long winded question, but if you have any insight here, it would be greatly appreciated.

Here's a link to a notebook with the example from above if that is helpful:
https://drive.google.com/file/d/1gu4jY5RsFgwSW8UP9ZQGX7nN6cKKA9ZX/view?usp=sharing

Cheers,
Austin

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions