Skip to content

Commit

Permalink
Update jade-data.json
Browse files Browse the repository at this point in the history
  • Loading branch information
@andriish
andriish authored Mar 5, 2024
1 parent c51e983 commit 90fae4d
Showing 1 changed file with 20 additions and 214 deletions.
234 changes: 20 additions & 214 deletions cernopendata/modules/fixtures/data/records/jade-data.json
View file
Original file line number Diff line number Diff line change
@@ -1,270 +1,76 @@
[
{
"abstract": {
"description": "<p>HICorePhysics primary dataset from the 2.76 TeV Pb-Pb run of 2010.</p> <p> The list of validated runs, which must be applied to all analyses, either with the full validation or for an analysis requiring only muons, can be found in</p>",
"description": "<p>JADE real data</p>",
"links": [
{
"description": "Validated runs, full validation",
"description": "All JADE runs",
"recid": "14202"
},
{
"description": "Validated runs, muons only",
"recid": "14203"
}
]
},
"accelerator": "CERN-LHC",
"accelerator": "DESY-PETRA",
"collaboration": {
"name": "CMS collaboration",
"name": "JADE collaboration",
"recid": "450"
},
"collections": [
"CMS-Primary-Datasets"
"JADE-Primary-Datasets"
],
"collision_information": {
"energy": "2.76TeV",
"type": "PbPb"
"energy": "12GeV",
"type": "e+e-"
},
"date_created": [
"2010"
"1986"
],
"date_published": "2020",
"date_reprocessed": "2010",
"date_published": "2024",
"date_reprocessed": "1986",
"distribution": {
"formats": [
"root",
"reco"
"raw"
],
"number_events": 5964915,
"number_files": 5436,
"size": 19336281599911
"number_events": 99999,
"number_files": 99999,
"size": 9999999999
},
"doi": "10.7483/OPENDATA.9S5F.BY3B",
"experiment": [
"CMS"
"JADE"
],
"files": [
{
"checksum": "adler32:44e5147f",
"size": 1575978,
"type": "index.json",
"uri": "root://eospublic.cern.ch//eos/opendata/cms/hidata/HIRun2010/HICorePhysics/RECO/PromptReco-v3/file-indexes/CMS_HIRun2010_HICorePhysics_PromptReco-v3_RECO_file_index.json"
},
{
"checksum": "adler32:12b0ad66",
"size": 799092,
"type": "index.txt",
"uri": "root://eospublic.cern.ch//eos/opendata/cms/hidata/HIRun2010/HICorePhysics/RECO/PromptReco-v3/file-indexes/CMS_HIRun2010_HICorePhysics_PromptReco-v3_RECO_file_index.txt"
}
],
"keywords": [
"heavy-ion physics"
"e+e- physics"
],
"license": {
"attribution": "CC0"
},
"methodology": {
"description": "<p>During the heavy-ion run, events were directed to this primary dataset through several different <a href=\"/docs/cms-guide-trigger-system#hlt-trigger-path-definitions\">HLT trigger paths</a>, which can be studied and selected with the example usage code linked below. The possible HLT trigger paths in this dataset (the list may be incomplete): <br/>HLT_HIJet35U_Core <br/>HLT_HIJet50U_Core <br/>HLT_HIJet75U_Core <br/>HLT_HIJet90U_Core <br/>HLT_HIL2DoubleMu3_Core <br/>HLT_HIL2Mu20_Core <br/>HLT_HIL2Mu5Tight_Core <br/>HLT_HIMinBiasHfOrBSC_Core <br/>HLT_HIPhoton15_Cleaned_Core <br/>HLT_HIPhoton20_Cleaned_Core <br/>HLT_HIPhoton30_Cleaned_Core </p>"
"description": "<p> During the experiment, the raw data was written to the tapes.</p>"
},
"publisher": "CERN Open Data Portal",
"recid": "14010",
"relations": [
{
"title": "/HICorePhysics/HIRun2010-v1/RAW",
"type": "isChildOf"
}
],
"run_period": [
"HIRun2010"
],
"system_details": {
"container_images": [
{
"name": "docker.io/cmsopendata/cmssw_3_9_2_patch5-slc5_amd64_gcc434:latest",
"registry": "dockerhub"
},
{
"name": "gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_3_9_2_patch5-slc5_amd64_gcc434:latest",
"registry": "gitlab"
}
],
"global_tag": "GR_R_39X_V6B::All",
"release": "CMSSW_3_9_2_patch5"
},
"title": "/HICorePhysics/HIRun2010-PromptReco-v3/RECO",
"title_additional": "HICorePhysics primary dataset in RECO format from the 2.76 TeV Pb-Pb run of 2010 (/HICorePhysics/HIRun2010-PromptReco-v3/RECO)",
"type": {
"primary": "Dataset",
"secondary": [
"Collision"
]
},
"usage": {
"description": "You can access these data through the CMS Open Data container or the CMS Virtual Machine. See the instructions for setting up one of the two alternative environments and getting started with CMS heavy-ion data data in",
"links": [
{
"description": "Running CMS analysis code using Docker",
"url": "/docs/cms-guide-docker"
},
{
"description": "How to install the CMS Virtual Machine",
"url": "/docs/cms-virtual-machine-2010"
},
{
"description": "Usage example for CMS 2010 heavy-ion data",
"recid": "466"
}
]
},
"validation": {
"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:",
"links": [
{
"description": "CMS data quality monitoring: Systems and experiences",
"url": "http://iopscience.iop.org/1742-6596/219/7/072020/pdf/1742-6596_219_7_072020.pdf"
},
{
"description": "The CMS Data Quality Monitoring software experience and future improvements",
"url": "http://cds.cern.ch/record/1631039/files/CR2013_418.pdf"
},
{
"description": "The CMS data quality monitoring software: experience and future prospects",
"url": "http://iopscience.iop.org/1742-6596/513/3/032024/pdf/1742-6596_513_3_032024.pdf"
}
]
}
},
{
"abstract": {
"description": "<p>HIAllPhysics primary dataset from the 2.76 TeV Pb-Pb run of 2010.</p> <p> The list of validated runs, which must be applied to all analyses, either with the full validation or for an analysis requiring only muons, can be found in</p>",
"links": [
{
"description": "Validated runs, full validation",
"recid": "14202"
},
{
"description": "Validated runs, muons only",
"recid": "14203"
}
]
},
"accelerator": "CERN-LHC",
"collaboration": {
"name": "CMS collaboration",
"recid": "450"
},
"collections": [
"CMS-Primary-Datasets"
],
"collision_information": {
"energy": "2.76TeV",
"type": "PbPb"
},
"date_created": [
"2010"
],
"date_published": "2020",
"date_reprocessed": "2010",
"distribution": {
"formats": [
"root",
"reco"
],
"number_events": 75482193,
"number_files": 28954,
"size": 166030973333340
},
"doi": "10.7483/OPENDATA.305G.POEC",
"experiment": [
"CMS"
],
"files": [
{
"checksum": "adler32:cb873e1e",
"size": 8963908,
"type": "index.json",
"uri": "root://eospublic.cern.ch//eos/opendata/cms/hidata/HIRun2010/HIAllPhysics/RECO/ZS-v2/file-indexes/CMS_HIRun2010_HIAllPhysics_ZS-v2_RECO_file_index.json"
},
{
"checksum": "adler32:b27bab6d",
"size": 4285665,
"type": "index.txt",
"uri": "root://eospublic.cern.ch//eos/opendata/cms/hidata/HIRun2010/HIAllPhysics/RECO/ZS-v2/file-indexes/CMS_HIRun2010_HIAllPhysics_ZS-v2_RECO_file_index.txt"
}
],
"keywords": [
"heavy-ion physics"
],
"license": {
"attribution": "CC0"
},
"methodology": {
"description": "<p>During the heavy-ion run, events were directed to this primary dataset through several different <a href=\"/docs/cms-guide-trigger-system#hlt-trigger-path-definitions\">HLT trigger paths</a>, which can be studied and selected with the example usage code linked below. The possible HLT trigger paths in this dataset (the list may be incomplete): <br/>HLT_HIBptxXOR <br/>HLT_HICentralityVeto <br/>HLT_HIDoublePhoton5_CEP_L1R <br/>HLT_HIJet35U <br/>HLT_HIJet50U <br/>HLT_HIJet75U <br/>HLT_HIJet90U <br/>HLT_HIL1Algo_BptxXOR_BSC_OR <br/>HLT_HIL1DoubleMuOpen <br/>HLT_HIL1SingleMu3 <br/>HLT_HIL1SingleMu5 <br/>HLT_HIL1SingleMu7 <br/>HLT_HIL2DoubleMu0 <br/>HLT_HIL2DoubleMu3 <br/>HLT_HIL2Mu20 <br/>HLT_HIL2Mu3 <br/>HLT_HIL2Mu5Tight <br/>HLT_HIMinBiasBSC <br/>HLT_HIMinBiasBSC_OR <br/>HLT_HIMinBiasHF <br/>HLT_HIMinBiasHfOrBSC <br/>HLT_HIMinBiasHf_OR <br/>HLT_HIMinBiasPixel_SingleTrack <br/>HLT_HIMinBiasZDCPixel_SingleTrack <br/>HLT_HIMinBiasZDC_Calo <br/>HLT_HIMinBiasZDC_Calo_PlusOrMinus <br/>HLT_HIMinBiasZDC_Scint <br/>HLT_HIPhoton15 <br/>HLT_HIPhoton20 <br/>HLT_HIPhoton30 <br/>HLT_HIRandom <br/>HLT_HIStoppedHSCP35 <br/>HLT_HIUpcEcal <br/>HLT_HIUpcMu <br/>HLT_HIZeroBias <br/>HLT_HIZeroBiasPixel_SingleTrack <br/>HLT_HIZeroBiasXOR </p>"
},
"publisher": "CERN Open Data Portal",
"recid": "14011",
"relations": [
{
"title": "/HIAllPhysics/HIRun2010-v1/RAW",
"type": "isChildOf"
}
],
"run_period": [
"HIRun2010"
],
"system_details": {
"container_images": [
{
"name": "docker.io/cmsopendata/cmssw_3_9_2_patch5-slc5_amd64_gcc434:latest",
"registry": "dockerhub"
},
{
"name": "gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_3_9_2_patch5-slc5_amd64_gcc434:latest",
"registry": "gitlab"
}
],
"global_tag": "GR_R_39X_V6B::All",
"release": "CMSSW_3_9_2_patch5"
},
"title": "/HIAllPhysics/HIRun2010-ZS-v2/RECO",
"title_additional": "HIAllPhysics primary dataset in RECO format from the 2.76 TeV Pb-Pb run of 2010 (/HIAllPhysics/HIRun2010-ZS-v2/RECO)",
"title": "JADE raw data",
"title_additional": "JADE raw data",
"type": {
"primary": "Dataset",
"secondary": [
"Collision"
]
},
"usage": {
"description": "You can access these data through the CMS Open Data container or the CMS Virtual Machine. See the instructions for setting up one of the two alternative environments and getting started with CMS heavy-ion data data in",
"description": "You can access these data through the EOS",
"links": [
{
"description": "Running CMS analysis code using Docker",
"url": "/docs/cms-guide-docker"
},
{
"description": "How to install the CMS Virtual Machine",
"url": "/docs/cms-virtual-machine-2010"
},
{
"description": "Usage example for CMS 2010 heavy-ion data",
"recid": "466"
}
]
},
"validation": {
"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:",
"links": [
{
"description": "CMS data quality monitoring: Systems and experiences",
"url": "http://iopscience.iop.org/1742-6596/219/7/072020/pdf/1742-6596_219_7_072020.pdf"
},
{
"description": "The CMS Data Quality Monitoring software experience and future improvements",
"url": "http://cds.cern.ch/record/1631039/files/CR2013_418.pdf"
},
{
"description": "The CMS data quality monitoring software: experience and future prospects",
"url": "http://iopscience.iop.org/1742-6596/513/3/032024/pdf/1742-6596_513_3_032024.pdf"
}
]
}
Expand Down

0 comments on commit 90fae4d

Please sign in to comment.