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

Troublesome Source persistent after 3GC calibration #370

Open
dianaklutse opened this issue Apr 25, 2020 · 2 comments
Open

Troublesome Source persistent after 3GC calibration #370

dianaklutse opened this issue Apr 25, 2020 · 2 comments

Comments

@dianaklutse
Copy link

I have been battling with a troublesome source in my image. Below is the 1GC image (first image) and the 3GC image (second image) produced with cubical. Attached is the cubical log file, the casa list observation file and the sky model. The troublesome source is not a point source. The original data set is made up of 4096 channels but it's been down sampled to 128 channels.

J2215
wsclean-image

J2215_cubical22.log
J2215_list_observation.log

testing3.lsm.html.tar.gz

@IanHeywood
Copy link
Collaborator

Hi @dianaklutse. I remember this pest from your poster!

Here are some thoughts on it:

  1. I haven't done the calculation, but bandwidth smearing might be starting to bite if you average the entire MeerKAT band down to 128 channels, which will make the accuracy of models of off-centre sources derived from images suffer.

  2. The attached LSM has nothing in the spectral index (spi) column, which means your sky model is entirely spectrally flat. Aside from the intrinsic (astrophysical, probably synchrotron) spectrum that the troublemaker has, it will have strong apparent spectral behaviour induced by its position in the antenna primary beam, as will every other sources away from the pointing centre. You will need to model the spectrum of the strong source more accurately to get rid of it.

  3. On that note I notice your frequency solution intervals for both the G and dE terms are set to 128, so the entire band. I would suggest chunking the band up here, once the improved sky model is in place. (The dE solution

  4. The LSM also has a lot of components around the troublemaker, as well as clusters of components around other bright features. I don't have the map but I suspect these are artefacts that the source finder has picked up and rolled into the model.

  5. I think in the current setup your skymodel only consists of the dE-tagged sources, so the rest of the sky won't be included while solving.

In short, I think you are asking CubiCal to calibrate your visibility data against a model that does not resemble the sky as MeerKAT sees it. It sounds like a lot but there are certainly ways to address the above, although it might mean backing up a few steps. I don't think it's necessarily a CubiCal issue though, so feel free to contact me directly if this isn't the place to discuss it.

Cheers.

@dianaklutse
Copy link
Author

Thanks Ian, I will work on the sky model and keep you posted.

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