General information

Title	Author(s)	Reference	Paper	Volume, pp	Date
LHCb Software and Conditions Database Cross-Compatibility Tracking: a Graph-Theory Approach	I.Shapoval et al.	Proceedings of IEEE NSS 2012	LHCb-PROC-2012-058 ; CERN-LHCb-PROC-2012-058	7	October 2012
Proposal on LHCb Software and Conditions Database Cross-Compatibility Tracking System: a Graph-Theory Approach	I.Shapoval et al.	LHCb Note	CERN-LHCb-PUB-2012-008	10	June 2012

CondDB compatibility related terminology

CTS - CondDB compatibility tracking system;

The compatibility relations, tracked by the CTS, can be established between the following entities:

• CondDB state - an entity fully identifiable by a CondDB tag (either local, or global);
• Software state - an entity fully identifiable by a software package/project version;
• Real/MC data - an entity fully identifiable by, e.g., a GUID of the data file, or any other wider identifier for a set of files.

CondDB incompatibility criteria/types

A) A CondDB tag is:

• (A1) not usable (job execution fails) with another CondDB tag;
• (A2) usable (no job execution failure) with another CondDB tag BUT such usage is not valid;

B) A software package/project is:

• (B1) not usable with a certain CondDB tag (job execution fails);
• (B2) usable with a certain CondDB tag (no job execution failure) BUT such usage is not valid;

C) A software package/project is:

• (C1) not usable (job execution fails) with certain MC/real data;
• (C2) usable with certain MC/real data BUT such usage is not valid.

D) A CondDB tag is:

• (D) usable with certain MC/real data BUT such usage is not valid.

Internal CondDB incompatibilities

Brunel vs CondDB incompatibilities

DaVinci vs CondDB incompatibilities

Gauss vs CondDB incompatibilities