Versions Compared

Old Version 3

changes.mady.by.user Unknown User (chamont)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (chamont)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Review all the inline documentation of DataServer package, which is mainly obsolete.
  2. The way to check the content of a produced root file (script scanFile) is not good enough. We need something checking deeper the content. Replace scanFile with RUN_Check ??
  3. We should integrate large-scale tests, and track the size of the parameter files (files end events lists) so to check they stay in good limits.

Interface & Features

  1. be able to process svac, cal and beamtest input data files.
  2. have a "merge" options for the output data files ?
  3. generically scan, display, and copy auxiliary objects found in ROOT files.
  4. The GlastDataTypes C++ class have harcoded data types and values. They should rather be read from a configuration file, under the controll of the user.
  5. That same configuration file, or a separate one, should contain parameters instead of the environnements variables. Why not GAUDI parameter files ? Should we depend on GAUDI ?
  6. For the communication with the Web front-end, we should favor a early detection of problems, and setup a standard way to feed back the front-end with such early information (which could include an evaluation of the job end).
  7. Study the use-case "no tcut". In such a case, we should perhaps skip the use of a file containing the list of all data files.
  8. Enable tcuts through multiple data kinds.
  9. Idea : ensure that when a skimming is failing, the incomplete output data files is erased. Then, change the skimming step so that it will check that some output files already exists or not, and only do the ones which are lacking ? (a SK_FORCE_SKIP would enforce the skimmign whatever the files, and perhaps would be "true" by default).

...