General tools and documentation for the science tools checkout

The tools in this category are gtselect, exposure_cube, and exposure_map. Descriptions of these tools and links to any documentation are in the science tools section of the User Workbook.

This section is also being used for comments on the user-level documentation and on user interface issues.

Please edit this page to include results, issues, advice, etc., or links to these.

(4 October 2005) This may be a SLAC-specific problem, but I am unable to run the science tools and the general FTOOLS utilities from the same shell (under Linux, of course). If I have got .../headas/i686-pc-linux-gnu-libc2.2/lib in LD_LIBRARY_PATH, then the general FTOOLS work but none of the science tools will run; they quit immediately, for example:

$ gtpphase
This is gtpphase version v1r0p2
Caught N5hoops10HexceptionE at the top level: Parameter evfile not found in parameter group gtpphase (at ../src/hoops_group.cxx: 65)

So something is interfering with how the parameter files are processed. This might be solvable in the wrapper scripts, if there isn't a better way to make the science tools and FTOOLS coexist. (Seth Digel)

(4 October 2005) Reviews of gtselect, exposure_cube, and exposure_map have been posted by Masa Hirayama.

(29 September 2005) Eduardo's report on trying to run the tools under Windows also has some comments about documentation.

(28 September 2005) (Excerpted from the report by Jean Ballet)

  1. Documentation
    The User's documentation (workbook) is a vast improvement. Regarding the overall organization, I wonder why in the SciTools References bar gtexpmap appears under the General heading. I don't imagine what purpose this can serve outside likelihood. On the other hand, gtbin should appear under General (it is listed only under GRB).
    It would be nice if the ScienceTools part of the User's workbook could be distributed with the Science Tools and run locally (rather than depend on the web).
  2. General settings
  • Verbosity: The chatter parameter does not seem to have a large effect on most tasks.
  • Graphical User interface: At checkout2, a mechanism was introduced for several tasks, whereby they could be called with the setting gui=Y and conjure up a GUI. This is not documented at all, and does not seem to have moved forward since checkout 2. It is still not supported by most tasks. I have checked gtbin, on which I had declared STGEN-14. The GUI comes up, but nothing happens in my surroundings when I click on Run. The list of parameters is still truncated.
  • No labels