Summary of PWG Review Session, December 14, 1999

Update on previous and new computing issues (see previous PWG summaries of May and July).

Summary by T. Trainor and T. Ullrich


Control of the dev to new migration based on autoQA results and group discussion has significantly improved the working environment. Standardized notification of library changes has been implemented with good result.

Recent confusion about the state of the CVS library should disappear with the migration of the new DST format and corresponding software to new. There are apparent problems in defining the current state of the developer version (dev) which must be known for useful debugging and QA. State definition is now being addressed by the QA team. In order to minimize the library workload and ensure optimum library uniformity a move to automated script-based library updates is highly desirable. Updates should soon include Online libraries as well.

Grand Challenge

This effort has been identified as exclusively HPSS related. Thus, impact of GC on disk-resident analysis, the bulk of offline physics analysis in the first year, is seen to be negligible for the foreseeable future. It would be desirable if resources previously directed toward HPSS-related GC development could be temporarily diverted to immediate year-1 software goals, especially the data catalog and TagDB.

Data Bases

Some MySQL data bases are now coming on line, albeit much delayed from expectations formed in May, July and October. DBs continue to be on several software critical paths. It is required now to prioritize DB effort to insure that the most essential elements are in place for first collisions. The TagDB is a critical item for offline analysis, as are calibration and geometry DBs needed for tracking.


Good progress on several fronts: improved consistency between GSTAR model and apparatus, consistent definition of hits for difficult track geometries, updated event menu for MDC3 production, increasing use of mevsim and several standard track densities for QA and general tracking diagnostics.


Great strides in this area in recent months. Script-based monitoring of library software quality has been the major recent emphasis, with autoQA of small nightly productions. In the near future this system must be expanded to general DST production QA with quality-cut criteria defined by experts and PWGs, and to Online QA for monitoring STAR detector performance via DST output. A major near-term goal is to encourage use of the autoQA mechanism routinely in code development by individual workers <before> CVS submissions to speed code development and improve library quality.

Offline analysis production management

PWG operation on CAS requires a job control package which integrates data cataloguing, maker chain configuring and load balancing. An approximation to this facility has recently been implemented by Torre Wenaus, which does not yet incorporate load balancing via LSF.

PWG Common Interests

Separate Working Groups