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

UV to k-space pixel maping of output #42

Open
piyanatk opened this issue Oct 30, 2020 · 5 comments
Open

UV to k-space pixel maping of output #42

piyanatk opened this issue Oct 30, 2020 · 5 comments

Comments

@piyanatk
Copy link

A functionality to map (or match) uv pixels of the output to given k-pixels (e.g. from an already existing image cube) would be very useful for incorporating 21cmSense into other simulations (e.g. generating training sets for machine learning).

@steven-murray
Copy link
Contributor

@piyanatk is the idea that you want Image-space sensitivities? Or just that you want a function to convert uv to k?

@piyanatk
Copy link
Author

piyanatk commented Feb 1, 2021

@steven-murray The idea was just the latter of what you said, but being able to make an image cube of sensitivities would be awesome of course. This idea came from a conversion in the machine learning telecon a while ago that a k-cube or image-space cube would make it convenient for various machine learning purpose.

@steven-murray
Copy link
Contributor

There is already a function in the code that converts uv to k: py21cmsense.conversions.dk_du. As for the latter, see #33 :-)

@piyanatk
Copy link
Author

piyanatk commented Feb 2, 2021

Hm, I am not sure why this conversation was brought up anymore. The function seems to exist since 15 months ago too ...

Anyway, that is great. Just to make sure I understand. The uv grid can be specified in py21cmsense.observation.Observation.ugrid, and because the mapping between Image to K to UV is linear, ones can trace back from the images that they have to to ugrid that they need to specify, correct?

@steven-murray
Copy link
Contributor

Yes, I believe that is all correct :-)

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