L1 Configuration Objects (CondFormats/L1TObjects)

Description of columns:

• OMDS: the record is implemented in OMDS.
• O2O: the code for reading keys and payload data from OMDS and constructing the C++ objects exists in CVS and it is functional .
• Key: Objects whose keys are not coupled to the TSC key are handled by the Run Settings (RS) mechanism, as described in SWGuideL1EmulatorConfiguration and SWGuideL1CondDBTools. Some objects are not produced from OMDS data but from trivial producers in CMSSW (Triv) -- this is only appropriate for objects that will never change.
• Blob: Objects written out with blob streaming have a corresponding xml file in CondFormats/L1TObjects/xml, which must be updated every time the memory layout of the object changes.
• Status: among other things, it should be noted whether the code is validated or not validated. Validation means:
  • There exists a test EDAnalyzer in CVS that reads configuration objects from EventSetup and prints out their contents. A link to this validation code in WebCVS should also be included.
  • This EDAnalyzer has been used in the test job (https://twiki.cern.ch/twiki/bin/view/CMS/SWGuideL1O2OTestJob) and the output compared (by hand) to the configuration data in OMDS.

CSCTF

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1MuCSCPtLutRcd	L1MuCSCPtLut		no		yes
L1MuCSCTFAlignmentRcd	L1MuCSCTFAlignment	Yes	Yes		yes
L1MuCSCTFConfigurationRcd	L1MuCSCTFConfiguration	yes	yes	TSC	no

• Status: CONTENT VALIDATED, Dayong Wang Dec.1 2008

DTTF

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1MuDTEtaPatternLutRcd	L1MuDTEtaPatternLut	n/a	yes	TSC	yes
L1MuDTExtLutRcd	L1MuDTExtLut	n/a	yes	TSC	yes
L1MuDTPhiLutRcd	L1MuDTPhiLut	n/a	yes	TSC	yes
L1MuDTPtaLutRcd	L1MuDTPtaLut	n/a	yes	TSC	yes
L1MuDTQualPatternLutRcd	L1MuDTQualPatternLut	n/a	yes	TSC	yes
L1MuDTTFParametersRcd	L1MuDTTFParameters	yes	yes	TSC	no	Parameters
L1MuDTTFMasksRcd	L1MuDTTFMasks	yes	yes	RS	no	Channel masks

• Special handling: The LUTs are not stored in OMDS but are part of the firmware and are programmed directly into the boards. They are expected to change very infrequently. So, the LUT payloads will be written to ORCON by hand, using the fake producers (L1ConfigWriteSinglePayload_cfg.py), and this must be done every time the LUTs change. We will associate with each version a LUT key that is stored in OMDS and is coupled to the TSC key.
• Status: CONTENT VALIDATED 18 May 2009 JorgeTroconiz

RPC

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1RPCConfigRcd	L1RPCConfig	n/a	yes	TSC	yes
L1RPCConeDefinitionRcd	L1RPCConeDefinition	n/a	yes	TSC	yes

• Special handling: O2O for most of the RPC trigger configuration is performed by the RPC CMS.PopCon application. The exceptions are the objects in the table above, for which all possible versions will be cached in ORCON beforehand. Since the key for this object is coupled to the TSC key, it is straightforward to incorporate this object into the L1-O2O scheme. We use L1ConfigWriteSinglePayload_cfg.py to write the payload cache before data-taking begins.
• Status: CONTENT NOT VALIDATED

GMT

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1MuGMTChannelMaskRcd	L1MuGMTChannelMask	yes	yes	RS	no
L1MuGMTParametersRcd	L1MuGMTParameters	yes	yes	TSC	no
L1MuGMTScalesRcd	L1MuGMTScales		no	TSC	yes	Internal GMT geometry
L1MuTriggerPtScaleRcd	L1MuTriggerPtScale	yes	yes	TSC	yes
L1MuTriggerScalesRcd	L1MuTriggerScales	yes	yes	TSC	yes	GMT input and output geometry

• Status: CONTENT VALIDATED IvanMikulec 1 Apr 2009

RCT

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1CaloEcalScaleRcd	L1CaloEcalScale	yes	yes	TSC	yes	Input scale to RCT
L1CaloHcalScaleRcd	L1CaloHcalScale	yes	yes	TSC	yes	Input scale to RCT
L1EmEtScaleRcd	L1CaloEtScale	yes	yes	TSC	yes	Output scale from RCT
L1RCTChannelMaskRcd	L1RCTChannelMask	yes	yes	RS	yes
L1RCTParametersRcd	L1RCTParameters	yes	yes	TSC	yes	Updated to include new Calib constants

• Status: RunSettings Validated Jonathan Efron March 11, 2009 Updated October 25, 2007 TSC Validate Jonathan Efron March 25, 2009

GCT

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1GctJetFinderParamsRcd	L1GctJetFinderParams	yes	yes	TSC	no	Jet finder algorithm parameters
L1GctChannelMaskRcd	L1GctChannelMask	yes	yes	RS	yes	masked channel list
L1JetEtScaleRcd	L1CaloEtScale	yes	yes	TSC	yes	Jet Et scale
L1HtMissScaleRcd	L1CaloEtScale	no	no	TSC	no?	HtMiss scale
L1HfRingEtScaleRcd	L1CaloEtScale	yes	yes	TSC	no?	HF ring sum Et scale
L1GctHfLutSetupRcd	L1GctHfLutSetup		no	TSC	yes	obsolete
L1GctJetCounterNegativeEtaRcd	L1GctJetCounterSetup		no	TSC	yes	obsolete
L1GctJetCounterPositiveEtaRcd	L1GctJetCounterSetup		no	TSC	yes	obsolete
L1GctJetCalibFunRcd	L1GctJetEtCalibrationFunction		no	TSC	yes	obsolete

• Status: updated JimBrooke - 06 Mar 2009

Calo (RCT and GCT)

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1CaloGeometryRecord	L1CaloGeometry		no	TSC	yes

• Status: CONTENT NOT VALIDATED

GT

Record	C++ Type	OMDS	O2O	Key	Blob	Analyzer	Description
L1GtBoardMapsRcd	L1GtBoardMaps	n/a	n/a	Triv	yes	yes	n/a hardware
L1GtParametersRcd	L1GtParameters	yes	yes	TSC	no	yes
L1GtPrescaleFactorsAlgoTrigRcd	L1GtPrescaleFactors	yes	yes	RS	yes	yes
L1GtPrescaleFactorsTechTrigRcd	L1GtPrescaleFactors	yes	yes	RS	yes	yes
L1GtPsbSetupRcd	L1GtPsbSetup	yes	yes	TSC	yes	yes
L1GtStableParametersRcd	L1GtStableParameters	n/a	n/a	Triv	yes	yes	n/a hardware
L1GtTriggerMaskAlgoTrigRcd	L1GtTriggerMask	yes	yes	RS	yes	yes
L1GtTriggerMaskTechTrigRcd	L1GtTriggerMask	yes	yes	RS	yes	yes
L1GtTriggerMaskVetoAlgoTrigRcd	L1GtTriggerMask	n/a	n/a	Triv	yes	yes	n/a hardware
L1GtTriggerMaskVetoTechTrigRcd	L1GtTriggerMask	yes	yes	RS	yes	yes
L1GtTriggerMenuRcd	L1GtTriggerMenu	yes	yes	TSC	yes	yes	documentation

• Global Tag test cfg file: L1GtGlobalTagTest_cfg.py
• *GT Configuration documentation link
• Status: Content validated -- VasileGhete - 02 Apr 2009

O2O

Record	C++ Type	OMDS	O2O	Key	Blob	Description
L1TriggerKeyRcd	L1TriggerKey	yes	yes	TSC	yes
L1TriggerKeyListRcd	L1TriggerKeyList	n/a	n/a	n/a	yes

• Status: validated 19 Feb 2009 WernerSun (l1o2otestanalyzer_cfg.py)

-- WernerSun - 01 Oct 2008