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

Validation of iDPC routine #2

Open
uellue opened this issue Sep 6, 2023 · 0 comments
Open

Validation of iDPC routine #2

uellue opened this issue Sep 6, 2023 · 0 comments

Comments

@uellue
Copy link
Member

uellue commented Sep 6, 2023

In principle, iDPC is supposed to calculate the potential from a field, i.e. integrate it. By using the iDPC routine instead of a simple path integral, it is supposed to reject irregular components, such as potential differences along a closed path.

With SSB and WDD, an object can be reconstructed quantitatively, i.e. the result is very close to a bandpass-filtered version of the object.

When calculating the field from a potential and then reconstructing it with iDPC, a blurred image is obtained:

image

Transfer function on a larger array of random data: np.abs(np.fft.fftshift(np.fft.fft2(rec_potential)/np.fft.fft2(potential)))

image

It seems like the weight of the individual spatial frequencies is off?

So, first, is the assumption right that potential -> field -> potential is supposed to work correctly?

In a simulated 4D STEM setting where WDD can reconstruct the object very faithfully, iDPC simply fails:

validation

Now, is the simulation and WDD routine in https://github.com/LiberTEM/LiberTEM-iCoM/blob/9e47352a1ada0a096abcb2fa7e6508179a4c7d8f/examples/reference-validation.ipynb wrong, is this breaking assumptions of iDPC, is the iDPC function not implemented correctly, or is iDPC simply not quantitative?

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

1 participant