Difference: CondDBIncompatibilities (2 vs. 3)

Revision 32012-10-08 - IllyaShapoval

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
-- IllyaShapoval - 08-Oct-2012
Line: 12 to 12
  CTS - CondDB compatibility tracking system;
Changed:
<
<
The compatibility relations can be established between the following entities:
  • Software states - an entity which is fully defined by a CondDB tag (either local, or global);
  • CondDB states - an entity which is fully defined by a software package/project version;
  • Physics data.
>
>
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

Changed:
<
<
A1) Certain CondDB tag can not be used together with another CondDB tag (the execution fails);
>
>
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.
 
Changed:
<
<
A2) Certain CondDB tag can not be used together with another CondDB tag (no failure, BUT the usage is not valid);

B1) Certain software package/project can not run with a certain CondDB tag (the execution fails);

B2) Certain software package/project can run with a certain CondDB tag (no failure) BUT the result is not correct/expected for some reason;

C1) Certain software package/project can not run on a specific MC/real data (the execution fails);

C2) Certain software package/project can run on a specific MC/real data BUT the result is not valid.

>
>
D) A CondDB tag is:
  • (D) usable with certain MC/real data BUT such usage is not valid.
 

Internal CondDB incompatibilities

Changed:
<
<
CondDB DDDB tag CondDB LHCBCOND tag CondDB SIMCOND tag CondDB DQFLAGS tag Incompatibility type Reason
>
>
CondDB DDDB tag CondDB LHCBCOND tag CondDB SIMCOND tag CondDB DQFLAGS tag Incompatibility type Reason Contact person
 

Brunel vs CondDB incompatibilities

Changed:
<
<
Package name Package version Brunel version CondDB DDDB tag CondDB LHCBCOND tag Incompatibility type Reason
>
>
Package name Package version Brunel version CondDB DDDB tag CondDB LHCBCOND tag Incompatibility type Reason Contact person
 

DaVinci vs CondDB incompatibilities

Changed:
<
<
Package name Package version DaVinci version CondDB DDDB tag CondDB LHCBCOND tag Incompatibility type Reason
>
>
Package name Package version DaVinci version CondDB DDDB tag CondDB LHCBCOND tag Incompatibility type Reason Contact person
 

Gauss vs CondDB incompatibilities

Changed:
<
<
Package name Package version Gauss version CondDB DDDB tag CondDB SIMCOND tag Incompatibility type Reason
>
>
Package name Package version Gauss version CondDB DDDB tag CondDB SIMCOND tag Incompatibility type Reason Contact person
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback