Flagging channels in 22 frequency ranges
Processing file 2010-10-11_0326.C2426
CABB data detected
Scan 1 started at 10OCT11:03:26:54.9
Source: 1934-638
RPFITS file version is unknown
---------------------------------------
Total number of spectra selected: 6600
There was no flagged data
---------------------------------------
No CACAL data was detected
Could you please reply here if you are using a different set of options to load the data, and continue to get the error with the latest atlod?
kaputar-161% atlod in=2010-10-11_0326.C2426 out=c2426.uv
atlod: Revision 1.34, 2010/12/08 00:59:40 UTC
Processing file 2010-10-11_0326.C2426
CABB data detected
Scan 1 started at 10OCT11:03:26:54.9
Source: 1934-638
RPFITS file version is unknown
---------------------------------------
Total number of spectra selected: 11880
There was no flagged data
---------------------------------------
No CACAL data was detected
We are getting the same problem here at Swinburne on the green machine. I ran the same test on the ATNF machines and all is well. Both Swinburne and ATNF are using
atlod: Revision 1.35, 2011/02/06 22:46:40 UTC
I just tried this:
atlod% inp
Task: atlod
in = 2009-05-31_0519.C1794
out = atfile.test
ifsel =
restfreq =
options = birdie,rfiflag,xycorr,noauto
nfiles =
nscans =
edge =
atlod% go
At Swinburne the response is:
atlod: Revision 1.35, 2011/02/06 22:46:40 UTC
Flagging channels in 22 frequency ranges
Processing file 2009-05-31_0519.C1794
CABB data detected
### Fatal Error: IF_NUM(i).ne.i ... I do not understand
atlod%
While at ATNF the response is this:
atlod: Revision 1.35, 2011/02/06 22:46:40 UTC
Flagging channels in 22 frequency ranges
Processing file ../2009-05-31_0519.C1794
CABB data detected
Scan 1 started at 09MAY31:05:20:04.9
Source: bp0537-441
RPFITS file version is unknown
---------------------------------------
Total number of spectra selected: 14400
There was no flagged data
---------------------------------------
Ok - we managed to overcome the weird "### Fatal Error: IF_NUM(i).ne.i ... I do not understand" error by removing a line in the atlod code that causes the fatal error. Then all seems to process okay. Quoting Luke "however it is still odd (and mildly alarming) to me that the same dataset worked with their build of the code."