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

Measurement pixel size on Hyperspectra measurements #762

Open
borondics opened this issue Oct 16, 2024 · 1 comment
Open

Measurement pixel size on Hyperspectra measurements #762

borondics opened this issue Oct 16, 2024 · 1 comment

Comments

@borondics
Copy link
Member

A user is asking if they could change the plotted pixel size for non-uniform maps (left on image). This could be an interesting use case but I am unsure how difficult it would be for implementation.

image

Also, it brings up other questions for regular raster maps: what happens if we plot a measurement with 10 micron aperture but 5 micron step size...? Measurement software and Quasar as well just plots the center of the aperture with a size of neighbouring center distance divided by two. Can we come up with a better way?

What if we have the opposite: a small aperture but large step, so the measurements never touch each other? For example in OPTIR?

@stuart-cls
Copy link
Member

This is an old but tricky problem. The function that we use to synthesize the map image array works best for a single, dense, hyperspectral cube like you get from an array detector. With point maps you often get grid mismatch between different measurement regions (as shown here), and this also happens when you combine maps (#567) or if there's variation in the position (#572) There's generally no information in the data file about aperture/spot size so we always default to span.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants