Custom Query (241 matches)

When trying to load ASAP scantables previously created using version 3.0.0, I get the error 'SEVERE: Invalid Table data type when accessing column in ROArrayColumn ctor for column RESTFREQUENCY'

Likewise, scantables created in 3.1.0 produce the same error when attempting to load them into 3.0.0. I attach an example scantable created in 3.0. Is there a fix or workaround for this problem?

In running a script on MX Multibeam data with ASAP 3.1.0, I get the following error (script works under 3.0.0):

ASAP>execfile('mx.py')
Found ATPKSMB data.
Auto averaging integrations
Importing 2011-09-27_0551-P000_WKK5999_test.mbf...
SEVERE: STMath::quotient: no matching off
SEVERE: 'NoneType' object has no attribute '_add_history'
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)

/p/observer/radioschool/<ipython console> in <module>()

/p/observer/radioschool/mx.py in <module>()
      8 # Average all beam dat atogether
      9 
---> 10 avb = q.average_beam()
     11 
     12 # Average pols together

AttributeError: 'NoneType' object has no attribute 'average_beam'

We have been monitoring a particular spectral line source with Hobart (Mon R2) for more than a year now. We observe with fixed frequency and align in velocity when averaging the data during ASAP processing. When comparing spectra taken months apart we noticed differences of around 1 km/s between the same features in different spectra.

We have data collected with the ATCA and Hobart on the same day. Processing the ATCA data in miriad and the Hobart data in ASAP the velocities are different there as well. The source coordinates and observing frequency are recorded correctly in the RPFITS files (as best we can tell) and ASAP identifies the data as coming for Hobart.