Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change particle data to a subclass of Signal1D so that hyperspy functions can work on the data #33

Open
TomSlater opened this issue Mar 5, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@TomSlater
Copy link
Contributor

Had an interesting point raised that particle data could be stored as a Hyperspy Signal1D object where the navigation dimension is particle number and the signal dimension contains the signal in question. This would enable hyperspy functions to work on the data without iterating through particles.

One possibility is to have all "stored data" stored only in the particles object as independent Signal1D objects. Each particle object would then have an index which would allow it to reference the Signal1D navigation axis and access the data.

The main question is, does this allow any additional functionality or a speed up in processing time?

@TomSlater TomSlater added the enhancement New feature or request label Mar 5, 2020
@TomSlater
Copy link
Contributor Author

The particle dimensions in any signals would have to be normalized before doing this, which is trivial using normalize_boxing. Even more trivial for spectra etc...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant