Desired Upgrades for tasks in the PyDrizzle package. Last Modified: 19-Sept-2002 (WJH) Disclaimer: The following lists of desired upgrades are NOT listed in any semblance of priority, nor should any priorities be assumed. There are currently no specific time lines for getting any of these done, although, ideally they should all be addressed within the next year. This file should also be kept current based on revisions that get completed and on any new upgrades that would be scientifically helpful. Furthermore, it is implicit in this list that a complete set of documentation be produced for users to not only explain how to use this code, but also what components make it up so they could build upon it in their own analysis tasks. Pipeline Processing: 1. Revise and implement a version of 'multidriz' to automatically perform improved image registration, cosmic-ray removal, distortion correction and dither combination at the same time (as needed). PyDrizzle: 1. Keep track of output path and use that for all outputs, intermediate products and final images alike. 2. Possible logging of CL commands used to run 'drizzle'. 3. Revise 'buildPars' to work completely independently after a PyDrizzle object has been built. It should work so that changes can be made to the output parameters or drizzle parameters without recreating mask files or coeffs files, and it should properly resize the output as well. 4. Provide support for NICMOS 5. Provide support for simple (no-extension) FITS files. 6. Refine the calculated output size to not drop pixels. 7. Accept total shifts from ASN table, instead of only deltas. This would support the effort by CADC/ST-ECF to compute shifts between observations in WFPC2 associations and then use PyDrizzle to combine them in OTFR (eventually). 8. Remove dependency on 'keypar' to make it more robust when being run multiple times at the same time on the same machine. 9. Remove any dependency on 'WAVELENGTH' column from the IDCTAB. 10. Maintain compatibility with whatever version of 'multidriz' gets implemented for the pipeline. buildasn: 1. Create CALACS-compatible ASN tables, if possible. 2. Add optional column for scale changes in output table. (this may not be needed, but came up as a possible way to support velocity aberration or other breathing related plate scale changes that occur during an observation.) updateasn: xytosky: