Dealing with SEM/HAADF complementary data with their respective luminescence about lumispy HOT 4 OPEN

The management of the different signals is taken care by the workflow: the python script or the notebook.

In the case of the navigator, it would be worth considering improving support signal navigator if this is thought in a generic fashion and in a way that it doesn't too much burden to other functions. Maybe it is worth continuing this part of the discussion at hyperspy/hyperspy#2639?

from lumispy.

So you mean I should stick to keeping track of the changes in the navigation axis of the cl signal and manually applying the same changes to the s SE image file?
That's what I am doing, but I still think there must be a better way...

from lumispy.

@jordiferrero - I understand your point. In principle it applies also for EELS and EDX data and might be of more general interest. Though in many cases the spectral maps will have a lower resolution than proper HAADF or SE images of the same region, and a direct linking of this data is of limited value.

For example, our CL system does not record the SE signal in parallel. I usually have a corresponding SE image taken beforehand and the spectral image corresponds to only a ROI on that image. That SE image usually has a better resolution than the spectral image as I hardly ever use step sizes below 20 nm.

The main issue I see with your approach is that quite a number of functions would need to be adapted directly in hyperspy (e.g. crop, inav, rebin). What you want to do is basically stacking of signals. But I am not sure if stacking two signals with the same navigation dimensions, but different signal dimensions (e.g. 1024 and 1) is possible @ericpre, I do not have enough experience with that function. It might be worth thinking along the lines of adding such a functionality instead of adding an additional signal to the metadata.

from lumispy.

Indeed, there is room for improvement for the navigator and it would good to discuss how to improve it with others who are interested in this and this is why I put the link to the other issue!

from lumispy.