The ATCA Forum

Hi Tim,

The most common cause of behaviour like this is including data across an acal. Are you sure you discarded data before the final acal on 1934?

Hi Tim, Although that method is pretty good, it can only calibrate for certain effects. If, for example, you don't do opacity correction during the atlod stage, I'm not sure this calibration method will compensate. Now, even if tell atlod to do the opacity correction, it may not apply it to the flag...

Hi Jules, Can you give an example please? Are you trying to do this on the command line, or from within the Miriad shell? If you're doing it on the command line, you need to put quotes around the select command. For example you could do something like: uvplt vis=dataset.uv "select=-ant(6)"

Yes, I think we may need to look at the data. What does the output of that uvplt command look like in PGPLOT?

Thanks Stephen. Based on the output, I would first check that antenna 6 is present in the data, because I can't immediately see any problem with the command.

Hi Stephen,

Can you please post your inputs to invert in full please, and the terminal output?

Hello,

I think you will have more luck if you use the "uvputhd" command for this.

uvputhd vis=0512-7306.1419.5.2 hdvar=source varval=0512-7301

Hi Boyang,

No, I mean the ouput of uvspec, with vis=1934-638, stokes=xx,yy options=nopass,nopol,nocal, axis=chan,phase and yrange=-180,180.

Hi Boyang,

This looks to me like you have not set your delays correctly, which also affects the Tsys measurements. What do your phases look like over your channel range while observing 1934-638?

Hi Stacy,

I didn't time it, and I just left it running from Friday afternoon, but mfcal with interval=1 (no other options) worked for me on kaputar on your 1921-293.22237.7 dataset.