Jonas Lähnemann
Jonas Lähnemann
### Description of the change Replaces #2967 leaving different types of changes to different commits for easier review. Addresses comments raised in #2967 and leaves out disputable changes. IO-related changes...
[](https://lgtm.com/projects/g/hyperspy/hyperspy/context:python) [](https://lgtm.com/projects/g/hyperspy/hyperspy/alerts/) The code checker `lgtm` has a number of errors, warnings and recommendations for HyperSpy. We should use that to consolidate our code: https://lgtm.com/projects/g/hyperspy/hyperspy
**This was reported by @magnunor in https://github.com/hyperspy/hyperspy/pull/2830#issuecomment-1086916555:** I tested `axes_manager.set_axis`, and there seems to be an "inversion" of the indices: ```python import numpy as np import hyperspy.api as hs s0...
As brought up on gitter by @TommasoCostanzo, it would be nice to support the new EDAX `.h5` (hdf5) file format for EDX measurements. The main thing is that one file...
If trying to initiate SAMFire with a fixed noise variance (using `m.signal.set_noise_variance()`), it fails because the variance is just a single value and not a signal object and as such...
The `tests.yml` workflow was probably affected by: https://about.codecov.io/security-update/ See the related discussion on jupyter: https://github.com/jupyterhub/team-compass/issues/398 At least the workflow does not contain any reference to `secrets. ...` that could have...
Allow setting optional `"hidden"` key in definition of signals extending hyperspy, which prevents them from being shown by `print_known_signal_types()`. ### Progress of the PR - [x] Change implemented (can be...
#### Describe the bug When replacing the first or second of multiple signal axes, `set_axis` replaces the wrong axis! #### To Reproduce Steps to reproduce the behavior: ``` import hyperspy.api...
#### Describe the bug When initializing a `signal1D` with two signal axes determined by setting `'navigate': False` in the dictionary, the resulting signal contains one navigation axis and one signal...
### Description of the change Adapt the metadata structure according to the discussion in #2095 ### Progress of the PR - [X] update metadata documentation, - [ ] Update occurences...