Skip to content

Commit ec75b8b

Browse files
katilpkatilp
committed
cms-validated-runs_HIRun1.json: add HI2013 related records
1 parent 01b2400 commit ec75b8b

File tree

1 file changed

+301
-1
lines changed

1 file changed

+301
-1
lines changed

‎cernopendata/modules/fixtures/data/records/cms-validated-runs-HIRun1.json

Lines changed: 301 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -552,5 +552,305 @@
552552
}
553553
]
554554
}
555-
}
555+
},
556+
{
557+
"abstract": {
558+
"description": "<p>This file describes which luminosity sections in which runs are considered good and should be processed.</p><p>This list covers 5.02TeV proton-Pb heavy-ion collision data taken in 2013. HIRun2013 is between run numbers 210498 and 211631.</p>"
559+
},
560+
"accelerator": "CERN-LHC",
561+
"collaboration": {
562+
"name": "CMS collaboration"
563+
},
564+
"collections": [
565+
"CMS-Validated-Runs",
566+
"CMS-Validation-Utilities"
567+
],
568+
"collision_information": {
569+
"energy": "5.02TeV",
570+
"type": "pPb"
571+
},
572+
"date_created": [
573+
"2013"
574+
],
575+
"date_published": "2023",
576+
"experiment": "CMS",
577+
"license": {
578+
"attribution": "CC0"
579+
},
580+
"publisher": "CERN Open Data Portal",
581+
"recid": "14216",
582+
"run_period": [
583+
"HIRun2013"
584+
],
585+
"title": "CMS list of validated runs Cert_210498-211631_HI_PromptReco_Collisions13_JSON_v2.txt",
586+
"title_additional": "CMS list of validated runs for 5.02TeV proton-Pb heavy-ion collision data taken in 2013",
587+
"type": {
588+
"primary": "Environment",
589+
"secondary": [
590+
"Validation"
591+
]
592+
},
593+
"usage": {
594+
"description": "<p>Add the following lines in the configuration file for a cmsRun job: <br /> <pre> import FWCore.ParameterSet.Config as cms</pre><pre> import FWCore.PythonUtilities.LumiList as LumiList</pre><pre> goodJSON = 'Cert_210498-211631_HI_PromptReco_Collisions13_JSON_v2.txt'</pre><pre> myLumis = LumiList.LumiList(filename = goodJSON).getCMSSWString().split(',') </pre></p><p> Add the file path if needed in the file name.</p><p> Add the following statements after the <code>process.source</code> input file definition: <br /><pre> process.source.lumisToProcess = cms.untracked.VLuminosityBlockRange()</pre><pre> process.source.lumisToProcess.extend(myLumis)</pre></p><p>Note that the two last statements must be placed after the <code>process.source</code> statement defining the input files.</p>"
595+
},
596+
"validation": {
597+
"description": "During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:",
598+
"links": [
599+
{
600+
"description": "The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future",
601+
"url": "https://www.epj-conferences.org/articles/epjconf/pdf/2019/19/epjconf_chep2018_02003.pdf"
602+
}
603+
]
604+
}
605+
},
606+
{
607+
"abstract": {
608+
"description": "<p>This file describes which luminosity sections in which runs are considered good and should be processed, for analyses requiring only valid muons.</p><p>This list covers 5.02TeV proton-Pb heavy-ion collision data taken in 2013. HIRun2013 is between run numbers 210498 and 211631.</p>"
609+
},
610+
"accelerator": "CERN-LHC",
611+
"collaboration": {
612+
"name": "CMS collaboration"
613+
},
614+
"collections": [
615+
"CMS-Validated-Runs",
616+
"CMS-Validation-Utilities"
617+
],
618+
"collision_information": {
619+
"energy": "5.02TeV",
620+
"type": "pPb"
621+
},
622+
"date_created": [
623+
"2013"
624+
],
625+
"date_published": "2023",
626+
"experiment": "CMS",
627+
"license": {
628+
"attribution": "CC0"
629+
},
630+
"publisher": "CERN Open Data Portal",
631+
"recid": "14217",
632+
"run_period": [
633+
"HIRun2013"
634+
],
635+
"title": "CMS list of validated runs Cert_210498-211631_HI_PromptReco_Collisions13_JSON_MuonPhys_v2.txt",
636+
"title_additional": "CMS list of validated runs for 5.02TeV proton-Pb heavy-ion collision data taken in 2013, only valid muons",
637+
"type": {
638+
"primary": "Environment",
639+
"secondary": [
640+
"Validation"
641+
]
642+
},
643+
"usage": {
644+
"description": "<p>Add the following lines in the configuration file for a cmsRun job: <br /> <pre> import FWCore.ParameterSet.Config as cms</pre><pre> import FWCore.PythonUtilities.LumiList as LumiList</pre><pre> goodJSON = 'Cert_210498-211631_HI_PromptReco_Collisions13_JSON_MuonPhys_v2.txt'</pre><pre> myLumis = LumiList.LumiList(filename = goodJSON).getCMSSWString().split(',') </pre></p><p> Add the file path if needed in the file name.</p><p> Add the following statements after the <code>process.source</code> input file definition: <br /><pre> process.source.lumisToProcess = cms.untracked.VLuminosityBlockRange()</pre><pre> process.source.lumisToProcess.extend(myLumis)</pre></p><p>Note that the two last statements must be placed after the <code>process.source</code> statement defining the input files.</p>"
645+
},
646+
"validation": {
647+
"description": "During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:",
648+
"links": [
649+
{
650+
"description": "The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future",
651+
"url": "https://www.epj-conferences.org/articles/epjconf/pdf/2019/19/epjconf_chep2018_02003.pdf"
652+
}
653+
]
654+
}
655+
},
656+
{
657+
"abstract": {
658+
"description": "<p>This file describes which luminosity sections in which runs are considered good and should be processed.</p><p>This list covers 2.76TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2013. Run2013A is between run numbers 211739 and 211831.</p>"
659+
},
660+
"accelerator": "CERN-LHC",
661+
"collaboration": {
662+
"name": "CMS collaboration"
663+
},
664+
"collections": [
665+
"CMS-Validated-Runs",
666+
"CMS-Validation-Utilities"
667+
],
668+
"collision_information": {
669+
"energy": "2.76TeV",
670+
"type": "pp"
671+
},
672+
"date_created": [
673+
"2013"
674+
],
675+
"date_published": "2023",
676+
"experiment": "CMS",
677+
"license": {
678+
"attribution": "CC0"
679+
},
680+
"publisher": "CERN Open Data Portal",
681+
"recid": "14218",
682+
"run_period": [
683+
"Run2013A"
684+
],
685+
"title": "CMS list of validated runs Cert_211739-211831_2760GeV_PromptReco_Collisions13_JSON.txt",
686+
"title_additional": "CMS list of validated runs for 2.76TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2013",
687+
"type": {
688+
"primary": "Environment",
689+
"secondary": [
690+
"Validation"
691+
]
692+
},
693+
"usage": {
694+
"description": "<p>Add the following lines in the configuration file for a cmsRun job: <br /> <pre> import FWCore.ParameterSet.Config as cms</pre><pre> import FWCore.PythonUtilities.LumiList as LumiList</pre><pre> goodJSON = 'Cert_211739-211831_2760GeV_PromptReco_Collisions13_JSON.txt'</pre><pre> myLumis = LumiList.LumiList(filename = goodJSON).getCMSSWString().split(',') </pre></p><p> Add the file path if needed in the file name.</p><p> Add the following statements after the <code>process.source</code> input file definition: <br /><pre> process.source.lumisToProcess = cms.untracked.VLuminosityBlockRange()</pre><pre> process.source.lumisToProcess.extend(myLumis)</pre></p><p>Note that the two last statements must be placed after the <code>process.source</code> statement defining the input files.</p>"
695+
},
696+
"validation": {
697+
"description": "During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:",
698+
"links": [
699+
{
700+
"description": "The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future",
701+
"url": "https://www.epj-conferences.org/articles/epjconf/pdf/2019/19/epjconf_chep2018_02003.pdf"
702+
}
703+
]
704+
}
705+
},
706+
{
707+
"abstract": {
708+
"description": "<p>This file describes which luminosity sections in which runs are considered good and should be processed, for analyses requiring only valid muons.</p><p>This list covers 2.76TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2013. Run2013A is between run numbers 211739 and 211831.</p>"
709+
},
710+
"accelerator": "CERN-LHC",
711+
"collaboration": {
712+
"name": "CMS collaboration"
713+
},
714+
"collections": [
715+
"CMS-Validated-Runs",
716+
"CMS-Validation-Utilities"
717+
],
718+
"collision_information": {
719+
"energy": "2.76TeV",
720+
"type": "pp"
721+
},
722+
"date_created": [
723+
"2013"
724+
],
725+
"date_published": "2023",
726+
"experiment": "CMS",
727+
"license": {
728+
"attribution": "CC0"
729+
},
730+
"publisher": "CERN Open Data Portal",
731+
"recid": "14219",
732+
"run_period": [
733+
"Run2013A"
734+
],
735+
"title": "CMS list of validated runs Cert_211739-211831_2760GeV_PromptReco_Collisions13_JSON_MuonPhys.txt",
736+
"title_additional": "CMS list of validated runs for 2.76TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2013, only valid muons",
737+
"type": {
738+
"primary": "Environment",
739+
"secondary": [
740+
"Validation"
741+
]
742+
},
743+
"usage": {
744+
"description": "<p>Add the following lines in the configuration file for a cmsRun job: <br /> <pre> import FWCore.ParameterSet.Config as cms</pre><pre> import FWCore.PythonUtilities.LumiList as LumiList</pre><pre> goodJSON = 'Cert_211739-211831_2760GeV_PromptReco_Collisions13_JSON_MuonPhys.txt'</pre><pre> myLumis = LumiList.LumiList(filename = goodJSON).getCMSSWString().split(',') </pre></p><p> Add the file path if needed in the file name.</p><p> Add the following statements after the <code>process.source</code> input file definition: <br /><pre> process.source.lumisToProcess = cms.untracked.VLuminosityBlockRange()</pre><pre> process.source.lumisToProcess.extend(myLumis)</pre></p><p>Note that the two last statements must be placed after the <code>process.source</code> statement defining the input files.</p>"
745+
},
746+
"validation": {
747+
"description": "During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:",
748+
"links": [
749+
{
750+
"description": "The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future",
751+
"url": "https://www.epj-conferences.org/articles/epjconf/pdf/2019/19/epjconf_chep2018_02003.pdf"
752+
}
753+
]
754+
}
755+
},
756+
{
757+
"abstract": {
758+
"description": "<p>This file describes which luminosity sections in which runs are considered good and should be processed.</p><p>This list covers 5.02TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2015. Run2015E is between run numbers 261445 and 262328.</p>"
759+
},
760+
"accelerator": "CERN-LHC",
761+
"collaboration": {
762+
"name": "CMS collaboration"
763+
},
764+
"collections": [
765+
"CMS-Validated-Runs",
766+
"CMS-Validation-Utilities"
767+
],
768+
"collision_information": {
769+
"energy": "5.02TeV",
770+
"type": "pp"
771+
},
772+
"date_created": [
773+
"2015"
774+
],
775+
"date_published": "2023",
776+
"experiment": "CMS",
777+
"license": {
778+
"attribution": "CC0"
779+
},
780+
"publisher": "CERN Open Data Portal",
781+
"recid": "14212",
782+
"run_period": [
783+
"Run2015E"
784+
],
785+
"title": "CMS list of validated runs Cert_262081-262328_5TeV_PromptReco_Collisions15_25ns_JSON.txt",
786+
"title_additional": "CMS list of validated runs for 5.02TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2015",
787+
"type": {
788+
"primary": "Environment",
789+
"secondary": [
790+
"Validation"
791+
]
792+
},
793+
"usage": {
794+
"description": "<p>Add the following lines in the configuration file for a cmsRun job: <br /> <pre> import FWCore.ParameterSet.Config as cms</pre><pre> import FWCore.PythonUtilities.LumiList as LumiList</pre><pre> goodJSON = 'Cert_262081-262328_5TeV_PromptReco_Collisions15_25ns_JSON.txt'</pre><pre> myLumis = LumiList.LumiList(filename = goodJSON).getCMSSWString().split(',') </pre></p><p> Add the file path if needed in the file name.</p><p> Add the following statements after the <code>process.source</code> input file definition: <br /><pre> process.source.lumisToProcess = cms.untracked.VLuminosityBlockRange()</pre><pre> process.source.lumisToProcess.extend(myLumis)</pre></p><p>Note that the two last statements must be placed after the <code>process.source</code> statement defining the input files.</p>"
795+
},
796+
"validation": {
797+
"description": "During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:",
798+
"links": [
799+
{
800+
"description": "The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future",
801+
"url": "https://www.epj-conferences.org/articles/epjconf/pdf/2019/19/epjconf_chep2018_02003.pdf"
802+
}
803+
]
804+
}
805+
},
806+
{
807+
"abstract": {
808+
"description": "<p>This file describes which luminosity sections in which runs are considered good and should be processed, for analyses requiring only valid muons.</p><p>This list covers 5.02TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2015. Run2015E is between run numbers 261445 and 262328.</p>"
809+
},
810+
"accelerator": "CERN-LHC",
811+
"collaboration": {
812+
"name": "CMS collaboration"
813+
},
814+
"collections": [
815+
"CMS-Validated-Runs",
816+
"CMS-Validation-Utilities"
817+
],
818+
"collision_information": {
819+
"energy": "5.02TeV",
820+
"type": "pp"
821+
},
822+
"date_created": [
823+
"2015"
824+
],
825+
"date_published": "2023",
826+
"experiment": "CMS",
827+
"license": {
828+
"attribution": "CC0"
829+
},
830+
"publisher": "CERN Open Data Portal",
831+
"recid": "14213",
832+
"run_period": [
833+
"Run2015E"
834+
],
835+
"title": "CMS list of validated runs Cert_262081-262328_5TeV_PromptReco_Collisions15_25ns_JSON_MuonPhys.txt",
836+
"title_additional": "CMS list of validated runs for 5.02TeV proton-proton collision data, needed as reference data for heavy-ion data analysis, taken in 2015, only valid muons",
837+
"type": {
838+
"primary": "Environment",
839+
"secondary": [
840+
"Validation"
841+
]
842+
},
843+
"usage": {
844+
"description": "<p>Add the following lines in the configuration file for a cmsRun job: <br /> <pre> import FWCore.ParameterSet.Config as cms</pre><pre> import FWCore.PythonUtilities.LumiList as LumiList</pre><pre> goodJSON = 'Cert_262081-262328_5TeV_PromptReco_Collisions15_25ns_JSON_MuonPhys.txt'</pre><pre> myLumis = LumiList.LumiList(filename = goodJSON).getCMSSWString().split(',') </pre></p><p> Add the file path if needed in the file name.</p><p> Add the following statements after the <code>process.source</code> input file definition: <br /><pre> process.source.lumisToProcess = cms.untracked.VLuminosityBlockRange()</pre><pre> process.source.lumisToProcess.extend(myLumis)</pre></p><p>Note that the two last statements must be placed after the <code>process.source</code> statement defining the input files.</p>"
845+
},
846+
"validation": {
847+
"description": "During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:",
848+
"links": [
849+
{
850+
"description": "The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future",
851+
"url": "https://www.epj-conferences.org/articles/epjconf/pdf/2019/19/epjconf_chep2018_02003.pdf"
852+
}
853+
]
854+
}
855+
}
556856
]

0 commit comments

Comments
 (0)