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

Beam #24

Open
FerreolS opened this issue Oct 8, 2021 · 12 comments
Open

Beam #24

FerreolS opened this issue Oct 8, 2021 · 12 comments
Assignees
Labels
enhancement New feature or request

Comments

@FerreolS
Copy link
Member

FerreolS commented Oct 8, 2021

From the oifits files it is possible to estimate the beam that is: minor, major axes and PA of an ellipse describing the resolution of the interferometer.

@FerreolS
Copy link
Member Author

FerreolS commented Oct 8, 2021

There is 2 ways to estimate the beam

  • fit a 2D Gaussian on the dirty beam (Fourier transform of the (u,v) plane filed with 1 on each measurements
  • fit an ellipse on the (uv) plane that encompass all the uv coverage

@FerreolS FerreolS added the enhancement New feature or request label Oct 8, 2021
@FerreolS FerreolS self-assigned this Oct 8, 2021
@FerreolS
Copy link
Member Author

I propose to compute the beam by estimating the covariance matrix of the (u,v) coordinate of the baseline. Its eigen values will be the axis and the eigenvector will gives the angle of the ellipse in Fourier domain. Then convert to image domain.

@bourgesl
Copy link
Member

To compute the beam, should we use U-V frequencies from VIS2 tables only or also consider VIS and T3 tables ? Some OIFITS files may not have VIS2 tables, then no beam estimation.
As there is redundancy between tables, how to normalize properly ?

@FerreolS
Copy link
Member Author

Good question
All the UV frequencies has to be taken only once. This IMO drives out all T3 tables has I believe that if 3 telescopes are cophased then there must be corresponding VIS2 or VIS for the 3 baselines. (even if, in gravity, the recorded uv of the T3 differs do to integration difference).
For VIS and VIS2, it depends of the instrumental mode. If there is phase reference, we should take the UV of the VIS mainly (no need of V2 in that case), if the VIS contains only differencial quantities, the UV coordinates are probably counted twice in VIS and VIS2 table. As you can have files with mix of these modes, depending of how the tables were built, we probably need to retrieve all the non-redondant UV coordinate for both table.

@FerreolS
Copy link
Member Author

I propose to compute the beam by estimating the covariance matrix of the (u,v) coordinate of the baseline. Its eigen values will be the axis and the eigenvector will gives the angle of the ellipse in Fourier domain. Then convert to image domain.

To keep track of the information the Julia code, the documentation and a demo for that is here

@bourgesl
Copy link
Member

Here is OImaging beta release that computes the beam on VIS2 only and displays the ellipse at the image center (overlay):
https://www.jmmc.fr/apps/beta/OImaging/

@bourgesl
Copy link
Member

What algorithm can be used to discard redundant UV coordinate ?
it seems tricky to take precision into account (gridding ?)

@FerreolS
Copy link
Member Author

Nice! Should we add a button to display/hide it and maybe move it to a corner.

@FerreolS
Copy link
Member Author

What algorithm can be used to discard redundant UV coordinate ? it seems tricky to take precision into account (gridding ?)

I don't know. Probably the redondant UV coordinates in VIS and VIS2 have exactly the same value. This has to be checked in practice

@FerreolS
Copy link
Member Author

Here is OImaging beta release that computes the beam on VIS2 only and displays the ellipse at the image center (overlay): https://www.jmmc.fr/apps/beta/OImaging

✔️ I have checked that the plotted ellipse in the exactly the same than in my notebook for RCar

@bourgesl
Copy link
Member

bourgesl commented Jun 4, 2024

I updated OImaging beta:
https://www.jmmc.fr/apps/beta/OImaging/

Changes:

  • Added the toogle button 'Beam' on image panels to show or hide the beam info (displayed in its tooltip)
  • Modified the beam estimation to use distinct spatial frequencies from both OI_VIS and OI_VIS2 tables (with small rounding of spatial frequencies)

I left the beam at the image center as the plot is zoomable

@jean-philippeberger
Copy link

jean-philippeberger commented Jun 5, 2024 via email

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
Status: Test/Validation
Development

No branches or pull requests

3 participants