GLAST Standard Analysis Environment (SAE) Evaluation Questionnaire
Checkup 1
October 12, 2004 - October 29, 2004

Reviewer: Masaharu Hirayama
Software Component: exposure_cube
Summary of Tests Performed: Run it on Linux, give an output file to
exposure_map, and look at its output.

User Interface

1. What, if anything, about the choice and meaning of parameters
could be improved? Are there new parameters which need to be
added? Are the current parameters sensible?

1) Accept the FITS standard in specifying filename and extension, such
as "ft1file.fits[2]" and "ft1file.fits+2" meaning the second
extension of a file named ft1file.fits.
2) Rename npix to npixx, if it means the number of pixels in X-axis.
Ignore this request, otherwise.

2. Are there any prompts you would suggest rewording?

1) Use capital letters in a consistent manner. For example,
table_name: "name of" -> "Name of"
filter: "filter expression:" -> "Filter expression:"
projtype: "Projection Method" -> "Projection method"
uselb: "use l, b instead of ra,dec" -> "Use (l, b) instead of (RA, DEC)"
npixy: "y axis" -> "Y-axis"

2) Change the confusing wordings as follows, for example.
npix: "Total pixel size of the image in each axis:"
-> "The number of pixels in X-axis"
npixy: "Total pixel size of the image in y axis:"
-> "The number of pixels in Y-axis"
pixelsize: "Image size [degrees/pixel]" -> "Pixel size [degrees/pixel]"

3. Are there any hidden parameters which you think should be
prompted for or vice versa?

The following parameters should be hidden by default: clobber,
chatter, mode, table_name, filter, uselb, and costhetabinsize.

4. Would you like the prompts to appear in a different order?

Yes. My suggestion is to prompt them in the following order: infile,
table_name, outfile, npix, npixy, pixelsize, xref, yref, rot,
projtype, uselb, tstart, tstop, filter, costhetabinsize, clobber,
chatter, and mode.

5. Would you suggest changes to the default values of any
parameters? Changes to min, max fields?

1) Change the default value of "mode" parameter from "h" to "ql".
2) Don't include environment variables in a system parameter file.
Expand it when installed.

Tool Behavior

6. In what way, if any, did the tool perform unexpectedly?

None.

7. Were there any aspects of the tool's output which seem
scientifically suspicious to you? (e.g. fluxes too large,
number of events selected too small, etc.)

No.

8. Was there information (i.e. output) the tool did not provide
which you think it should?

No.

9. Was there information (i.e. output) the tool provided which
you think it should not?

No.

Future Development

10. List new features you would like to see implemented, in
descending order of importance. Please flag any which you
think are critical for DC2.

Command line editing and filename completion for user inputs probably
by introducing readline.

11. Are there any aspects of this tool you would change in order
for it to work more smoothly with other parts of the SAE?

No.

JIRA Summary

Please list the identifiers of any/all JIRA issues which were filed
in connection with this evaluation.

None.

General Notes

Please include here any comments about this tool which do not
fit into one of the categories above.

None.