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

Data 3D with different signal axis at each pixel #1

Open
aurore-finco opened this issue Oct 28, 2024 · 4 comments
Open

Data 3D with different signal axis at each pixel #1

aurore-finco opened this issue Oct 28, 2024 · 4 comments

Comments

@aurore-finco
Copy link

Hi!
I started trying loading our data from other setups not running with pymodaq using pymodaq_data, and there is something that I do not know how to do. When we do 2D scans measuring the magnetic resonance of the NV center at each pixel, we often change the microwave frequency range at each pixel to track the resonance. So in the end we have a 3D data object with 2 nav axes and one signal axis which is varying. Is there a way to "attach" an Axis object to every pixel in the map in a DataWithAxes? Or is it a weird thing that nobody else would need?
Thanks!

@seb5g
Copy link
Contributor

seb5g commented Oct 28, 2024

this is uncommon because then each signal data is different for each pixel. What could be done to get back with usual data is to create an axis and interpolate all your signal data on this one (even if it means you'll have to crop a bit the total range). Then you'll be back with an object that you can manipulate easily

@aurore-finco
Copy link
Author

OK thanks. This is indeed a solution, although I do not really like interpolating raw data when this is not absolutely needed.
I have the impression that something could also work with a spread data distribution, as we keep the number of microwave frequencies constant, but this is not clear yet, I'll keep thinking about it.

@seb5g
Copy link
Contributor

seb5g commented Oct 29, 2024

if the number of frequencies is constant and the scaling also then you could just use an axis composed of index and store the scaling and offset as extra attributes of the data object

@aurore-finco
Copy link
Author

Yes, I think that it would work. I will try that.
Thanks a lot!

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

No branches or pull requests

2 participants