|
Known PyRAF Shortcomings, Differences from IRAF,
Planned Improvements, and Bugs
|
This is a list of known problems or limitations of PyRAF, differences
from the IRAF CL, and planned improvements for the future. Each item
is followed by a parenthetical comment on our plans for responding to
the item. If the comment says "no plans" then we do not currently
have any plans to implement the listed feature or behavior. That may
change if we receive enough feedback indicating that it is important.
Not included in this list are enhancements to the IDL-like capabilities
of Python through improvements to the Numeric module (which will be a
major focus of our efforts in the future.)
- Differences from the IRAF CL
- Known Bugs
- Limitations & Planned Improvements
Differences from the IRAF CL
Known Bugs in Current Release (v0.9.1)
-
When CL scripts are executed using `cl < script.cl', any tasks
inside script.cl that read input from stdin will not work
correctly (because stdin has been directed to script.cl, which
has no remaining data once the CL code has been read.)
(fixed in next release)
Limitations & Planned Improvements
-
CL script error messages print the Python line number where
the error occurred but not the CL line number.
(planned)
-
The startup configuration (e.g., IRAF home directory) is not configurable.
(planned)
-
Startup from within Python scripts (via 'import pyraf') is not easily
configurable.
(tentatively planned, although we are unsure of the best approach)
-
There is no text-based epar (a la IRAF epar) that runs in
a terminal window.
(no plans)
-
Graphics defaults (fonts, colors, etc) are not configurable.
(planned)
-
CL level gcur commands are incomplete. We plan to add more, though
it is unclear if we will ever implement the full set of commands.
(planned)
-
The image display cannot be used for interactive plotting. (Note that
it can already be used for noninteractive plots.)
(work in progress)
-
There is limited graphics support for terminal-type devices such
as xgterm and xterm.
(no definite plans, but we may add support
for interactive use of some terminals if demand warrants it)
-
A few graphics functions are not implemented (e.g., PUTCELLARRAY which
is used to put an image in the graphics window.)
(tentatively planned, but low priority)
-
We plan to make more of the current gcur capabilities (zooming,
etc.) accessible through GUI mechanisms --- menus, buttons, etc. ---
as well as (or instead of) through the traditional keystroke commands.
-
The PyRAF GUI epar is undergoing a redesign that will make it even better.
The Help GUI available within epar will be available independently and
will have more capabilities. The epar window may be persistent so that
it can remain available for multiple runs of a task. The functionality
of the window will be improved (e.g., making the up/down-arrow and
page-up/down keys active.)
|
Perry Greenfield & Rick White
Questions? Contact help@stsci.edu
2001 December 7
|