-
I wanted to start this thread because I think there is quite a bit of misunderstanding on how hyperspy handles `lazy` operations and how to optimize performance. Sometimes I think that they way that …
-
We should improve the situation with setting the `signal_type` of EDS dataset, make it consistent across EDS data file reader and document its behaviour in `rosettasciio` and in `hyperspy`.
The app…
-
#### Describe the functionality you would like to see.
I think that it would be useful to save the functions that are applied to a signal. This is good practice and when given a dataset it would be u…
-
Currently getting access to the newest bug-fixes and features in the master branch can be fairly difficult for inexperienced users, but sometimes having access to these developments can be very benefi…
-
For background removal there are a few methods that operate on the data to create a background curve. They're not fitting methods but more like smoothing/filters with some parameters.
I was lookin…
-
It would be very nice having HyperSpy releases in the Debian repository, and since Ubuntu basically use the Debian repository it would be available there as well.
I'm guessing it won't be too complic…
-
#### Describe the functionality you would like to see.
Currently there are a couple of cases where attributes of a signal are added but then these attributes are not saved/propagated through to a n…
-
**Problem**
I don't have Bruker eSprit, but pattern intensities stored in a 4D HDF5 file and a separate text file with settings (such as grid dimensions, step size, pattern resolution in pixels etc.)…
-
It is probably not an issue to most of the users, but I find the current hyperspy metadata structure to be a bit clumsy. My main issue is with SEM and TEM leafs. These are like singletons. It makes th…
-
#### Describe the bug
Using hs.load to load a emi file of a flucam image yields an empty list []. I have checked that normal TEM images (ie. from a proper camera) work properly. Note that flucam imag…