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

Reviewer: Masaharu Hirayama
Software Component: dataSubselector
Summary of Tests Performed: Run it on Linux, and look at an output file.

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?

See the first three of my answer to question 10.

2. Are there any prompts you would suggest rewording?

Do not use word "FT1", but use a generic phrase such as "event file"
or "photon file". It is used to prompt input_file and output_file as
"Input FT1 file" and "Output FT1 file".

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

No.

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

No.

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

Change the default values as follows.
tmax 0 -> 1.0e+10
thetamax 0 -> 180
phimax 0 -> 360
gammaProbMax 0 -> 1
zmax 0 -> 180

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.

1) Cut by multiple time intervals, specified by a GTI extension or a
column-wise ASCII file.
2) Cut by user-defined Boolean/mathematical expression.
3) Cut by the FT2 parameter(s).
4) Allow a user to say "don't make a cut on that parameter," or change
a user interface so that the tool doesn't ask all the cut criteria.
5) Display a photon screening summary after screening,
so that a user can see how many photons are lost at each cut.
6) Command line editing and filename completion for user inputs
probably by introducing readline.
7) Warn a user if it removes all the photons in FT1.

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.