GLAST Standard Analysis Environment (SAE) Evaluation Questionnaire
Checkup 3
Sept 6, 2005 - Sept 27, 2005

Reviewer: Masaharu Hirayama
Software Component: exposure_cube
Summary of Tests Performed:
Created an exposure cube using an FT2 file downloaded from the
GSSC web site (http://glast.gsfc.nasa.gov/ssc/dev/databases/STC3/).

Observation about tool:

Executable name "exposure_cube" doesn't start with "gt" unlike other
SAE tools, and I don't know why.

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?

Some parameter names don't conform parameter interface standard by James.
http://lheawww.gsfc.nasa.gov/~peachey/glast/STParameterStandards.html

  • infile should be renamed to scfile.
  • table should be renamed to sctable.
  • clobber and mode should default to h (hidden).

2. Are there any prompts you would suggest rewording?

No.

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

It did NOT prompt for any parameters at all, but I think it should
prompt for parameters with 'a' (non-hidden ones).

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?

No.

Tool Behavior

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

The version number was not displayed. It said:
"exposure_cube: INFO: This is exposure_cube version unknown"

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.

None.

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.

General Notes

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

It takes a long time to complete: 820 s on glitch for 1 day data.
From that, it is estimated that it would take 6.8 hours for 30 day
data, 3.5 days for 1 year data.

  • No labels