Conditions Validation Weekly Workflow 2016

Contacts / DQM For Conditions Validation

The contacts for validation can be found from the data validator table. The 2012 weekly conditions validation workflow can be found here.

For 2016, there will be two validation workflows: Fast track and Full. The description of the two workflows can be found in the presentation here and below.

Validation Workflows

Talk by Javier

Full Validation

List of conditions subject to updates:

Condition type	Condition record	HLT or Prompt or Both	HLT/Prompt Test Tags	Affected group(s)	Persons if not in validator table	Update Frequency	Validation Needed	Dataset	DQM quantity	DQM plot example
Pixel	SiPixelLorentzAngleRcd	both	SiPixelLorentzAngle_2015_v2_hltvalidation	Tracking, Alignment	Jelena Luetic	1-2/year	Full	/MuOnia/*/RECO	None (although cluster charge MPV may change slightly), analyzed offline, Summary posted on Hypernews	none
Pixel	SiPixelTemplateDBObjectRcd	both	SiPixelTemplateDBObject_38T_2015_v1_hltvalidation (3.8T)	Tracking, Alignment	Morris Swartz	1-2/year	Full	/MuOnia/*/RECO	None (although cluster charge MPV may change slightly), analyzed offline, Summary posted on Hypernews	none
Pixel	SiPixelGenErrorDBObject	Both	SiPixelGenErrorDBObject_v1_hltvalidation	Tracking, Alignment	Morris Swartz	1-2/year	Full	/MuOnia/*/RECO	None (although cluster charge MPV may change slightly), analyzed offline, Summary posted on Hypernews	none
Strip	SiStripApvGainRcd	Both	SiStripApvGain_v1_hltvalidation	Tracking / TrackerDPG	Kalyanmoy Chatterjee	ASAP (>1/week)	Full	HLTPhysics	Tracking / dEdx / dedxDQMHarm2SO	Tracking / dEdx / dedxDQMHarm2SO
Strip	SiStripApvGain2Rcd	Both	SiStripApvGain2_v1_hltvalidation	Tracking / TrackerDPG	A. Di Mattia, A. Kumar	1/month	Full	ZeroBias, JetHT	Tracking / dEdx / dedxDQMHarm2SO	Tracking / dEdx / dedxDQMHarm2SO
Tracker	TrackerAlignmentRcd	Both	TrackerAlignment_v1_hltvalidation	Tracking	Kalyanmoy Chatterjee	2-3/year	Full	HLTPhysics	?	?
Tracker	TrackerSurfaceDeformationRcd	Both	TrackerSurfaceDeformations_v1_hltvalidation	Tracking	Kalyanmoy Chatterjee	2-3/year	Full	HLTPhysics	?	?
Tracker	TrackerAlignmentErrorExtendedRcd	Both	TrackerAlignmentExtendedErrors_v1_hltvalidation	Tracking	Kalyanmoy Chatterjee	2-3/year	Full	HLTPhysics	?	?
Ecal	EcalPedestalsRcd				?	?	Full	?	?	?
Ecal	EcalLaserAPDPNRatiosRcd	Both	EcalLaserAPDPNRatios_v1_hltvalidation	E/Gamma	Rocky Garg	1/week	Full	MinimumBias	delta(reco energy, hlt energy)	example
Hcal	HcalGainsRcd	?	?	Jet/MET	Henning Kirschenmann/Jane Nachtman	1/month	Full	JetHT	Pt(HLT) resolution - pt spectra in regions	?
Hcal	HcalRespCorrsRcd	Both	HcalRespCorrs_v2_hltvalidation	Jet/MET	Henning Kirschenmann/Jane Nachtman	~1 at startup	Full	?	Pt(HLT) resolution - pt spectra in regions	?
Hcal	HcalTimeCorrsRcd	?	?	Jet/MET	Henning Kirschenmann/Jane Nachtman	~1 at startup	Full	Henning Kirschenmann/Jane Nachtman	rechit timing	?
Hcal	HcalFlagHFDigiTimeParamsRcd	?	?	Jet/MET	Henning Kirschenmann/Jane Nachtman	?	Full	?	?	?
Hcal	HcalRecoParamsRcd	?	HcalRecoParams_v2_hltvalidation	Jet/MET	Henning Kirschenmann/Jane Nachtman	~1 at startup	Full	?	Pt(HLT) resolution - pt spectra in regions , rechit timing	under Hcal/RecHitMonitor_Hcal/diagnostics
Hcal	HcalPedestalsRcd	?	HcalPedestals_v1_hltvalidation	Jet/MET	Henning Kirschenmann/Jane Nachtman	~1 at startup	Full	?	rechit pt spectrum, jet phi-eta map	?
Hcal	HcalZSThresholdsRcd	?	?	Jet/MET	Henning Kirschenmann/Jane Nachtman	?	Full	JetHT
Hcal	HcalLongRecoParamsRcd	?	?	Jet/MET	Henning Kirschenmann/Jane Nachtman	?	Full	?	?	?

Procedure

• AlCa contacts need to make available updated conditions for HLT (Prompt) each (second) Monday morning by noon (12:00 PM)
• AlCa coordination will consider only conditions coming in a timely way to produce a target GT and will notify it through the AlCa hypernews forum hn-cms-alca@cernNOSPAMPLEASE.ch
• RelVal sumbission will follow, to be completed by the following day
• Follow up and sign off through https://cms-pdmv.cern.ch/valdb/
• AlCa Contact will be asked, once the green light has been given, to upload updates to HLT (Prompt) Global Tag

In order for a condition to be considered for updates at HLT (Prompt), it is particularly important that you fill completely the table at the top of this twiki page. Mandatory requirements for an AlCa update to be possible, at HLT (full validation) and Prompt are:

• There is a validator contact person responsible for sign-off of the condition change
• There are plots in the DQM framework to assess the changes

Without these two requirements, it won't be technically possible to submit updates.

Fast Track Validation (and internal)

These are the conditions related to hardware changes, that should go in a short timescale, so that the reconstruction can be consistent:

Test probes

• jobs running without crash in HLT and online DQM
• HLT rates
• HLT CPU timing
• DQM event rate

Procedure

1. The AlCa coordination maintains a GT queue for HLT validation purposes;
2. The AlCaDB contact, once the conditions are produced, submits them to the HLT validation GT queue; he/she updates the unique IOV 1-inf on a validation tag per validation request, exploiting the insertion timestamp
3. The AlCaDB contact, in coordination with the DPG, chooses a run for the test: it must be in the recent past, with the detector performance influencing the condition included
4. The AlCaDB contact sends a request to the AlCa hypernews forum hn-cms-alca@cernNOSPAMPLEASE.ch. See format in the next section.
5. The AlCaDB conveners or the AlCa/HLT contact transmit the request to the consumers of conditions at P5, i.e. online DQM and HLT, by sending an email to cms-tsg-operations and cms-dqm-oncall mailing lists
6. The HLT on call, or the FOG team will replay the run on HiLTOn with the production and test GT, check that no crash occurs, compare HLT rates and CPU timing
7. The online DQM team replays the run on the playback instance, eventually using the look area stream (so the run should be not too old). No crash should be reported.
8. The HLT and DQM on call report on the AlCa hypernews forum hn-cms-alca@cernNOSPAMPLEASE.ch about the outcome of the test. If successful, the AlCaDB conveners or the AlCa/HLT contact give green light for the upload. In case the same tag is used in prompt reconstruction, we should wait for Tier0, too.
9. The AlCaDB contact uploads the new condition on the production tag. The run number is decided by HLT synchronization in dropbox.

Documentation of Weekly Full Validations

Wrap-up of 2015 operations

Talk by Roberta at 2016 PPD planning workshop