Persistent state, complex images, DPC #27
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ays CoM using color wheel, update virtual image display routines to handle complex numbers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds some persistence of state across runs, currently maintaining the same window size and autorange settings. The data is stored in a platform-dependent location using a Qt settings INI file.
This also removes the "CoM Magnitude" and "CoM Angle" detector response modes, and replaces them with a single "DPC" response that displays a Lab colored image representing magnitude and phase. To support this the virtual image can now be specified as a complex array, which triggers this new rendering mode. The data cursor changes to display magnitude and phase when hovering a complex image.
Detectors that require a mask (and thus loop over each pattern) now cause a progress bar to display in the status bar, since on some datasets these can be slow.
Keyboard shortcuts are available for the vanilla loader and the py4DSTEM export: Ctrl+O and Ctrl+S