Custom Query (104 matches)

Have any of you come across an error message:

### Warning:  I/O error when reading bandpass table, in Gains routines.
### Fatal Error:  End of file detected

Everything seemed to be fine until I ran mfcal/gpcal and the message comes up if I run eg uvplt. Although uvplt works fine if I set options=nopass

Similarly if I try to plot the bandpass table I get:

GpPlt: version 23-Jan-07
### Warning:  Error reading the bandpass table
### Fatal Error:  End of file detected

I don't think it's the data as the same problem now occurs if I recalibrate the previous epoch which had been fine. How could I have broken the software?!

I'm looking at the files 2009-11-08*.C989 although once I got this problem I also tested a dataset that had previously worked ok, 2009-11-05*.C989, and now I get it with that as well.

I've run atlod, uvaver, uvsplit and blflag with no problems. Then mfcal/gpcal appear to run without problems. Then after that I get the error mentioned below when I try to do anything that tries to apply the calibration (blflag, uvplt, gpplt).

The task parameters I'm using are all fairly standard:

mfcal - vis=1817-254.5500, stokes=i, interval=2

gpcal- vis=1817-254.5500, stokes=i, interval=2, options=qusolve,xyvary

uvplt - vis=1817-254.5500, stokes=i, device=\xs, nxy=1 (including
options=nopass gets rid of the error)

I'm running the current version of miriad/rpfits on Mac OS X 10.5.7

It has been found by a team (Feain, Broderick, Mahony) investigating polarisation at 7mm that the position angle of the E vectors change by 90 degrees from 12mm data to 7mm data. This has been reported on a few sources. By forcibly multiplying the Q and U components by -1 they achieve much more satisfactory (and believable) results.

Feain also points to a similar problem found by Johnston and Koribalski at 12mm a few years ago, that required a change to atlod to fix.

When the maxwidth option is used some of the files contain spectra with incorrect frequency labels.