CMS - HI collision data recovery #241
Description
To get the information necessary for the reprocessing of the deleted HI collision data:
Query for parent of:
/PPPhoton/Run2013A-PromptReco-v1/RECO
/PPMuon/Run2013A-PromptReco-v1/RECO
/PPMinBias/Run2013A-PromptReco-v1/RECO
/PPJet/Run2013A-PromptReco-v1/RECO
/PPFSQ/Run2013A-PromptReco-v1/RECO
/PAMuon/HIRun2013-PromptReco-v1/RECO
/PAMinBiasUPC/HIRun2013-PromptReco-v1/RECO
/PAMinBias2/HIRun2013-PromptReco-v1/RECO
/PAMinBias1/HIRun2013-PromptReco-v1/RECO
/PAHighPt/HIRun2013-PromptReco-v1/RECO
(e.g. dasgoclient -query="parent dataset=/PAMuon/HIRun2013-PromptReco-v1/RECO")
Record also the runs
(e.g. dasgoclient -query="run dataset=/PAMuon/HIRun2013-PromptReco-v1/RECO")
Get RAW.
Query config for RAW
(e.g. dasgoclient --json -query="config dataset=/PAHighPt/HIRun2013-v1/RAW")
Find configs that in ids_map do not have "DQMConfigCacheID but ConfigCacheID
Find out the differences in configs
If no differences, get the request name of one of the entries.
(e.g. franzoni_pApartialSep28_538HIp2HI_130928_174454_4973)
O&C should be able to start the processing with the information available in ReqMgr
Take note of the runs listed in RunWhitelist: of the ReqMgr query result. If it does not include all those that were queried from DAS above, make note of it when passing the information for reprocessing.