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

inaccuracies in lwimager specification via browser / cattery #38

Open
twillis449 opened this issue Dec 29, 2015 · 0 comments
Open

inaccuracies in lwimager specification via browser / cattery #38

twillis449 opened this issue Dec 29, 2015 · 0 comments

Comments

@twillis449
Copy link
Contributor

So I just tried for the first time to make a dirty image via the 'imaging options' that appears via turbo-sim.py. There I'm offered the options of specifying the image size in pixels and the image size in arcmin. Since lwimager wants the cell separation in arcsec, you divide image size(arcmin) / image size in pixels. In the particular case I had I specified 13.65 / 2048-> cell size of 3.999999 arcsec (or thereabouts - anyway marginally less than the 0.4 arcsec I wanted.) This meant that the lwimager called via turbo-sim calculated that a point source situated several hundred pixels from the field centre had a flux density of 4.78 units vs 4.74 when lwimager was directly specified via the command line with a cellsize of 0.4 arcsec. Since I'm trying to 'compete' in an SKA gridding competition I though I had discovered a CASA bug until I looked at the exact spec fed into the lwimager.

Could you please add an option to specify cell size directly so as to override the calculation done above? Thanks!

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

1 participant