Magnus Nord

@vidartf, thinking about it a little more, I guess the git-in-git is not really necessary. I was thinking if we wanted to keep the current layout with for example all...

I've been thinking about this a bit more, and I think it would make it much easier to expand HyperSpy's functionalities past the (mostly) EELS/EDX functionalities at the moment. For...

Doing the "hyperspy" and "hyperspy-em" split first sounds like a good idea, since it reduces the complexity by not having to sort into many different sub-projects. In addition, having the...

@dnjohnstone, agreed, hyperspy-em seems too narrow. I'm guessing doing a hyperspy-core + hyperspy-X, where X would be something related to material characterization?

I ran some quick and dirty benchmarking using one of my 4D-STEM-DPC datasets. The same dataset `(256 x 256 x 256 x 256)`, where the hdf5 file has been chunked...

The basic functionality works now, at least for the files I generate. However, the DM-files which I make are for some reason fairly large: 10x10 bool datasets takes about 600...

@francisco-dlp, nice! That reduces 7 MB down to ~60 kB.

The implementation should be ready for review now! I wasn't sure if (or where) I should mention this in the user guide. In the markers page: http://hyperspy.org/hyperspy-doc/current/user_guide/visualisation.html#markers or the IO...

To not plot the markers: `s.plot(plot_markers=False)`. Any kind of slicing and transposing means all the annotations are lost. This is due to how the permanent markers themselves are implemented. Individual...

For me, in the ipython qtconsole, it shows up in the docstring for both Signal1D and Signal2D. However, it is only present in the signature for Signal1D, not in the...