TypeError: argument tablename must be a string #25

Activity

1. mtazzari commented on Apr 25, 2018

   

   mtazzari

   on Apr 25, 2018

   Last edited by mtazzari

   Owner

   More actions

   I tried on CASA 4.7.0 and I am not able to reproduce the error.
   I run

   from uvplot import export_uvtable
   export_uvtable('uvtable.txt',
   tb,
   vis= 'test.ms')

   and I got no error.

   Have you tried typing the command manually instead of copy-pasting it?
   Which version of CASA are you using?
2. mtazzari commented on Apr 26, 2018

   

   mtazzari

   on Apr 26, 2018

   Owner

   More actions

   I am trying it out with CASA 5.1.

   In the meanwhile, try adding a str() command such as vis=str('test.ms'). Do you still get the error?

   Could you give more details on how you use the script?
   I.e. a minimum working example and how you run it in CASA.
3. SBrownson commented on Apr 26, 2018

   

   SBrownson

   on Apr 26, 2018

   Last edited by SBrownson

   Author

   More actions

   It seems
   from __future__ import (unicode_literals)
   in my script was producing the error.

   from uvplot import export_uvtable export_uvtable('uvtable.txt', tb, vis= 'test.ms')
   now runs smoothly.

   I note a new error,
   export_uvtable('uvtable.txt', tb, split=split, split_args = {'vis': 'test.ms', 'outputvis': 'new.ms', 'datacolumn':'DATA', 'spw': '0'})

   produces 'datacolumn CORRECTED_DATA is not available.'
   This seems strange given that DATA column was asked for explicitly. Also,
   export_uvtable('uvtable.txt', tb, 'test.ms', datacolumn= 'DATA')
   produces no such error.
   Note, 'test.ms' only has one spw - spw0
4. mtazzari commented on Apr 26, 2018

   

   mtazzari

   on Apr 26, 2018

   Last edited by mtazzari

   Owner

   More actions

   Ok, so

   from __future__ import (unicode_literals)
   

   was the responsible for the error about the string. It's fine not to use it.

   Re the datacolumn error: datacolumn is not only a keyword in the split_arg dictionary, but is also a parameter of the export_uvtable function itself, which by default is set to CORRECTED_DATA: as a consequence, if you pass only datacolumn in the split_args dict, by default datacolumn will be CORRECTED_DATA anyway.
   This is a bug that I should fix in future release.

   For the time being, there are two viable options:

   1. if split_args=None, datacolumn can be provided,

   export_uvtable('uvtable.txt', tb, 'test.ms', datacolumn= 'DATA')

   2. if you specify split_args, then datacolumn outside the split_args must be set to the same value as inside split_args, e.g.:

   export_uvtable('uvtable.txt', tb, 'test.ms', datacolumn= 'DATA', split_args = {'vis': 'test.ms', 'outputvis': 'new.ms', 'datacolumn':'DATA', 'spw': '0'})
5. mtazzari

   added

   bug

   on Apr 26, 2018