Ganga Planning in 2007

Medium and long-term goals:

  • improve usability of the currently available features
  • improve testing and documentation
  • introduce several missing functionalities

Assure that the maintenance of the software may be done with reduced manpower effort in 2008

Ganga Core and Framework

GPI Interface changes

  • jobs.select(): logical slices (also in the job tree) and collective operations (kill, submit with keep_going behaviour)
  • physical indexing and slicing
  • revise the job tree interface
  • submission behaviour: keep_going for subjobs
  • submission behaviour: clear exception handling and error reporting
  • ability to manually "fail" the job
  • verbosity control when printing jobs
  • access to the monitoring loop (disable/enable/do_once)
  • timestamps in repository
  • revise the type checking

Internal changes

  • stop threads gracefully (avoid jobs locked in the "completing" state)
  • credential /Afstoken,GridProxy/ expiry detection (disable the monitoring loop automatically to prevent corruption)
  • automatic debug information collection
  • configuration subsystem upgrade
  • cleanup of logging messages (GangaLogging)
  • implement the remote workspace
  • disabling of backends (so if LSF is not available then LSF plugin is disabled)
  • lazy loading of jobs (faster startup)
  • ability to see jobs created in different sessions (refreshing job registry)
  • revise status machine for job status
  • fixes in the sequences of simple items (append)

Documentation

  • Restructuring of the web page and integration of existing pages
  • Creation of Ganga workbook from existing/new information
  • Extraction of reference manual from help texts.
  • Ganga paper

Test suite improvements

  • collation of tests performed at multiple different sites/architectures
  • systematic monitoring of job submission to the Grid: Ganga Robots and Dashboard
  • test framework improvement: reduce the testing time by parallel execution of some tests (submission/completion)
  • new tests
    • repository scalability tests with realistic jobs
    • repository compatibility tests (schema checking)
    • exception testing (make the submission fail in different places on purpose and check how the framework reacts)

Ganga LHCb

  • testing: create tests for the most frequent use-cases
  • experiment specific developments

Ganga Atlas

  • testing: create tests for the most frequent use-cases
  • experiment specific developments

Ganga GUI

  • fix obvious problems which are very likely to be reported beyond 2007 => bring GUI to maintenance mode


Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2007-03-16 - JakubMoscicki
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ArdaGrid All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback