Miriad Future

From CARMA
(Difference between revisions)
Jump to: navigation, search
(Infrastructure)
(Library)
Line 13: Line 13:
 
* cleanup or clarify the MAXDIM, MAXDIM2, MAXCHAN, MAXCHAN2, MAXANT, MAXANT2 confusion? Or use better memory management?
 
* cleanup or clarify the MAXDIM, MAXDIM2, MAXCHAN, MAXCHAN2, MAXANT, MAXANT2 confusion? Or use better memory management?
  
* python interfaces
+
* python/ruby interfaces (SWIG)
  
 
* uvio enhancements
 
* uvio enhancements

Revision as of 16:24, 19 February 2008

The CARMA bugzilla (you need an account for this) will contain a list of bugs and enhancements requests that are closer to being implemented than this list.

Tasks

  • uvimage currently just writes a visbrick image with no WCS. Once that is written, tools can use this to intelligently write region files for flagging using uvflag
  • uvclean: a new proposed task that would use the clean algorithm and for major cleaning cycles would subtract from the original visibilities (or the gridded one, not decision taken on this)
  • maxen: measure=cornwell does not seem to work (moved to bug 632)

Library

  • cleanup or clarify the MAXDIM, MAXDIM2, MAXCHAN, MAXCHAN2, MAXANT, MAXANT2 confusion? Or use better memory management?
  • python/ruby interfaces (SWIG)
  • uvio enhancements

Infrastructure

  • the old style shell scripts that install and maintain Miriad will be replaced by an autoconf based system. Currently this is mostly working
  • a set of procedures to use generated (uvgen, imgen) and teal (CARMA, SMA) telescope data to ensure that Miriad keeps on working as it used to work.
  • attempt to keep some level of correspondence with the ATNF version of Miriad
  • switch the current CVS to SVN, possibly in a neat environment for bugtracking etc.etc. An example could be the trac
Personal tools