The ATCA Forum

Using uvindex, I see the frequency configuration change every 6th scan. Looking at the configurations reported by uvindex, the zoom frequencies are slightly different, but I'm unsure what could have caused this. Has it been reported before? 17MAY17:12:32:44.9 1045-62 c 6 39941 0 1 42121 17MAY17:12:3...

Hi Mark,

Just saw this. I ran mirsync and indeed mfcal is much faster. Thanks for the fix.

Cheers
Stacy.

After ~ 30 minutes and using edge = 2000 and interval = 2, mfcal completed.

I used edge here as there is a ridiculous number of channels, not required

Hi Jamie,

Doesn't seem to make a difference. Looking at the activity monitor the bytes in/out is 0, even after 2 minutes.

Hi Jamie, Only stokes=ii and interval=[0.1|10] I have copied the file to kaputar:/data/KAPUTAR_1/mad134/1921-293.22237.7.tar.bz2 The data was taken using 1M0.5k, with 16k channels (I just concatennated all zooms). I should note everything was fine the other day, but today, I'm running into this prob...

I'm seeing the same kind of thing with mfcal running 100% CPU, processing 1921-293 from last month. Upon finding this post, I did a mirsync and the version I currently have is: MfCal: $Revision: 1.18 $, $Date: 2017/03/06 03:50:09 $ It doesn't seem to matter whether I set interval to 0.1 or 10 minute...

The COORD script has been re-written using PyEphem. Hopefully past bugs/issues have been addressed.

imfit: Revision 1.11, 2013/08/30 01:49:21 UTC ------------------------------------------------- Object 1933-400_3cm RMS residual is 1.22E-02 (theoretical image noise is 1.24E-04) Using the following beam parameters when deconvolving and converting to integrated flux Beam Major, minor axes (arcsec): ...

Just understood your meaning. I'll look at the position.

Hi Jamie,

There is only 7.5 degrees between source and phase calibrator 1933-400... In processing all the L, C and X data, the same effect is seen. Odd.