The LHC Computing Grid Project

The LHC Computing Grid Project (LCG)

RTAG8 (LCG Blueprint) June 2002

Material circulated in the RTAG (now obsolete): please protect it via the usual SC2 password (ask Lucia Silvestris)

Chair: Lucia Silvestris

Mandate:

Write the product specification for detector geometry and materials description services.

Specify scope: e.g. Services to define, provide transient access to, and store the geometry and materials

descriptions required by simulation, reconstruction, analysis, online and event display applications,

with the various descriptions using the same information source

Identify requirements including end-user needs such as ease and naturalness of use of the description tools,

readability and robustness against errors e.g. provision for named constants and derived quantities

Explore commonality of persistence requirements with conditions data management

Interaction of the DD with a conditions DB. In that context versioning and ‘configuration management’ of the detector description, coherence issues.

Identify where experiments have differing requirements and examine how to address them within common tools

Address migration from current tools

SC2-mandated schedule: Initial report July 5, Final report Aug 2

Makeup: Experiment representatives, CERN IT/API, Experts, additional members at chair's discretion

Members and experts:

Lucia Silvestris (chair), Andrei Gheata (Alice), Steve Golfdfarb (Atlas), Martin Liendl (CMS), Sebastien Ponce (LHCb), Radovan Chytracek (IT/API), Joe Boudreau (expert), Torre Wenaus (Ex-officio)

Guidance: The result of the RTAG should be the detailed description of use cases that could be implemented within the framework of the four experiments

	Write the product specification for detector geometry and materials description services.
	Specify scope: e.g. Services to define, provide transient access to, and store the geometry and materials descriptions required by simulation, reconstruction, analysis, online and event display applications, with the various descriptions using the same information source
	Identify requirements including end-user needs such as ease and naturalness of use of the description tools, readability and robustness against errors e.g. provision for named constants and derived quantities
	Explore commonality of persistence requirements with conditions data management
	Interaction of the DD with a conditions DB. In that context versioning and ‘configuration management’ of the detector description, coherence issues.
	Identify where experiments have differing requirements and examine how to address them within common tools
	Address migration from current tools