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

Gaussian source models #211

Open
nicholebarry opened this issue Apr 5, 2020 · 3 comments
Open

Gaussian source models #211

nicholebarry opened this issue Apr 5, 2020 · 3 comments
Labels
discussion needed A call for discussion

Comments

@nicholebarry
Copy link
Contributor

Gaussian source models are off by about 10%. If a standard scaling factor in both RA/DEC widths is applied at a constant 5-10%, the residuals are better (for both near-zenith and off-zenith Fornax models). Since DEC is well-behaved in a x-y coordinate system, this indicates that there is some sort of proportionality constant/conversion that is missing (as opposed to a problem in just RA, which does not map well to a x-y coordinate system). See pull request #143 for plots.

@miguelfmorales
Copy link
Contributor

I am wondering if this is an array filling factor issue. Essentially when the Gaussian model was made from the dirty image, it implicitly assumes the dirty image was made from a filled uv plane.

If this was the case the visibilities would be right based on the model, but the round trip of dirty-image, Gaussian components, visibilities, dirty image would have an amplitude error. This error would be implicit in the 1-2 step. One test is it would get worse as you extended the maximum baseline (keeping everything else equal), as the filling factor of the MWA would fall.

Within FHD point sources have an associated normalization factor (which might even be being applied here), but the appropriate factor will change with the size of the Gaussian. Essentially the spatial pattern of the Gaussian talks with the spatial pattern of the filling factor.

Just throwing mud at the wall.

@nicholebarry nicholebarry added the discussion needed A call for discussion label Jan 25, 2021
@rlbyrne
Copy link
Contributor

rlbyrne commented Nov 3, 2022

@nicholebarry is this resolved with #291?

@nicholebarry
Copy link
Contributor Author

I don't remember... I'll queue up a job and let you know

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

No branches or pull requests

3 participants