Python Task Interface System

CASA Modification Request 32C108, November 2007



1. Introduction

Each task (egs clean) is built on a python file <clean.py> which defines the set of tools that are executed, the parameters and types that are needed, and the input and help documentation. For asynchronous use, there is a similar script named <task_clean.py>. These scripts are presently generated by hand and have a relatively complicated structure.

2. Background

3. Requirements

Wes Young has been working on a simplified XLM(?) scheme which takes a set of logical inputs for a task and generates the python scripts. This would make it much easier for astronomers to define useful task scripts that use a collection of tools.

4. Design

The system has been defined, I believe. Debugging and implementation should begin relatively soon.

5. Deployment Checklist

6. Test Plan

6.1 Internal Testing

6.2 Sponsor Testing

6.3 Integration/Regression Tests

6.4 Testing for Scientific Validity


Signatures

APPROVED: I acknowledge that my request is fully contained in this MR, and if the CASA development group delivers exactly what I specified, I will be happy.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.

Written - - - - -
Checked - - - - -
Approved by Scientific Sponsor - - - - -
Accepted/Delivered by Sponsor - - - - -

Symbols:
  • Use %X% if MR is not complete (will display ALERT!)
  • Use %Y% if MR iscomplete (will display DONE)


Discussion Area

-- NicoleRadziwill - 30 Oct 2007

-- EdFomalont - 23 Nov 2007

This topic: Software > CasaPlanOfRecordC12008 > CasaModificationRequest32C108
Topic revision: 2007-11-23, EdFomalont
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback