Carter Francis

@viljarjf This is a good discussion to bring up, obviously things change with time so rehashing things is always good! Personally, I haven't really gotten into the habit of adding...

@magnunor This sounds really good! I do think that we need to be better about documenting what "DPC" means to us. We could probably copy and paste the first part...

@magnunor I was thinking something like: ```python s = hs.load("stem_dpc_data.zspy", lazy=True) s_nav = s.mean(axis=(-1, -2)).T s_nav.compute() s.plot(navigator=s_nav) shifts = s.get_direct_beam_position() # beam shift object # Need to compute the shifts...

> Actually, having thought about this a bit more: the reason I don't (currently) like to use `BeamShift` as the "DPC signal" is that the default `BeamShift.plot()` is pretty much...

Failing due to flaky tests fixed #1024

@pc494 This should be good to go. Just need to add to the changelog.

@ericpre I might move this up to `hyperspy` as an example? We could take part of @magnunor presentation on making publication quality plots from `hyperspy` and make that into a...

For example: ```python import hyperspy.api as hs import numpy as np n = 360 #the number of secants for the mesh t = np.linspace(0,2*np.pi,n) #theta values r = np.linspace(.6,1,2) #radius...

Just playing around with other things... ```python import hyperspy.api as hs import numpy as np t = np.linspace(0,2*np.pi,n) #theta values r = np.linspace(.6,1,2) #radius values change 0.6 to 0 for...

Something like this where the inset is rotate to match the real space x,y coordinate system