Opened 13 years ago

Closed 13 years ago

#250 closed defect (fixed)

ASAP 3.1.0 cannot process MX scan script

Reported by: StacyMader Owned by: Malte Marquarding
Priority: normal Milestone: Unified development
Component: General Version: 2.0
Severity: critical Keywords:
Cc: stacy.mader@…

Description

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'

Attachments (1)

mx.tar.gz​ (4.1 MB) - added by StacyMader 13 years ago.

Change History (4)

Changed 13 years ago by StacyMader

Attachment: mx.tar.gz​ added

comment:1 Changed 13 years ago by Malte Marquarding

Owner: changed from Malte Marquarding to Malte Marquarding
Severity: normal → critical
Status: new → assigned

I have reverted back to asap-3.0.1 for ATNF lenny 64bit machines. You might want the sys admin to do a pull (for pictor).

comment:2 Changed 13 years ago by Malte Marquarding

There a various breakages now via the ALMA update which need to be rectified first.

comment:3 Changed 13 years ago by Malte Marquarding

Resolution: → fixed
Status: assigned → closed

Fixed in trunk.

Note: See TracTickets for help on using tickets.